Death Counter


Tracks the ways you (and your friends) have died

Utilities
2 months ago
1.0 - 2.0
7.49K

b [Fixed]When trying to run the game from the map editor

4 years ago

The mod Death Counter (0.0.1) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event Death_Counter::on_player_removed (ID 73)
Death_Counter/control.lua:41: attempt to index field '?' (a nil value)
stack traceback:
Death_Counter/control.lua:41: in function <Death_Counter/control.lua:40>

4 years ago

Thanks, will investigate

4 years ago

I am not able to reproduce the problem .. this is what I did

  • Started a blank game with just my mod installed
  • From the console entered /editor twice
  • From the editor mode un-paused the game
  • Moved around

No crash.

Can you give me some more details on what you were doing ?
Maybe a save file so I can see if something is going on with a mod conflict.

4 years ago
(updated 4 years ago)

Yep. Other mods could have made an impact.
https://drive.google.com/file/d/1LhFuXo7A_KGhI6WkDVJnVaFEcLy4MH0D/view?usp=sharing
This is a saved scenario.
The mod list is long. Casual free play start does not crash it. But doing it from editor does.
Removing Death Counter solves the issue.
I might have time today\tomorrow to zero in on the mod combinations that cause it..

The crash is before you have control in game, so you don't need to preform any game actions.

4 years ago

I think I have found the cause .. something is running the method game.remove_offline_players()

Now I have to figure out how I want to deal with this
.. should I purge the players death count when they have been removed from the game
.. or should I hold onto their counter in case them come back and we want to keep a running track of their deaths.

I think the second option is what I am going to aim for.

4 years ago

yep, second sounds better for long multiplayer games ^_^

4 years ago

Let me know if this works, it should as I have removed the event capture entirely for .. on_player_removed

4 years ago

Yep, fixed now. Thank you!