WML error causing the game to hang-up when quitted
Moderator: Forum Moderators
Forum rules
Before reporting issues in this section, you must read the following topic:
Before reporting issues in this section, you must read the following topic:
WML error causing the game to hang-up when quitted
Hello!
While programing a scenario, I tried to use the following WML code:
The code wasn't working, no village was captured, but that's not the point: I exited the campaign and clicked "quit" on the main menu - hang-up. I changed some others thing in my WML code, restarted the game, exited, clicked quit - hang-up. Then I changed my WML code again, deleting the [village] part. There was no hang-up when I clicked "quit".
I think this is strange because the WML code in a scenario config file shouldn't be able to produce problems when quitting the game, should it?
I'm using Windows 7 64bit and Wesnoth 1.8.0, English language pack.
If you want to reproduce the error, put the WML above in a scenario config file (in my case, the coordinates were real villages, but I don't think that's important). Start the scenario, exit the scenario, quit the game.
EDIT: Or that is what is meant by "strange behaviour" in the WML reference.
While programing a scenario, I tried to use the following WML code:
Code: Select all
[village]
x=15,17,23,29
y=27,12,19,19
[/village]
I think this is strange because the WML code in a scenario config file shouldn't be able to produce problems when quitting the game, should it?
I'm using Windows 7 64bit and Wesnoth 1.8.0, English language pack.
If you want to reproduce the error, put the WML above in a scenario config file (in my case, the coordinates were real villages, but I don't think that's important). Start the scenario, exit the scenario, quit the game.
EDIT: Or that is what is meant by "strange behaviour" in the WML reference.