The Hammer of Thursagan: Broken scenario

[Blutkoete]

Hello,

in both the latest SVN and in the 1.10.3 stable version, the 04_Troll_Bridge.cfg file for the Hammer of Thursagan campaign appears to be broken.

The main hero's name is wrong (Hamel instead of Aiglondur) and he starts at level 1 with no experience points, Angarthing isn't there and you can't recall any troops.

Best regards & thank you for your great work,

Blutkoete

[Blutkoete]

STDERR gives me the following when the scenario starts (SVN revision 54515, language German):

Code: Select all

20120701 12:14:10 error engine: A [recall] tag with the following content failed:
id = Angarthing
x = 2
y = 9
20120701 12:14:14 warning engine: cannot show message

That's quite logical, as I can't recall troops, so Angarthing can't be recalled and so he can't talk (show message). I tried to change the name in the cfg file from Hamel to Aiglondur and finished scenario 3 again, but it didn't help.

Just in case this isn't a pure cfg file problem, my operating system is Bodhi Linux (Ubuntu 10.04 with the Enlightenment desktop environment), I'm compiling with scons.

[Anonymissimus]

Are you sure that it happens in 1.10 as well ? Perhaps you've mixed the savegames. Any results are not relevant in this case.
Since this looks like a duplicate of bug #19872. (And if not, that bug overlays this one in any case.)

[Blutkoete]

This really looks like a duplicate. I only checked the 04_Troll_Bridge.cfg file from 10.3 and that file has the wrong name for Aiglondur, then I jumped to conclusions.

So there's the duplicate (the main problem) and then the wrong name for Aiglondur in the 04_Troll-Bridge.cfg file. The latter one is in both the stable version and in SVN.

Thank you for your reply & great work,

Blutkoete

[Anonymissimus]

I only checked the 04_Troll_Bridge.cfg file from 10.3 and that file has the wrong name for Aiglondur, then I jumped to conclusions.

Which is a bug but one which certainly cannot cause loss of the recall list. The default leader, who that name belongs to, is normally ignored and replaced by the engine with the leader from the recall list who happens to miss in this case. Which is why none noticed that wrong name so far.

[Blutkoete]

Ah, okay. So thank you for the name change (saw that one in SVN just now) and good luck for the bug hunt with the recall problem.