You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
21433.725 Error MainLoop.cpp:1404: Exception at tick 78463607: Мод YARM - Resource Monitor (0.10.14) вызвал неустранимую ошибку.
Пожалуйста, сообщите об этой ошибке автору мода.
Error while running event YARM::on_tick (ID 0)
LuaEntity API call when LuaEntity was invalid.
stack traceback:
[C]: in function '__index'
__YARM__/resmon.lua:453: in function 'scan_current_site'
__YARM__/resmon.lua:1676: in function 'update_players'
__YARM__/resmon.lua:1733: in function 'on_tick_internal'
__YARM__/resmon.lua:1767: in function <__YARM__/resmon.lua:1762>
21433.725 Error ClientMultiplayerManager.cpp:100: MultiplayerManager failed: "Мод YARM - Resource Monitor (0.10.14) вызвал неустранимую ошибку.
Пожалуйста, сообщите об этой ошибке автору мода.
Error while running event YARM::on_tick (ID 0)
LuaEntity API call when LuaEntity was invalid.
stack traceback:
[C]: in function '__index'
__YARM__/resmon.lua:453: in function 'scan_current_site'
__YARM__/resmon.lua:1676: in function 'update_players'
__YARM__/resmon.lua:1733: in function 'on_tick_internal'
__YARM__/resmon.lua:1767: in function <__YARM__/resmon.lua:1762>"
21433.725 Info ClientMultiplayerManager.cpp:616: UpdateTick(78463607) changing state from(InGame) to(Failed)
The text was updated successfully, but these errors were encountered:
We take the next entity from next_to_scan and assume it still exists but any number of ticks may have passed since it was added -- the entity might have been mined away, especially with a particularly fast miner. Should be a relatively easy fix.
Just a simple guard clause to make sure that if an entity is mined away while we're scanning the site, we don't crash by trying to access something that doesn't exist.
Fixes#170
The text was updated successfully, but these errors were encountered: