same issues at every combat ^^
1 Like
oh man… the amount of dups for this bug… 
1 Like
sorry no options to merge xD
1 Like
Title: Prune Dead Listeners Looping Error
Summary:was attacked by goblins and error popped up.
Steps to reproduce:
1)play
2)get attacked
3)error
Expected Results:
Defeat goblins
Actual Results:
defeat goblins, but error out
Notes:
Game Mode:Normal Mode
I noticed that in my old game I never got this error when it came to goblin attacks(due to the 4000 net worth), however, what I noticed with this game was that I had a low networth.Possibly the reason why we are getting this error? just a thought
Attachments:
Image:
http://s6.postimg.org/4z3cnb129/253250_2015_09_30_00010.png
Save File:
Log:
Error Log:
develop-2617 (x64)
radiant/modules/events.luac:73: assertion failed!
stack traceback:
[C]: ?
[C]: in function 'assert’
radiant/modules/events.luac:73: in function '_prune_dead_listeners’
radiant/modules/events.luac:78: in function '_update’
radiant/server.luac:19: in function <radiant/server.luac:17>
Versions and Mods:
Mods: N/A
Version:StoneHearth 0.12.0
Develop:2617 x64 build
System Information:
System: Windows 10 Home 64-bit
Processor:Intel Core i7-4790k CPU @ 4.00GHz
Ram:16.0 GB
@8BitCrab can you remove the RES statement ^^ its still active for 2617 ^^
but fixed in 2620 
lol ^^ i have seen it just this moment xD
1 Like
</3
say it aint so wiese
1 Like
Title:
Prune Dead Listeners Persists?
Summary:
Loaded a dev savegame from four days ago and continued playing on 2620. Instructed my footmen to dispatch some goblins, which they did with extreme prejudice. The moment they died, the game threw these prune dead listeners errors:
develop-2620 (x64)
@radiant/modules/events.luac:73: old_entry is nil
stack traceback:
radiant/modules/common.luac:46: in function 'report_traceback'
radiant/modules/common.luac:125: in function 'verify'
radiant/modules/events.luac:73: in function '_prune_dead_listeners'
radiant/modules/events.luac:78: in function '_update'
radiant/server.luac:19: in function <radiant/server.luac:17>
develop-2620 (x64)
@radiant/modules/events.luac:73: old_entry ~= entry
stack traceback:
radiant/modules/common.luac:46: in function 'report_traceback'
radiant/modules/common.luac:125: in function 'verify'
radiant/modules/events.luac:73: in function '_prune_dead_listeners'
radiant/modules/events.luac:78: in function '_update'
radiant/server.luac:19: in function <radiant/server.luac:17>
It’s important to note that this behavior existed in 2609 as well, which was the last Dev build I tested (about four days ago), so unless 2609 save games are invalid for testing this bugfix, the issue is apparently still present.
Steps to reproduce:
1) Load this save game
2) Wait til Goblins spawn again
3) Create a Party consisting of both footmen and set a waypoint near the goblins
4) Wait for the footmen to kill a goblin
Expected Results:
Dead goblins, no _prune_dead_listeners error dialog.
Actual Results:
Dead goblins, _prune_dead_listeners error dialog.
Versions and Mods:
Dev 2620
System Information:
Win10, x64
1 Like
i would suggest that you test it on a new save file before we say that this evil demon hath crawled back from the land it was banished to… just to be certain.
1 Like
Undoubtedly something to test. Definitely why I called it out in detail here though, JUST to make it clear. Attempting to recreate it from scratch with a new save now.
2 Likes
develop-2620 (x64)
@radiant/modules/events.luac:73: old_entry is nil
stack traceback:
radiant/modules/common.luac:46: in function 'report_traceback’
radiant/modules/common.luac:125: in function 'verify’
radiant/modules/events.luac:73: in function '_prune_dead_listeners’
radiant/modules/events.luac:78: in function '_update’
radiant/server.luac:19: in function <radiant/server.luac:17>
i’m afraid that simply killing this bug isnt enough. evil like this doesnt just die. we have to chop its head off, put garlic in its mouth, put it in a pit at a crossroads and burn it under the light of dawn. add some blessed gasoline since i doubt holy water would help with combustion.
3 Likes
alas my friend, that is not enough, for this is the hydra of all bugs, if you chop off one of its heads two more will come back in its place…
going to merge this with the old thread.
edit: paging @Albert… yet again… 
2 Likes
…night of the living bug…“it’s hard for us here to believe what we’re reporting to you, but it does seem to be a fact. The dead bugs are returning to life and seeking human vicitms…”
3 Likes
@8BitCrab sorry…I think it mutated. The error contains “prune dead listeners” though so I thought I would post a copy here in case it’s a related issue
Title: Zombie bug
Summary: The usual. Combat began, a goblin died, error popped up.
Steps to reproduce:
-
Enter combat
-
Slay a goblin
-
visit the forums
Expected Results: a goblin dies, followed by all of his friends and family.
Actual Results: a goblin dies and @Albert 's stress levels increase
Notes: <develop-2620 (x64)
@radiant/modules/events.luac:73: old_entry is nil
stack traceback:
radiant/modules/common.luac:46: in function ‘report_traceback’
radiant/modules/common.luac:125: in function ‘verify’
radiant/modules/events.luac:73: in function ‘_prune_dead_listeners’
radiant/modules/events.luac:78: in function ‘_update’
radiant/server.luac:19: in function <radiant/server.luac:17>>
second error
<develop-2620 (x64)
@radiant/modules/events.luac:73: old_entry ~= entry
stack traceback:
radiant/modules/common.luac:46: in function ‘report_traceback’
radiant/modules/common.luac:125: in function ‘verify’
radiant/modules/events.luac:73: in function ‘_prune_dead_listeners’
radiant/modules/events.luac:78: in function ‘_update’
radiant/server.luac:19: in function <radiant/server.luac:17>>
Attachments: I had to zip the log file because of the size…fingers crossed it transmits? Stonehearth.log.zip (2.9 MB)
Versions and Mods: A12 develop-2620x64
Debugging tools only
System Information:
Windows 10 x64 home
12GB DDR3 RAM
Intel Core i7-3630QM @ 2.4GHz
Primary graphics processor: Nvidia GT650M w/ 1 GB GRAM
Secondary (inactive) graphics processor: Intel HD4000 integrated graphics chip
All drivers update automatically and are checked daily
2 Likes
@8BitCrab AAaaaaand confirmed in a brand new 2620 world. Same symptoms. Save game here. stonehearth.log here.
Paging: @sdee
Error messages:
develop-2620 (x64)
@radiant/modules/events.luac:73: old_entry is nil
stack traceback:
radiant/modules/common.luac:46: in function 'report_traceback’
radiant/modules/common.luac:125: in function 'verify’
radiant/modules/events.luac:73: in function '_prune_dead_listeners’
radiant/modules/events.luac:78: in function '_update’
radiant/server.luac:19: in function <radiant/server.luac:17>
develop-2620 (x64)
@radiant/modules/events.luac:73: old_entry ~= entry
stack traceback:
radiant/modules/common.luac:46: in function 'report_traceback’
radiant/modules/common.luac:125: in function 'verify’
radiant/modules/events.luac:73: in function '_prune_dead_listeners’
radiant/modules/events.luac:78: in function '_update’
radiant/server.luac:19: in function <radiant/server.luac:17>
3 Likes
The bug still exists, but the games should be playable after the error occurs. We added logging to help diagnose the issue, but your save games should allow us track down the problem. Thanks for all the help!
5 Likes
Does anyone else have a save game with this error? I simply cannot get it to happen in my games or with megashub’s save.
2 Likes
i’ll test it out right now, both with a “clean” save and mega’s
okay @Albert, havent tested with a new save yet, but upon loading mega’s i got this error,
im guessing thats because the game was saved whilst in x-ray…
back to the bug at hand, except for a massive field of rotten turnips the town of “new rosegourd” was threat free, so there was never anything to fight to see if the error still persisted…
i’m going to go test a new save now.
I’ll spend some time generating save files with the zombie bug tonight. Is there a particular set of circumstances or tips for generating a save that would be most helpful?