2 bugs in scenario editing, and a question

Pocus · #1 February 6th, 2004, 11:17 AM

1. the #scenario command is buggy, and if set, wont allow the players to parametize their game.

2. the #startspell command doesnt work.

now a question: even if I perform some carriages return in the scenario description, all the text is displayed as a unique line under dom. I suppose its an incompatibility with windows?

Pocus · #2 February 6th, 2004, 01:38 PM

I have a scripted scenario based on Aran map (Tomb of the Lizard King is his name). If I can have some answers about these issues, I could release it.

TIA.
Pocus.

Gandalf Parker · #3 February 6th, 2004, 03:33 PM

Im debating if the #scenario thing is a bug. It might be the way they meant scenario to be all along.

I myself used it just to put a pretty star next to my maps saying "this one is special and not just a map" because maybe I had writtena storyline in the description. It didnt always feel right because sometimes the only thing different about it was that it had a star by its name. Now if I declare it a scenario it has to have more than just a storyline in the description. It has to lay out the entire world.
Just a thought.

Targa · #4 February 6th, 2004, 04:44 PM

Quote:

Originally posted by Pocus:
now a question: even if I perform some carriages return in the scenario description, all the text is displayed as a unique line under dom. I suppose its an incompatibility with windows?

Carriage return in which text editor? Notepad, Wordpad, something else?

Pocus · #5 February 6th, 2004, 06:23 PM

Quote:

Originally posted by Targa:

quote:
Originally posted by Pocus:
now a question: even if I perform some carriages return in the scenario description, all the text is displayed as a unique line under dom. I suppose its an incompatibility with windows?

Carriage return in which text editor? Notepad, Wordpad, something else?

notepad. Does I need #10#13, or only #10 ?

Pocus · #6 February 6th, 2004, 06:24 PM

Quote:

Originally posted by Gandalf Parker:
Im debating if the #scenario thing is a bug. It might be the way they meant scenario to be all along.

I myself used it just to put a pretty star next to my maps saying "this one is special and not just a map" because maybe I had writtena storyline in the description. It didnt always feel right because sometimes the only thing different about it was that it had a star by its name. Now if I declare it a scenario it has to have more than just a storyline in the description. It has to lay out the entire world.
Just a thought.

its a bug, as you cant set independant forces (they stay at 3), and you have no script to change it either. Also in 2.02 there was not this problem.

Kristoffer O · #7 February 6th, 2004, 06:35 PM

Quote:

Originally posted by Pocus:
1. the #scenario command is buggy, and if set, wont allow the players to parametize their game.

That is the point of the command. You also get a yellow star.

Kristoffer O · #8 February 6th, 2004, 06:42 PM

Quote:

Originally posted by Pocus:
its a bug, as you cant set independant forces (they stay at 3), and you have no script to change it either. Also in 2.02 there was not this problem.

I do not get it.

Is it impossible to set independent strength in a scenario?

What was it that had changed from 2.02?

Pocus · #9 February 6th, 2004, 08:32 PM

yes its one the difference, I'm rather sure that even with a scenario you could set indep strength and site frequency, etc. in 2.02. This is mostly problematic with the indep settings, as we dont have a scripted command to modify it.

Graeme Dice · #10 February 6th, 2004, 09:38 PM

Quote:

Originally posted by Pocus:
yes its one the difference, I'm rather sure that even with a scenario you could set indep strength and site frequency, etc. in 2.02. This is mostly problematic with the indep settings, as we dont have a scripted command to modify it.

The scenarios have never given you the ability to modify the game settings.