ToME: the Tales of Maj'Eyal

got an infinite loading screen after returning to Reknor to get the two components for the portal. Used the rod of recall and got the loading loop.

Any way the save file can be rescued?

thanks in advance, and keep up the great works guys!

return d [string "d={}..."]:699: unexpected symbol near '='
FROM /mod/addons/cults/superload/engine/dialogs/ShowErrorStack.lua loading previous!


ERROR:
Game version: tome-1.7.0
Addons: ashes-urhrok-1.7.0[O], items-vault-1.7.0[O], possessors-1.7.0[O], orcs-1.7.0[O], cults-1.7.0[O]

Game version (character creation): tome-1.7.0
Lua Error: /engine/class.lua:484: bad argument #1 to 'setfenv' (number expected, got nil)
At [C]:-1
At [C]:-1 setfenv
At /engine/class.lua:484 deserialize
At /engine/class.lua:502 load
At /engine/Savefile.lua:477 loadObject
At [string "d={}..."]:9148 deserialize
At /engine/class.lua:502 load
At /engine/Savefile.lua:477 loadObject
At [string "d={}..."]:14 deserialize
At /engine/class.lua:502 load
At /engine/Savefile.lua:477 loadObject
At [string "d={}..."]:72 deserialize
At /engine/class.lua:502 load
At /engine/Savefile.lua:477 loadObject
At [string "d={}..."]:3 deserialize
At /engine/class.lua:502 load
At /engine/Savefile.lua:477 loadObject
At [string "d={}..."]:129 deserialize
At /engine/class.lua:502 load
At /engine/Savefile.lua:477 loadReal
At /engine/Savefile.lua:629
At /engine/SavefilePipe.lua:295 doLoad
At /engine/Zone.lua:803 load
At /engine/Zone.lua:120 init
At /engine/class.lua:147 new
At /mod/class/Game.lua:1142 changeLevelReal
At /mod/addons/cults/superload/mod/class/Game.lua:45 changeLevelReal
At [string "if engine.version_compare(game.__mod_info.ver..."]:2446 changeLevelReal
At /mod/class/Game.lua:948 unload
At /engine/Game.lua:467 unregisterDialog
At /mod/dialogs/ShowEquipInven.lua:181
At /engine/KeyBind.lua:231 receiveKey
At /engine/ui/Dialog.lua:807 keyEvent
At /engine/ui/Dialog.lua:510

Caused by equipping Writhing Ring of the Hunter. 1.7.1 will fix this issue and also should let you continue saves where this issue has already occurred.

thank you for the update , much appreciated!