Print

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

[Meph]

They are harmless.

All but the first one are some reaction-trigger failing to register (meaning some reaction somewhere isn't going to work as intended) and the first one is roses-init failing, meaning anything that relies on roses scripts will fail.

Not quite. First one is one of Roses script, yes, but it does not affect the others. I talked with him about it. Everything I do with his scripts works.

The reaction-trigger I havent seen myself, but until I know which reactions cause this, I cant do anything.

[Dirst]

Figured out why TESB seems to be initializing three times.  Meph has modified copies of a TESB script to handle warpstone.  That's fine except that all three calls are using the same callback handle in the Eventful system, meaning that only one is actually active.

Meph, on line 185 "tesbJobMonitor" is the callback handle, you'll probably want to change that to "warpstone" or something similar.  Then delete line 225 and adjust the text in the new 225.  The proper solution is to expand on TESB's job monitor so that it can handle more than one set of probabilities, but I'm not sure when I'll be able to get to that.

With the corrected callbacks, it will function as expected with the minuscule probability of multiple specials occurring in the same tile.

[Meph]

Nice catch, I'll fix it for the next release.

[urmane]

Question: with weekly releases, the question comes up, "Can I retrofit my existing fort with new content?"

Maybe not everybody - still, how to determine what has been updated, and if it would break an existing fort?  Maybe I could write a script ...

[zakhad]

Had a crash with this version when trying to carve stairs into a 1st layer cavern (making a well for my hospital) upon that tile being flooded with water it crashed (Was observing as I was about to destroy the stairs and start channelling out the well)

The only relevant information from the error log is

Spoiler (click to show/hide)

(Above this was just a lot of return kill path finding fails)

Connected Component Overflow
Connected Component Overflow
Connected Component Overflow
path fail: nith wisp,0,107,30 -> 0,108,30: Id #6650:Path Goal Seek Station Flood:Station None at 0,108,30

stderr log

Spoiler (click to show/hide)

(Above this bit it was just repeating)

stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
Invoking: gui/workflow
Invoking: gui/workflow
Invoking: gui/workflow
...Fortress/data/save/region3/raw/scripts/base/on-death.lua:41: attempt to index global 'killer' (a nil value)
stack traceback:
   ...Fortress/data/save/region3/raw/scripts/base/on-death.lua:41: in function <...Fortress/data/save/region3/raw/scripts/base/on-death.lua:25>
Invoking: gui/workflow
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
Invoking: gui/workflow
Invoking: job-material DACITE
Current job material isn't inorganic: any
Invoking: gui/workflow
Invoking: gui/workflow
Invoking: gui/workflow

No idea what to look for error wise to report a crash. Was it a path finding memory crash? (I installed LAA)

[Meph]

Had a crash with this version when trying to carve stairs into a 1st layer cavern (making a well for my hospital) upon that tile being flooded with water it crashed (Was observing as I was about to destroy the stairs and start channelling out the well)

The only relevant information from the error log is

Spoiler (click to show/hide)

(Above this was just a lot of return kill path finding fails)

Connected Component Overflow
Connected Component Overflow
Connected Component Overflow
path fail: nith wisp,0,107,30 -> 0,108,30: Id #6650:Path Goal Seek Station Flood:Station None at 0,108,30

stderr log

Spoiler (click to show/hide)

(Above this bit it was just repeating)

stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
Invoking: gui/workflow
Invoking: gui/workflow
Invoking: gui/workflow
...Fortress/data/save/region3/raw/scripts/base/on-death.lua:41: attempt to index global 'killer' (a nil value)
stack traceback:
   ...Fortress/data/save/region3/raw/scripts/base/on-death.lua:41: in function <...Fortress/data/save/region3/raw/scripts/base/on-death.lua:25>
Invoking: gui/workflow
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: attempt to index a nil value
stack traceback:
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:116: in function 'getitemType'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:126: in function 'handler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:166: in function 'equipHandler'
   ...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:175: in function <...3)\Dwarf Fortress/hack/scripts/modtools/item-trigger.lua:169>
Invoking: gui/workflow
Invoking: job-material DACITE
Current job material isn't inorganic: any
Invoking: gui/workflow
Invoking: gui/workflow
Invoking: gui/workflow

No idea what to look for error wise to report a crash. Was it a path finding memory crash? (I installed LAA)

Could you please upload the save? I'd like to have a look. It most likely has a different reason, not the water or pathfinding.

[zakhad]

I don't have the exact save anymore, (Abandoned. Although the site could be re-embarked upon?) I just moved to another site; next door to be exact. I tried replicating the issue at the time, but it never crashed again, same spot similar actions etc, it didn't crash the game. It was acting very odd with pathfinding though, as my log was filled with it, and a lot of dwarves standing still waiting for tile updates (So they could figure out where to path) or whatever DF calls them. I was assuming it was just a out of memory crash as it had to suddenly calculate a lot of path finding, when it didn't have the memory to do so, as the dwarf had to run away after channelling the last stairs the entire cavern had to be calculated for pathing but that's just my 2 pence.