XML Modifications and Variations

[Shino Tenshi]

Preset Starting Armies

Description: The ability for a mapmaker to specify how many armies any given territory starts off with.

Why It Should Be Considered: This would be useful for making special territories (the Throne in Siege, a flag in 'Capture the Flag', etc) that would give bonuses for owning just the one territory. The territory could be set to have 20 armies on it (neutral, of course, which would require the above update as well).

Lack Label (Mod Use):

[Shino Tenshi]

Limit Bonus for Territories Owned

Description: The ability for mapmakers to limit or eliminate the bonus for the number of territories that you own.

Why It Should Be Considered: This would allow mapmakers to come up with alternative troop economies and control them better. For example, the map I have in mind I would like to make it so that if you don't own your homeworld, you don't get any reinforcements at all. It would be the equivalent of a capitols Risk idea, only instead of being eliminated, you would have a chance to take back your homeworld. The reinforcements would be given for owning your homeworld and any given planet, plus perhaps 'continent' bonuses as well.

Lack Label (Mod Use):

[DiM]

Forgive me if either one of the following two suggestions has already been posted, but there's FAR too many pages to read to make sure I'm not duplicating.

Preset Player Territories

Description: The ability for a mapmaker to specify which players, including neutral, own specific territories in the game.

Why It Should Be Considered: This would allow mapmakers to create maps where players all start off on equal footing. An example would be each player in Chinese Checkers starting off with a triangle and the rest being set to neutral. I have also been considering a space conquest map of sorts involving homeworlds, in which I would need to be able to assign a homeworld, and likely surrounding planets, to each player.

Lack Label (Mod Use):

already proposed

Preset Starting Armies

Description: The ability for a mapmaker to specify how many armies any given territory starts off with.

Why It Should Be Considered: This would be useful for making special territories (the Throne in Siege, a flag in 'Capture the Flag', etc) that would give bonuses for owning just the one territory. The territory could be set to have 20 armies on it (neutral, of course, which would require the above update as well).

Lack Label (Mod Use):

already possible

Limit Bonus for Territories Owned

Description: The ability for mapmakers to limit or eliminate the bonus for the number of territories that you own.

Why It Should Be Considered: This would allow mapmakers to come up with alternative troop economies and control them better. For example, the map I have in mind I would like to make it so that if you don't own your homeworld, you don't get any reinforcements at all. It would be the equivalent of a capitols Risk idea, only instead of being eliminated, you would have a chance to take back your homeworld. The reinforcements would be given for owning your homeworld and any given planet, plus perhaps 'continent' bonuses as well.

Lack Label (Mod Use):

already possible

[cairnswk]

Somebody was looking for this???

[yeti_c]

Ressurrection ahoy...

OK - here's the suggestion to end all suggestions - however it comes with a caveat... and this means all XML programmers will have to be more careful...

OK...

SO the suggestion is to allow Continent names in the components section of a continent...

i.e. from World 2.x

Code: Select all

<continent>
  <name>All of Africa</name>
  <components>
    <component>Mahgreb</component>
    <component>The Horn</component>
    <component>Southern Africa</component>
    <component>Egypt</component>
    <component>Libya</component>
    <component>Cameroon</component>
    <component>Chad</component>
  </components>
  <bonus>3</bonus>
</continent>


