ROTD variables

[Koror]

Can somone explain me wich variables must i change?

 

[MySpaceBarBroke]

Specific.

 

[Koror]

The one variable with spells from a ligthing Dragon from map 3 to end.
____________
Do you know wich?

 

[HappyTauren]

this will be hard as you will have to redo half of the scripts.

 

[Wolverabid]

According to Daelin:

The problem comes from Darky's coding, more specifically, Nozdramus' abilities. Some of them have local variables with the logical name "lightning". Unfortunately, in 1.12 or maybe earlier/later versions, the object type lightning was introduced by Blizzard. Therefore, the map crashes because the trigger is not disabled (even though you don't select Nozdramus, the bug still exists because the code exists in the map). Only maps 1,2,3 and 5 do not cause the bug, as they do not contain any dragon, and therefore, the spells triggers do not exist.

More explicit explanation of the bug: Since patch 1.12, "lightning" has becomed a reserved name, part of the syntax. Therefore, no variables may be initialised with this name (it is not the case of global variables as their name is udg_name => udg_lightning0).

Also see: RotD (cry for help)

 

[Koror]

Do you know a fixed Version of this campaign? Because i already have a variable named "lightningstrike". I think its the modified version. Or?

 

[HappyTauren]

It will take ages to fix, there are many maps. I might pick a month to redo scripts.

 

[Wolverabid]

Darky never updated his creation after the patch damaged it, so the bugs persist.

Ralle gave it an (unsuccessful) try a while back.

One possible solution would be to install a very early version (pre 1.12) of Warcraft III onto a different computer (or a separate partition of a machine).

By leaving Warcraft III un-patched (not updated) one might be able to complete the campaign without errors.