[Online] Map XML Wizard

[chipv]

I have added the errors for Territory with killer neutral+bonus and Territory border+bombarding same territory.

I've modified the head post to explicitly say what the Wizard actually does when it encounters warnings and errors on validation.
(Auto correction)

Please can some of you take a look to see if it looks sensible.

[yeti_c]

Here's what I think...

• Error: Territory X has mutiple entries
  Action: Duplicate instances of Territory X are removed.
  Suggested action: Duplicates are renamed X(x++) (i.e. "X(1)", "X(2)")
  
• Error: Position X has component Y which does not exist as a territory
  Action: Position X is removed from positions list.
  Suggested action: Component Y is removed from position X.
  
• Error: Mutiple positions contain component X
  Action: Duplicate instances of positions with Component X are removed from positions list.
  Suggested action: None
  

C.

[chipv]

Here's what I think...

• Error: Territory X has mutiple entries
  Action: Duplicate instances of Territory X are removed.
  Suggested action: Duplicates are renamed X(x++) (i.e. "X(1)", "X(2)")
  
• Error: Position X has component Y which does not exist as a territory
  Action: Position X is removed from positions list.
  Suggested action: Component Y is removed from position X.
  
• Error: Mutiple positions contain component X
  Action: Duplicate instances of positions with Component X are removed from positions list.
  Suggested action: None
  

C.

I'm not sure about the suggested action for 'Territory X has multiple entries' because that would then create territories that
are not contained within the same continent , for which there are no warnings or errors. If X is contained within a objective
or any territory list containing X then you would have a similar dilemma because X(x) won't be.

Something like this could be a genuine mistake or maybe a result of the XML being generated.

That XML would now subsequently be valid (probably with one-way warnings for new territories X(x)) whereas perhaps it should flag some warning.
A corrected XML shouldn't produce any additional warnings.

Agreed with suggested actions on positions. (Can positions contain continents btw - the tutorial implies territories?)

[yeti_c]

Here's what I think...

• Error: Territory X has mutiple entries
  Action: Duplicate instances of Territory X are removed.
  Suggested action: Duplicates are renamed X(x++) (i.e. "X(1)", "X(2)")
  
• Error: Position X has component Y which does not exist as a territory
  Action: Position X is removed from positions list.
  Suggested action: Component Y is removed from position X.
  
• Error: Mutiple positions contain component X
  Action: Duplicate instances of positions with Component X are removed from positions list.
  Suggested action: None
  

C.

I'm not sure about the suggested action for 'Territory X has multiple entries' because that would then create territories that
are not contained within the same continent , for which there are no warnings or errors. If X is contained within a objective
or any territory list containing X then you would have a similar dilemma because X(x) won't be.

Something like this could be a genuine mistake or maybe a result of the XML being generated.

That XML would now subsequently be valid (probably with one-way warnings for new territories X(x)) whereas perhaps it should flag some warning.
A corrected XML shouldn't produce any additional warnings.

Agreed with suggested actions on positions. (Can positions contain continents btw - the tutorial implies territories?)

Hang on - what does the multiple entries error mean?

Your comment seems to imply that it is inside of continents?

I am assuming that it is just in the territory list...

The problem with removing multiples here - is that the multiples could be correct with other work having gone into them - but badly named (copied?) - and you lose data...

Perhaps doing nothing would be better?

Pretty sure positions are territories only.

C.

[MrBenn]

Pretty sure positions are territories only.

C.

They are (at the moment).

So too are objectives (for the time being).

Here's a suggestion: implement an automatic bonus calculator, that uses the formula in one of the spreadsheet ones to calculate bonuses for the continents...

Not something that needs to be done ASAP, but it would be a nice detail...

On the other hand, bonus assignment is fairly context-sensitive and the spreadsheets are always more like recommendations. Ideally this tool would get used after all the squabbling over gameplay specifics is done with.

Yeah, but it would be a nice addition to the tool. They can always be adjusted by hand later on. And it would make deciding bonuses easier, as you wouldn't have to count territories and borders and whatnot for the spreadsheets, but the program would do it for you.

Chip and I had a long discussion about this at the start of this project - we decided to stay away from that coding suggested bonuses into the tool. This was firstly because there are no perfect algorithms to describe the bonus structure for every potential, because the simplest algorithms are devoid of context and complex algorithms struggle to cope with too many permutations. Secondly, the tool is to assist with XML development, which is the last thing a map needs - at this stage it's probably too late to still be overhauling bonus values.

[Kabanellas]

chipv......

YOU ARE THE MAN!!!

[chipv]

Hang on - what does the multiple entries error mean?

Your comment seems to imply that it is inside of continents?

I am assuming that it is just in the territory list...

The problem with removing multiples here - is that the multiples could be correct with other work having gone into them - but badly named (copied?) - and you lose data...

Perhaps doing nothing would be better?

Pretty sure positions are territories only.

C.

Yes your assumption same as mine, in the territory list.
To exemplify what I was saying:

Code: Select all

<continent>
<name>Solar System</name>
<bonus>5</bonus>
<components>
<territory>Earth</territory>
<territory>Mars</territory>
</components>
</continent>

<territory>
<name>Earth</name>
...
</territory>
<territory>
<name>Earth</name>
...
</territory>


If I rename the duplicate territory, then the duplicate won't be automatically included in territory lists containing the original.

So here if I rename the multiple to Earth2 then Solar system will only include Earth. This could easily be missed by the user
as there won't be a validation problem if the multiple is renamed.

I think maybe do nothing on this one, but still flag.

[ender516]

Hang on - what does the multiple entries error mean?

Your comment seems to imply that it is inside of continents?

I am assuming that it is just in the territory list...

The problem with removing multiples here - is that the multiples could be correct with other work having gone into them - but badly named (copied?) - and you lose data...

Perhaps doing nothing would be better?

Pretty sure positions are territories only.

C.

Yes your assumption same as mine, in the territory list.
To exemplify what I was saying:

Code: Select all

<continent>
<name>Solar System</name>
<bonus>5</bonus>
<components>
<territory>Earth</territory>
<territory>Mars</territory>
</components>
</continent>

<territory>
<name>Earth</name>
...
</territory>
<territory>
<name>Earth</name>
...
</territory>


If I rename the duplicate territory, then the duplicate won't be automatically included in territory lists containing the original.

So here if I rename the multiple to Earth2 then Solar system will only include Earth. This could easily be missed by the user
as there won't be a validation problem if the multiple is renamed.

I think maybe do nothing on this one, but still flag.

Is there some way to catch and prevent the creation of a duplicate territory? This wouldn't help with the problem of duplicates in XML that the user loads in, but it gets us part way home.

[yeti_c]

I'm assuming Chip has that as part of his tool - this is purely for loaded XML.#

C.

[chipv]

Is there some way to catch and prevent the creation of a duplicate territory? This wouldn't help with the problem of duplicates in XML that the user loads in, but it gets us part way home.

Yes, I could either flag it dynamically or better still, I think, would be to flatly refuse to show the generated XML until
duplicates have been resolved. That would then mean I can leave alone loaded duplicates, but still validate them as errors.

That means the generated XML would always be correct which is what the intention is.

[ender516]

Is there some way to catch and prevent the creation of a duplicate territory? This wouldn't help with the problem of duplicates in XML that the user loads in, but it gets us part way home.

Yes, I could either flag it dynamically or better still, I think, would be to flatly refuse to show the generated XML until
duplicates have been resolved. That would then mean I can leave alone loaded duplicates, but still validate them as errors.

That means the generated XML would always be correct which is what the intention is.

Ah, an excellent solution. Make your watchword: "Garbage in, perhaps, but never garbage out." Never generate XML which has errors. You might even pop up an "Are you sure?" box before showing the XML if warnings are present, so that the user must actively take responsibility for using XML that might not be kosher.

[captainwalrus]

Perhaps a warning if someone tries to upload and work on a map which is over the size restrictions would be useful?

[chipv]

Just updated the tool (mostly for performance on save and load) but I have corrected the system for
adding positions. There is now a new tab for Positions so you can now add multiple territories per position which
should complete the XML combinations now.

I will take a look at the other suggestions including warnings and errors shortly but will be doing another rather useful addition first.

[natty dread]

will be doing another rather useful addition first.

I hope it'll be the sideways scrolling

[ender516]

I think it would be useful for this tool (or some other) to allow the user to test the XML by assigning territories to players and showing the bonuses achieved. Objectives could be tested in this way as well. This could avoid problems like the one in the Jamaica map where the sugar/slave combinations were carefully planned out, but a small slip made them too generous.