When I try to right click the ghost right after the title appears, I get
AsyncErr: Lua: Runtime error from mod 'citadel_core' in callback luaentity_run_simple_callback(): ...fgaz/.minetest/games/citadel/mods/citadel_core/ghost.lua:27: attempt to concatenate a nil value
stack traceback:
...fgaz/.minetest/games/citadel/mods/citadel_core/ghost.lua:27: in function <...fgaz/.minetest/games/citadel/mods/citadel_core/ghost.lua:22>
This happens when you first re-join the game (unless you're expirencing a different bug). It you time travel it will reload the ghosts and fix the problem temporarily. It's been fixed on github, and I'll publish a release on contentdb that fixes it after the jam.
I still get the error. You're allowed to release bug fixes on ContentDB that impact the game
2023-12-26 15:17:03: ERROR[Main]: ServerError: AsyncErr: Lua: Runtime error from mod 'citadel_core' in callback luaentity_run_simple_callback(): ...inetest/bin/../games/citadel/mods/citadel_core/ghost.lua:27: attempt to concatenate a nil value
2023-12-26 15:17:03: ERROR[Main]: stack traceback:
2023-12-26 15:17:03: ERROR[Main]: ...inetest/bin/../games/citadel/mods/citadel_core/ghost.lua:27: in function <...inetest/bin/../games/citadel/mods/citadel_core/ghost.lua:22>
It looks like the two commits that fix this bug were already in your main branch, mixed in with other contributed post-jam changes, and just need to be cherry-picked into a separate branch to be released. This seems to be the minimum set of changes necessary to fix the crash without altering the gameplay as designed.
When I try to right click the ghost right after the title appears, I get
AsyncErr: Lua: Runtime error from mod 'citadel_core' in callback luaentity_run_simple_callback(): ...fgaz/.minetest/games/citadel/mods/citadel_core/ghost.lua:27: attempt to concatenate a nil value stack traceback: ...fgaz/.minetest/games/citadel/mods/citadel_core/ghost.lua:27: in function <...fgaz/.minetest/games/citadel/mods/citadel_core/ghost.lua:22>Fixed
I consider this to be game-breaking, hopefully I don't get disqualified for making an update that fixes it. If I do, whatever.
Hi, I'm still getting that error when interacting with the ghost, even though I have the latest version of the game. Thanks.
This happens when you first re-join the game (unless you're expirencing a different bug). It you time travel it will reload the ghosts and fix the problem temporarily.
It's been fixed on github, and I'll publish a release on contentdb that fixes it after the jam.
I still get the error. You're allowed to release bug fixes on ContentDB that impact the game
It looks like the two commits that fix this bug were already in your main branch, mixed in with other contributed post-jam changes, and just need to be cherry-picked into a separate branch to be released. This seems to be the minimum set of changes necessary to fix the crash without altering the gameplay as designed.
I made the branch for you already, and you'd just need to pull it into your repo as a new branch, and then make a release from that instead of main. https://github.com/Warr1024/minetest-citadel/commits/jamhotfix/
Do you need help with any of the git or CDB parts of this?
I wish I had seen this earlier, thanks for your help. Hopefully I did everything right?
Hey I'm also getting an error in the new version, won't let me even start the game, makes the engine crash itself
1) What version of minetest are you on?
2) Could you get me an error message?
5.8.0
2024-01-17 21:32:05: ERROR[AsyncWorker-0]: HTTPFetch for https://content.minetest.net/api/updates/?type=mod&type=game&type=txp&protocol_version=43&engine_version=5.8.0 failed: Couldn't resolve host name
this error message was constantly being written
If the engine itself is crashing you should report the bug in the minetest issue tracker https://github.com/minetest/minetest/issues/
This error came in the latest version not in the previous ones
In what versions of the game does the engine not crash? Is it only the very latest version that doesn't work?
Hey no need to worry I apologize the game successfuly ran the second time I opened it, maybe the engine does have some fault