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
{{ message }}
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.
When entering Toto's building, Manny is not visible anymore. He can neither perform any action nor leave the building. If the arrow keys are pressed the scene switches from time to time to the room with the fridge.
This bug was introduced with commit c9b33fc, "GRIM: Fix an error with patchr instead of detecting it later". Removing "lua_error("Bad argument to start_script");" in start_script(), ltask.cpp fixes this problem. Either the patchr patch is not correctly applied or there are more positions in the lua code that pass bad arguments to start_script().
The text was updated successfully, but these errors were encountered:
I think the problem is that the savegame was made before the fixing of the lua script. So you have the old bugged script and the c++ code that doesn't let it pass anymore.
It is like giucam said. The script was changed by the patchr. But as I used a savegame, the old scripts embedded in the savegame were used. See #649.
The script fix prevents that bad arguments are passed to start_script() and so lua_error() was enabled again, which works fine with patched scripts - but not with old scripts in a savegame.
When entering Toto's building, Manny is not visible anymore. He can neither perform any action nor leave the building. If the arrow keys are pressed the scene switches from time to time to the room with the fridge.
This bug was introduced with commit c9b33fc, "GRIM: Fix an error with patchr instead of detecting it later". Removing "lua_error("Bad argument to start_script");" in start_script(), ltask.cpp fixes this problem. Either the patchr patch is not correctly applied or there are more positions in the lua code that pass bad arguments to start_script().
The text was updated successfully, but these errors were encountered: