Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[zwei]

(This is mostly "selfish suggestion" because it is aimed to be usefull for one certain tool. But overall, it seems like good idea for game to be more chatty when anouncing things for people who like to recount history of fort later on for fanfiction stories or who could use some anouncements to be able to react to events that need reaction to. Besides, it does not seem like overly complicated thing to do for most of them.)

Okay, I suggest game log and anouncements to contain theese messages:

* When game is loaded, usefull to know what region/fortress is being logged for consecutive games.

Loaded game for <region name>, fortress <fortress name>. It is <season> of <year>, <month_date> <month>.

* When dwarf is marked as criminal by justice and overall justice messages. Player might want to react to this message.

<dwarf> was found guilty of <crime> and was sentenced for <punishment>.
<dwarf> was imprisoned.
<dwarf> was released from prison.

* Merchants provide unloading goods message, but not "ready to trade" message, which requires close watch on it. Anouncing the fact that player can start trading is usefull.

Merchants have finished unloading and are ready to trade.

* Siege end, purely for historical records.

<race> siege has been broken.

* Animal slaughtering message is a bit confusing because it is same as when animal gets killed by hostiles and knowledge that cat was slaughtered by player isntead of being killed by monster is usefull.

<animal> was slaughtered.

* Hostiles deaths are not logged at all - they should be logged as part of their combat log. Fun for grepping answer for "how many goblins did we kill?"

* Dwarven skill-ups and downs. I have chosen breakpoints after which low-quality products are impossible and first signs of rust so that player can react accrdingly (either ignore or queue some production).

<dwarf> has became Proficient <skill>.
<dwarf> has became Accomplished <skill>.
<dwarf> has became Legendary <skill>.

<dwarf> is now very rusty at <skill>.
<dwarf> forgot great deal of <skill>.

* Animal groups entering/leaving map should be anounced. Important-ish to tip off player that hunters will be doing their thing or that there are new targets for military live practice.

<species> wandered near fortress.
<species> have left.

* Total population after embark wave, for historical records.

There are now <number> <fortress_race> in our fortress.

* Dwarves getting to critical levels of hunger or thirst, somethign that player might want to know in case cosntriction worker walled himself off at inaccessible location.

* Mayor elections, ascendance from expedition-leader led community to mayor-led one. Just to record history better.

* Party ending, as players could want to be tipped off that workforce will be once again avaialble.

* Workshop construction being finished, so that player can immediatelly queue tasks.

<dwarfname> has finished construction of <workshopname>.

---

That's it for now.

[NW_Kohaku]

Oh.  THAT kind of logging... I was expecting something about mechanisms for deforestation.

Someone had a similar thread recently, asking about making an announcement for when dwarves were becoming very hungry or very thirsty because he had dwarves get trapped, and didn't realize it, and wanted a warning for that.  You might want to addend that onto your list.

[zwei]

Oh.  THAT kind of logging... I was expecting something about mechanisms for deforestation.

Someone had a similar thread recently, asking about making an announcement for when dwarves were becoming very hungry or very thirsty because he had dwarves get trapped, and didn't realize it, and wanted a warning for that.  You might want to addend that onto your list.

That sounds reasonable as long as no extra "and has no access to food/drink" logic is requested

[Shadowclaimer]

Do want, so badly! I have always wondered why these kinds of things didn't appear in the logs. Instead i get three thousand "job item misplaced" messages and occasionally something useful (Migrants have arrived!)

[jaked122]

I can agree to your sentiment, but usually I try to stick around for when my dwarves are building something, especially when building upwards, so they don't get trapped

[Moonshine Fox]

I always missed the "<Dwarf> is now more experienced" messages from older versions. This suggestion, in addition to an "on/off" list of what messages are supposed to be displayed, would be great!

Item lost: Off
Siege: On
Ambush: Off

and so on and so forth. Would be wonderful!

[Aramco]

Oh, Logging, I thought you misspelled Lodging.

[Virex]

Someone said logging?


Anyway, while this may seem like a good idea, it should not go without improved functionality for the logs. If you're spammed with more messages there should be some good ways to filter them. Other then that, good ideas.

[zwei]

Someone said logging?


Anyway, while this may seem like a good idea, it should not go without improved functionality for the logs. If you're spammed with more messages there should be some good ways to filter them. Other then that, good ideas.

Technically, you are able to change log preferences, it is in init/announcements.txt - it does not have any anti-spam features however.

[Virex]

I mean filtering out specific notification types, such as death announcements, combat messages et cetera. T ogling off the combat messages for a moment so you can find that "dangerous terrain" message shouldn't require messing around with the init files.

[harborpirate]

Someone said logging?

Anyway, while this may seem like a good idea, it should not go without improved functionality for the logs. If you're spammed with more messages there should be some good ways to filter them. Other then that, good ideas.

Agreed. What we really need are better ways to filter log messages. Ideally, the game could log all sorts of things and players could decide what they want to see on the fly.

I really like the idea of increasing the number and types of things logged, but until there are better ways to parse through the logs it'll make things even harder to find.

[zwei]

Added party ending to list.

I really like the idea of increasing the number and types of things logged, but until there are better ways to parse through the logs it'll make things even harder to find.

Well, anouncements.txt should help you filter our gobally whatever messages you find too distracting.

And, of course, you can have some tool read logs and do whatever with them, including filtering unimportant stuff.

[zwei]

Another idea : People might want to know that workshop construction has finished so that they can start queuing tasks asap.

[Thundercraft]

A lot of good ideas here. I would agree with most of these suggestions.

In addition, I think the game log should register more events in Adventure Mode. Currently, many events in Adventure Mode are resolved in chat. I think events such as facing your quest target or encountering a megabeast should always be logged.

[HammerHand]

These are some great logging suggestions!  I wholeheartedly approve.  Some of them seem a little superfluous, but I can also see why they'd be useful (and hey, it's not like we don't get superfluous messages already).

Hammerhand cancels post thread on forum:  thread lost or destroyed.
Hammerhand cancels Clean Self:  Area Inaccessible.