-
-
Notifications
You must be signed in to change notification settings - Fork 988
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SoF - Last Scenario bugged/not winnable #3099
Comments
Hmm, that's a really odd error; it's just looping over a list of units and killing each one, so that shouldn't change the length of the array as far as I'm aware, unless The easiest fix would probably be to just replace all the If it's the |
Couldn't the [foreach] problem be caused by the fact that it's in a nested event..? Maybe all those cases of |
Hmm, I'm not sure. Certainly, if it's a nested event without |
This merely patches the worst problems (multiple successive [endlevel] calls, inconsistent [endlevel] contents, recursive elf die event, lava fills visually broken); ideally the whole scenario should be rewritten and redesigned. The mask changes only consist of re-sizing them to match the map size.
This merely patches the worst problems (multiple successive [endlevel] calls, inconsistent [endlevel] contents, recursive elf die event, lava fills visually broken); ideally the whole scenario should be rewritten and redesigned. The mask changes only consist of re-sizing them to match the map size.
This merely patches the worst problems (multiple successive [endlevel] calls, inconsistent [endlevel] contents, recursive elf die event, lava fills visually broken); ideally the whole scenario should be rewritten and redesigned. The mask changes only consist of re-sizing them to match the map size. (cherry-picked from commit c0583a1)
https://steamcommunity.com/app/599390/discussions/0/2828702372999695509/
So, someone played until the the Vulcano Scenario (when they all die) and instead of winning after the Vulcano explodes, he loses. (More details in the link.)
The text was updated successfully, but these errors were encountered: