0
Declined

Mighty Script: Triggers not being deleted

SeriousToni 3 months ago • updated 2 months ago 7

I found out there is an error, in which the editor doesn't correctly delete my triggers and still uses them (I deleted them in the mighty script, but on "publish and test" it still uses them ingame). I put the file in the attachment. Go to god mode, create some units near the final Hero Gate and attack the Heroes & Gate. Normally it should end the game if you kill the Lord of the Land. But somehow it uses old triggers that print console messages and ends the game if you hurt one of them or the gate. The triggers were already deleted in the mighty script. Still ingame they trigger. At least when I "Publish and Test", even after closing the editor and reload.

step by step_edit_191104193258284638
step by step_edit_191104193258284638.meta

Game Version:
GOG Galaxy
Platform:
Windows
GOOD, I'M SATISFIED
Satisfaction mark by SeriousToni 2 months ago

EDIT: I found out there is an error, in which the editor doesn't correctly delete my triggers and still uses them (I deleted them in the mighty script, but on "publish and test" it still uses them ingame). I put the file in the attachment. Go to god mode, create some units near the final Hero Gate and attack the Heroes & Gate. Normally it should end the game if you kill the Lord of the Land. But somehow it uses old triggers that print console messages and ends the game if you hurt one of them or the gate. The triggers were already deleted in the mighty script. Still ingame they trigger. At least when I "Publish and Test", even after closing the editor and reload. step by step_edit_191104193258284638.meta
step by step_edit_191104193258284638

Edit - can someone please change the ticket title? It doesn't fit the error and I cannot find out how to edit it

+1
Backlog

Will be looked at during our next bug pass

I'm afraid I've downloaded your map and tried your reproduce steps without encountering the issue. For me the script ran as it is setup in the editor. What puzzles me is that you said you did close and reloaded the map , so I should have had the bug too, but apparently not. If that still happen after the next patch however , I'd like to know :)

Just tried and it did not happen again. I remember restarting the game did not fix this for sure, but since it is now working on my side again, maybe restarting the computer was the fix? I surely don't know and let's just cross thumbs that this will not happen again. :) I am sorry for stealing your time on this one, but I am sure this did not work when I wrote the ticket. Thanks for your help anyway. :)