Print

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

[TomiTapio]

Suggestions:
- in the gamelog write "X asked to be a <monster hunter / entertainer> here, request was approved".

- in the gamelog write "We were granted a barony and X became a <title>".

- in the gamelog write "We traded X worth of goods to <civ> caravan and got Y worth of items."

- in the gamelog write "X people witnessed Y doing a crime."

- in the gamelog write "criminal X received a beating."

[Shonai_Dweller]

What would you use it for? As a fortress diary writing aid?
First two are already logged in Legends so should be easy enough.

[TomiTapio]

Well, the gamelog is already spammed with "activated as soldier! deactivated as soldier!" so it should tell important events.

[Shonai_Dweller]

Well, the gamelog is already spammed with "activated as soldier! deactivated as soldier!" so it should tell important events.

That's not much of a reason. Do you use the gamelog? Increasing the amount written to it won't help performance.

[TomiTapio]

I sense hostility from you.

The reason is: rare thing (barony, crime, beating, workshop toppled) happened in the fort, therefore it should be in the gamelog.

[DG]

Do you use the gamelog?

I do. I also save the game log for every year and keep it with the save, then start a fresh gamelog file at the start of spring. I'd like to see Tomi's suggested additions in it.

[Shonai_Dweller]

I'll not being hostile, I asked what you need the extra gamelog info for? And your answer was, 'because other useless stuff is in there'. Which doesn't seem like much of a reason to request Toady to put time and effort into making something.

Glad to see someone else respond. I use Legends, and don't often open the gamelog, but I can see how it'd be useful for, maybe modding or something. Utils like Soundsense would probably benefit. Plus there's some utils that create stories of a fortress from the gamelog which are very cool. Do people still use these? How popular is the gamelog? That's all I wanted to know.

[anewaname]

Having those additional entries in the log would be helpful for the story building aspect of your fort. When reviewing the gamelog, you would be able to see the chronological relation of those events to other events. They would not take up much filesystem, and they would be a great reason to add some new sound clips to Soundsense.

[Su]

iirc the events that get logged are customisable in one of the init files somewhere, though that might just be which events get the "box" treatment [e.g, forgotten beast / vile force of darkness arrival].

as it is the log is far too easily spammed, but I'd consider this more due to bugs in the game than to a flaw in the log concept itself.

the log is very useful for me to catch up on the happenings about my fort. I would love to see the suggestions implemented - beatings and crime reports are potentially site-changing events [tantrum spirals, vampires draining your most important dwarf dry] that are all too easy to miss, and as anewaname notes above the more player-driven events are useful for storytelling, which is a very big part of why some people like this game.

[TomiTapio]

I think the "accept petition" isn't a box-announcement now, rather a pop-up window, like the Barony-accept and liaison dialogs.
Really would be nice to see "criminal accused" and "criminal beating" and "criminal was chained/unchained" in the gamelog.

(if paste gamelog to spreadsheet with spaces-as-separators, can debug combat problems like, robes are way too protective)

[Putnam]

Well, the gamelog is already spammed with "activated as soldier! deactivated as soldier!" so it should tell important events.

That's not much of a reason. Do you use the gamelog? Increasing the amount written to it won't help performance.

won't really hurt--testing has shown negligible difference in my experience between SSD and hard drive, so I doubt the writing to gamelog is causing much issue

[anewaname]

When the gamelog gets hit with many messages, the file write is not the slowdown. Disk writes go to the disk cache before they go to the actual disk, which is a memory to memory transfer, and DF likely uses less than 1% of an older hard drive's cache at any time. DF's internal management of the log entries might slow DF down a fractional amount, but the display to screen at a rate and the user's ability to intake those messages is the main slowdown.