(Note this version doesn't override existing continents so 3 is additive)

So how does this help us with the foundry maps...

Supermax
Guards bonus (Gangs would be the same)

Code: Select all

<continent>
  <name>2 Guards</name>
  <components>
    <component>Guard A</component>
    <component>Guard B</component>
    <component>Guard C</component>
    <component>Guard D</component>
    <component>Guard E</component>
    <component>Guard F</component>
    <component>Guard G</component>
    ...
  </components>
  <required>2</required>
  <bonus>0</bonus>
</continent>

<continent>
  <name>4 Guards</name>
  <components>
    <component>Guard A</component>
    <component>Guard B</component>
    <component>Guard C</component>
    <component>Guard D</component>
    <component>Guard E</component>
    <component>Guard F</component>
    <component>Guard G</component>
    ...
  </components>
  <required>4</required>
  <bonus>0</bonus>
</continent>

<continent>
  <name>6 Guards</name>
  <components>
    <component>Guard A</component>
    <component>Guard B</component>
    <component>Guard C</component>
    <component>Guard D</component>
    <component>Guard E</component>
    <component>Guard F</component>
    <component>Guard G</component>
    ...
  </components>
  <required>6</required>
  <bonus>0</bonus>
</continent>

<continent>
  <name>Warden & 2 Guards</name>
  <components>
    <component>Warden</component>
    <component>2 Guards</component>
  </components>
  <bonus>2</bonus>
</continent>

<continent>
  <name>Warden & 4 Guards</name>
  <components>
    <component>Warden</component>
    <component>4 Guards</component>
  </components>
  <overrides>
    <override>Warden & 2 Guards</override>
  </overrides>
  <bonus>4</bonus>
</continent>

<continent>
  <name>Warden & 6 Guards</name>
  <components>
    <component>Warden</component>
    <component>6 Guards</component>
  </components>
  <overrides>
    <override>Warden & 2 Guards</override>
    <override>Warden & 4 Guards</override>
  </overrides>
  <bonus>6</bonus>
</continent>


Iraq!
Mahdi bonus

Code: Select all

<continent>
  <name>City A - Mahdi</name>
  <components>
    <component>City A</component>
    <component>City A Mahdi</component>
  </components>
  <bonus>0</bonus>
</continent>

<continent>
  <name>City B - Mahdi</name>
  <components>
    <component>City B</component>
    <component>City B Mahdi</component>
  </components>
  <bonus>0</bonus>
</continent>

<continent>
  <name>City C - Mahdi</name>
  <components>
    <component>City C</component>
    <component>City C Mahdi</component>
  </components>
  <bonus>0</bonus>
</continent>
...

<continent>
  <name>Mahdi Bonus</name>
  <components>
    <component>City A - Madhi</component>
    <component>City B - Madhi</component>
    <component>City C - Madhi</component>
    ...
  </components>
  <required>4</required>
  <bonus>7</bonus>
</continent>


Al Qaeda Bonus

Code: Select all

<continent>
  <name>City A - Al Qaeda</name>
  <components>
    <component>City A</component>
    <component>City A Al Qaeda</component>
  </components>
  <bonus>0</bonus>
</continent>

<continent>
  <name>City B - Al Qaeda</name>
  <components>
    <component>City B</component>
    <component>City B Al Qaeda</component>
  </components>
  <bonus>0</bonus>
</continent>

<continent>
  <name>City C - Al Qaeda</name>
  <components>
    <component>City C</component>
    <component>City C Al Qaeda</component>
  </components>
  <bonus>0</bonus>
</continent>
...

<continent>
  <name>2 Al Qaeda Cities</name>
  <components>
    <component>City A - Al Qaeda</component>
    <component>City B - Al Qaeda</component>
    <component>City C - Al Qaeda</component>
    ...
  </components>
  <required>2</required>
  <bonus>3</bonus>
</continent>

<continent>
  <name>4 Al Qaeda Cities</name>
  <components>
    <component>City A - Al Qaeda</component>
    <component>City B - Al Qaeda</component>
    <component>City C - Al Qaeda</component>
    ...
  </components>
  <required>4</required>
  <overrides>
    <override>2 Al Qaeda Cities</override>
  </overrides>
  <bonus>6</bonus>
</continent>


US Bonus

Code: Select all

<continent>
  <name>City A - US</name>
  <components>
    <component>City A</component>
    <component>City A US</component>
  </components>
  <bonus>1</bonus>
</continent>

<continent>
  <name>City B - US</name>
  <components>
    <component>City B</component>
    <component>City B US</component>
  </components>
  <bonus>1</bonus>
</continent>

<continent>
  <name>City C - US</name>
  <components>
    <component>City C</component>
    <component>City C US</component>
  </components>
  <bonus>1</bonus>
</continent>
...

<continent>
  <name>City A - US with Green Zone</name>
  <components>
    <component>City A - US</component>
    <component>Green Zone</component>
  </components>
  <bonus>1</bonus>
</continent>



Age Of Merchants
Resource Pair to Foreign Market bonus

Code: Select all

<continent>
  <name>Top left Harbours</name>
  <components>
    <component>Puerto Allegre</component>
    <component>Puerto Esperanza</component>
  </components>
  <required>1</required>
  <bonus>0</bonus>
</continent>

<continent>
  <name>Top Middle Harbours</name>
  <components>
    <component>Puerto Castillo</component>
    <component>Puerto Tiago</component>
  </components>
  <required>1</required>
  <bonus>0</bonus>
</continent>

<continent>
  <name>Hat & Clothes</name>
  <components>
    <component>Chiuso</component>
    <component>Reyes</component>
  </components>
  <bonus>0</bonus>
</continent>

<continent>
  <name>Hat & Clothes to Manchia Market</name>
  <components>
    <component>Hat & Clothes</component>
    <component>Manchia</component>
    <component>Top Left Harbours</component>
    <component>Top Middle Harbours</component>
  </components>
  <bonus>2</bonus>
</continent>


Now the Caveat

Code: Select all

<continent>
  <name>A</name>
  <components>
    <component>Country A</component>
    <component>Country B</component>
    <component>B</component>
  </components>
  <bonus>0</bonus>
</continent>

<continent>
  <name>B</name>
  <components>
    <component>Country C</component>
    <component>Country D</component>
    <component>A</component>
  </components>
  <bonus>2</bonus>
</continent>


As you can see this last example would cause an infinite loop... as both continents reference each other... This would need checking for in the XML tester... and by us Foundry XML gurus...

C.

[Coleman]

There are cases when continents and territories have the same name, this would no longer allow that. Why can't we mix component and collection tags in the same continent?

[yeti_c]

There are cases when continents and territories have the same name, this would no longer allow that.

Yes - Names of Continents and Territories would have to be unique - we may have to go back and change some XML for this - but that would be simple...

We wouldn't need a rewrite on XML where the continents were the same name though - as at present they are not referenced in any Continents in the XML.

Why can't we mix component and collection tags in the same continent?

I'm not sure what you mean?

C.

[mibi]

RESETTING NEUTRAL TERRITORIES

Description: Have it so a territory with a starting neutral can revert or reset back to that starting neutral each round. So that if a player A conquers territory Z that has 2 neutral armies and occupies it with 3 armies. Atthe end of the round or beginning of the next round, the 3 player armies are reverted back to 2 neutral armies.

Why is it needed? That territory can act as a stationary trigger for other xml ideas or bonuses. Other wise, a player would attack the neutral trigger territory and not be able to attack it again because they already own it. Ok that doesn't make much sense, here is how it might actually work for a map.

Lets say you have a map designed for Fog of War or something, and you have one territory that is like a 'crystal ball' and it can bombard any territory on the map, or some predefined territories. This crystal ball would allow you to see through the fog during your turn, but not after since it reverts back to neutral. I dunno, i think it would a cool idea and have more uses than I can think of.

[WidowMakers]

RESETTING NEUTRAL TERRITORIES

Description: Have it so a territory with a starting neutral can revert or reset back to that starting neutral each round. So that if a player A conquers territory Z that has 2 neutral armies and occupies it with 3 armies. Atthe end of the round or beginning of the next round, the 3 player armies are reverted back to 2 neutral armies.

Why is it needed? That territory can act as a stationary trigger for other xml ideas or bonuses. Other wise, a player would attack the neutral trigger territory and not be able to attack it again because they already own it. Ok that doesn't make much sense, here is how it might actually work for a map.

Lets say you have a map designed for Fog of War or something, and you have one territory that is like a 'crystal ball' and it can bombard any territory on the map, or some predefined territories. This crystal ball would allow you to see through the fog during your turn, but not after since it reverts back to neutral. I dunno, i think it would a cool idea and have more uses than I can think of.

I actually need this for my next two levels of Draknor. I want to have trap doors, auto shutting doors, and portals.

I just did not suggest it yet because I am about 3 months away from starting the map.

WM

[Herakilla]

SENTRY TERRITORIES

description: coding that allows a territory to border but not attack another territory. all it can do is see the other territory. would be awesome to have in like medieval maps (towers that can see around them) or futuristic maps (a sensor array perhaps?) or maybe you have a territory thats next to another and is at the top of a cliff above another or something that would enable it to see the other territory but it cant attack

Why is it needed? wouldnt be awesome for fog of war? you could really get some strategy going by making it important to know where your opponents armies and stuff are.

[Herakilla]

RESETTING NEUTRAL TERRITORIES

Description: Have it so a territory with a starting neutral can revert or reset back to that starting neutral each round. So that if a player A conquers territory Z that has 2 neutral armies and occupies it with 3 armies. Atthe end of the round or beginning of the next round, the 3 player armies are reverted back to 2 neutral armies.

Why is it needed? That territory can act as a stationary trigger for other xml ideas or bonuses. Other wise, a player would attack the neutral trigger territory and not be able to attack it again because they already own it. Ok that doesn't make much sense, here is how it might actually work for a map.

Lets say you have a map designed for Fog of War or something, and you have one territory that is like a 'crystal ball' and it can bombard any territory on the map, or some predefined territories. This crystal ball would allow you to see through the fog during your turn, but not after since it reverts back to neutral. I dunno, i think it would a cool idea and have more uses than I can think of.

what about a variation of this that it only resets if a player has just 1 army on it, this could be so awesome with maps like age of might if you only have autodeploy bonuses so you must keep a string of armies as a supply line to fortify your troops through to the front line. plus age of might would be more fun if you couldnt see where your opponent went lol

[yeti_c]

I know my idea wasn't sexy like your ideas... it was more "under the hood" stuff!!

But can someone discuss that too?!

C.

[Herakilla]

I know my idea wasn't sexy like your ideas... it was more "under the hood" stuff!!

But can someone discuss that too?!

C.

alright you want me to?

basically what you want is for continents to be a territory that consists of several territories at once? i can see how this would help programming it and save time there, also it might look better on the game log but i dont think there will be any difference unless you use overrides so only a couple bonuses show but they consist of all the bonuses you have.

now discuss mine!

[yeti_c]

I know my idea wasn't sexy like your ideas... it was more "under the hood" stuff!!

But can someone discuss that too?!

C.

alright you want me to?

basically what you want is for continents to be a territory that consists of several territories at once? i can see how this would help programming it and save time there, also it might look better on the game log but i dont think there will be any difference unless you use overrides so only a couple bonuses show but they consist of all the bonuses you have.

now discuss mine!

You're almost right - there are several maps in the foundry that don't work at the moment with the current XML - this solves that problem...

With a recursive structure like this I'm pretty sure almost any form of continents is possible - especially with the overrides and required tags.

Your idea is a good one... it could be a tag called <visible range>2 i.e. this territory can see 2 territories beyond... altho that might be a bit weird as for instance in AOR - if you were next to a dock - then you'd see what the Dock can see...

Perhaps a better tag would be...

Code: Select all

<visibles>
  <visible>territory</visible>
</visibles>

Where you define exactly what each territory could see.

C.

[Herakilla]

the second part you put down is exactly what i meant lol, it would mean more work but you could really use it for magic and future technology

[Coleman]

Why can't we mix component and collection tags in the same continent?

I'm not sure what you mean?

C.

I mean you have a required portion and an optional portion in the same continent. Like you must have the ones that are components and then the indicated amount of the collection.

[yeti_c]

Why can't we mix component and collection tags in the same continent?

I'm not sure what you mean?

C.

I mean you have a required portion and an optional portion in the same continent. Like you must have the ones that are components and then the indicated amount of the collection.

But that wouldn't solve the Iraq! problem?

C.

[benjikat]

I think yeti's idea of allowing continents as components of a greater continent is very elegant.

How about making the differences explicit?:

<continent>
<name>All of Africa</name>
<components>
<componentContinent>Mahgreb</componentContinent>
<componentContinent>The Horn</componentContinent>
<componentContinent>Southern Africa</componentContinent>
<componentTerritory>Egypt</componentTerritory>
<componentTerritory>Libya</componentTerritory>
<componentTerritory>Cameroon</componentTerritory>
<componentTerritory>Chad</componentTerritory>
</components>
<bonus>3</bonus>
</continent>

...making it easier to write and check.

[yeti_c]

I think yeti's idea of allowing continents as components of a greater continent is very elegant.

How about making the differences explicit?:

<continent>
<name>All of Africa</name>
<components>
<componentContinent>Mahgreb</componentContinent>
<componentContinent>The Horn</componentContinent>
<componentContinent>Southern Africa</componentContinent>
<componentTerritory>Egypt</componentTerritory>
<componentTerritory>Libya</componentTerritory>
<componentTerritory>Cameroon</componentTerritory>
<componentTerritory>Chad</componentTerritory>
</components>
<bonus>3</bonus>
</continent>

...making it easier to write and check.

This is a good idea actually - as this would mean that we wouldn't have to go back and change any old XML...

Although you would leave territory as merely <component> and then have <componentContinent> added... or of course we can use textpad to do a global search and replace (like we did when we changed country to territory)

C.

[militant]

Do all this disscusion mean the update is coming soon

[Coleman]

compcont would be fine wouldn't it?

[Coleman]

Why can't we mix component and collection tags in the same continent?

I'm not sure what you mean?

C.

I mean you have a required portion and an optional portion in the same continent. Like you must have the ones that are components and then the indicated amount of the collection.

But that wouldn't solve the Iraq! problem?

C.

No, but it would solve the SUPERMAX one, which I don't want to ignore.

[yeti_c]

Why can't we mix component and collection tags in the same continent?

I'm not sure what you mean?

C.

I mean you have a required portion and an optional portion in the same continent. Like you must have the ones that are components and then the indicated amount of the collection.

But that wouldn't solve the Iraq! problem?

C.

No, but it would solve the SUPERMAX one, which I don't want to ignore.

But my new solution solves BOTH Iraq! & Supermax! in one go?! (Did you see my examples?)

And would also allow a rewrite of other big XMLs... (AOM & AOR to mention but 2)

C.

[yeti_c]

For a perfect example of how my new updated code works - check out the Age of Merchants thread in FF...

http://www.conquerclub.com/forum/viewtopic.php?t=14626&postdays=0&postorder=asc&start=1185

C.

[Coleman]

After Update

Code: Select all

---removed---


That blew my mind and in its rebirth all I have to say is bloody brilliant.

Edit: logic for those that didn't see it or may not get it:

Code: Select all

If you have hats and clothes
and one of the northwestern ports
and one of the northern ports
then you receive 2 for Hats and Clothes to Manchia Market

It’s really that simple to us and through the ability to add continents and collections into other continents and collections it becomes that simple to code.

Through this kind of logic, like yeti_c I believe we can do almost anything. This one update would solve SUPERMAX and Iraq! simultaneously.

Some old xml files may need to be (and some even should be) rewritten as I am aware of a few situations where continents and territories share names and many situations where this would greatly improve the efficency of xml code.

yeti_c has expressed elsewhere possibly taking on that project for lack if he is willing to change his side of this to accomidate this change. I would be willing to do some as well if yeti_c doesn't want to do all of them himself.