Heart of Gold lvl1; Infinite templar spawn (ocured after saving)
Hello everyone,
While playing lvl 1 of the Heart of Gold campaign I've encountered a quite peculiar bug.
Given, the bug isnt directly blocking me finishing the level/achievement by simply restarting
the it and not using my save file (which aparently made the bug apear) but i think it would be nice if the team could find time to get behind it the problem to save other players some frustration
Now to the problem that apeared:
While i tried to get the "Stairway to Heaven" achievement i saved my progress in the midle of the level and reloaded the game later. by then, I already destroyed the Gateway where Mandalf first respawns from and the one which is located in the lava-river.
Now after reloading, the first mentioned destroyed Gateway (which i already claimed)
started spawning
an near INFINITE WAVE of LEVEL 2 TEMPLARS !!!
only after Mandalf respawned (i think he was lvl3 by then) the spawning stopped.
That was sadly of litle use since not only was i faced with a force of about 350 templars
which were crusading all my sentinels to death, but they also encumbered the game so much that it crashed one minute after.
Details:
An interesting sideffect to mention: another strange thing that was going on was that some unknown entety was using the lightning spell on my minions but on my own tiles.
(this very much confused me, since you dont play against another Underlord in level 1 [maybe not an official one but something that is set up in the missions mechanics that went wild? idk ])
-tiles around, aswell as the Gateway itself (Mandalfs first respawn point)
were claimed by me, the second Gateway, too
- order Gateways destroyed 1. Mandalf first respawn 2. lava-river Gateway
-game was saved after Mandalf died
I think this bug could become agrovating if it ocurs during hunting for time achievements
but i don't know if the problem ocurs often, haven't yet found someone who encountered the same bug and maybe i just became quite unlucky
dlc1_campaign_level1_name_20160712165109
I hope i did everything right, especialy since i never reported bug before and because english isn't my native language
If any information is needed (or in case i didnt took the right safe file, still not sure if i did it right)
just contact me per e-mail, and thanks in advance for fixing the problem ;)
♫ I don't know what I've been told ♫
♫ I don't know what I've been told ♫
♫But guarding Gateways won't get old♫
♫But guarding Gateways won't get old♫
(they just marched around there for no reason) ¯\_(ツ)_/¯
Hi Bulbaner,
That's a truly impressive bug, thanks for the in depth report on it and don't worry it appears everything is right from what I can see. Especially pleased that you submitted a save file.
I had a chat with the coders and it seems we have seen this once before but only once and we could never replicate it. We think that the issue might be fixed in the next patch anyway due to another fix we implemented but we'll take what's here and check what we can find anyway.
Essentially what's happening is for some reason Mandalf has failed to spawn at the correct timing, as part of the script where he spawns his guards are also spawned, because the scripting engine detects the fail it attempts to loop in order to reach a success state. So it loops the spawning of the guard until whatever is preventing the Mandalf spawn is gone and it successfully spawns him.
Anyway I'll pass this on now, but you may very well find this will be fixed in the upcoming patch! :)