A strange bug on 1.9.11 (now, two questions) - solved

[SkyOne]

Hi,

I am encountering a strange bug on 1.9.11. That is: - The scenario I attach works just fine on BfW 1.9.5 through 1.9.10. Nothing had been wrong to play on those versions. But On 1.9.11, the game turns off before starting the scenario. I tried several times, but still the same result. I know that it occurs when something is incorrect. So the first thing I tried was to clean up the prestart [event] (because of too many codes in it), moved some [unit] tags to the [side] tags and some [event]s out of it. But still the same result. Then I cut off all [event]s, except the prestart [event] just to make it work; however, still the same.

Another strange thing is that nothing is wrong if it reads once. I mean, after I use 1.9.10 to make it start, the game is just fine to play on 1.9.11 from the first turn. Could anyone tell me how/why it happens? I also attach the saving file.

And this is the change-log of 1.9.11: http://svn.gna.org/viewcvs/*checkout*/w ... /changelog
Except this scenario, all scenarios that I made work just fine on 1.9.11 so far (although I still have many more scenarios to test on 1.9.11), and it keeps going after the scenario. I am in a maze in a tunnel...

thanks

[gnombat]

I wonder if it could be this bug:

#19081 [Gna.org]

which is the same as this bug:

#19061 [Gna.org]

[SkyOne]

Thank you so much, gnombat.
I hope it is.
It seems to be fixed, so I wait until 1.9.12 is released.
Hopefully, it doesn't happen to the other add-ons, including my others.
--------------------------

EDIT:
Although the problem above has not been solved because 1.9.12 is not released yet, I have a tiny question regarding to "extra_defines" on main file.

On FoaP campaign, there are two of them:

Code: Select all

    extra_defines=DISABLE_GRAND_MARSHAL 
    extra_defines=ENABLE_ARMAGEDDON_DRAKE

On 1.8.x, only the first one triggered, but on 1.9.x, it seems none of them triggered in the game.


Also, I have another campaign that has not been released on the server, yet. It includes:

Code: Select all

    extra_defines=ENABLE_ARMAGEDDON_DRAKE
    extra_defines=ENABLE_DWARVISH_ARCANISTER

On this one, only the second one triggered on 1.9.x so far.
So as my personal result, we cannot use two "extra_defines" in a campaign. If we do, they work randomly. Is that correct? Or it is just a bug?

I will appreciate if someone responses about it.

thanks

[Iris]

Also, I have another campaign that has not been released on the server, yet. It includes:

Code: Select all

    extra_defines=ENABLE_ARMAGEDDON_DRAKE
    extra_defines=ENABLE_DWARVISH_ARCANISTER

On this one, only the second one triggered on 1.9.x so far.
So as my personal result, we cannot use two "extra_defines" in a campaign. If we do, they work randomly. Is that correct? Or it is just a bug?

The correct behavior should be for the last one to work and this is true for any WML node where there are multiple attributes with the exact same id (the left-hand string, such as ‘speaker’ in the example below):

Code: Select all

[message]
    speaker=narrator
    speaker=Hero
    message= _ "This should be Hero speaking."
[/message]

If you need multiple symbols in extra_defines, provide them as a comma-separated list:

Code: Select all

extra_defines=FOO,BAR,BAZ

[SkyOne]

It really makes sense. (it explains why it works randomly.)
Muchísimas Gracias, shadowmaster. CHI! CHI! CHI!


Also, by testing the first bug (on this thread) on BfW 1.9.12 (that has just been released), it works fine. I appreciate everyone who paid attention the bug.

EDIT: LE! LE! LE!