Open DigoAlves1480 opened 3 months ago
About Time Guardian, I noticed is possible to kill its Blaze and Frost transformations. When you defeat it in this way, Time Guardian's kill does not count to bosstiary and throws that exactly error. I am unfamiliar with this repo, but probably it tries to switch time guardian position with the killed (now null) transformation.
Update your issue and explain better about the problem.
Priority
Medium
Area
What happened?
2024-07-03 03:36:52 - [2024-03-07 03:36:52.615] [error] Lua Script Error Detected 2024-07-03 03:36:52 - --------------------------------------- 2024-07-03 03:36:52 - Interface: Scripts Interface 2024-07-03 03:36:52 - Script ID: /home/server/canary/data-otservbr-global/scripts/actions/object/imbuement_shrine.lua:callback 2024-07-03 03:36:52 - Error Description: ...ervbr-global/scripts/actions/object/imbuement_shrine.lua:8: attempt to call method 'isItem' (a nil value) 2024-07-03 03:36:52 - stack traceback: 2024-07-03 03:36:52 - [C]: in function 'isItem' 2024-07-03 03:36:52 - ...ervbr-global/scripts/actions/object/imbuement_shrine.lua:8: in function <...ervbr-global/scripts/actions/object/imbuement_shrine.lua:3> 2024-07-03 03:36:52 - --------------------------------------- 2024-07-03 03:36:52 - 2024-07-03 03:37:33 - [2024-03-07 03:37:33.425] [error] Lua Script Error Detected 2024-07-03 03:37:33 - --------------------------------------- 2024-07-03 03:37:33 - Interface: Scripts Interface 2024-07-03 03:37:33 - Script ID: /home/server/canary/data-otservbr-global/scripts/spells/monster/time_guardiann.lua:callback 2024-07-03 03:37:33 - Error Description: ...tservbr-global/scripts/spells/monster/time_guardiann.lua:43: attempt to index a nil value 2024-07-03 03:37:33 - stack traceback: 2024-07-03 03:37:33 - [C]: in function '__index' 2024-07-03 03:37:33 - ...tservbr-global/scripts/spells/monster/time_guardiann.lua:43: in function <...tservbr-global/scripts/spells/monster/time_guardiann.lua:36> 2024-07-03 03:37:33 - ---------------------------------------
What OS are you seeing the problem on?
Linux
Code of Conduct