PROJECT: Playtest (the 4th Thread)

[Ekmek]

The Upgrading code is still in there but the unit.txt no longer has the ' UpgradeTo UNIT_PIKEMAN ' and stuff like that.

Likewise with te DiffDb I had it tweaked to make a Very Hard game actually VERY HARD (maybe too hard?)

there seems to be some contention I guess I could start a poll but it might be just easier to create the AE mod scenario folder and stick those files there so those that want upgrading and a brutal AI would just start a new game through the scenario.


But I'm interested to hear some thoughts on this.


PS I think I found a way to make Govt City limits to vary depending on map size. I'm thinking of making it a Const.txt option

[Tamerlin]

Originally posted by E
The Upgrading code is still in there but the unit.txt no longer has the ' UpgradeTo UNIT_PIKEMAN ' and stuff like that.

As far as I know the upgrade paths are written along with the code, not in the unit.txt file. Why not keep the updater like it was before ? An independent Updater2.slc file with the code (included in the default Script.slc file) and an independent Updater2_str.txt file imported in the Strings.txt of the specific language folder.

Much more simpler.

...there seems to be some contention I guess I could start a poll but it might be just easier to create the AE mod scenario folder and stick those files there so those that want upgrading and a brutal AI would just start a new game through the scenario.

I agree with the Updater2 but I don't with a brutal AI.

PS I think I found a way to make Govt City limits to vary depending on map size. I'm thinking of making it a Const.txt option

Why not ! But I don't think we should change the rule.

[Tamerlin]

I have added the Updater2 again as described above.

Is there a chance of conflict between the two codes (the hardcoded one and the code added through an independent slic file) ?

[Ekmek]

Originally posted by Tamerlin
I have added the Updater2 again as described above.

Is there a chance of conflict between the two codes (the hardcoded one and the code added through an independent slic file) ?

Not sure its never been tried. The benefit of the hard code is that you just add the line UpgradeTo followed by the Unit. You add additional lines so you create an upgrade path. As far as I know the Slic doesn't let you have an immediate jump from warrior to infantryman (although expensive) but you have to go through each phase.

a note on my code don't put in the upgradeto units that are available at the same time (ie paratrooper and marine being two separate upgradeto lines in warrior for example) it crashes the game because the game cant decide which.

[Tamerlin]

Originally posted by E

... a note on my code don't put in the upgradeto units that are available at the same time (ie paratrooper and marine being two separate upgradeto lines in warrior for example) it crashes the game because the game cant decide which.

Someone other than me will have to do it as I don't have any programming skill.

Just a question: are the upgrade paths the ones I designed for the Updater2 or are they different?

[Ekmek]

programming skill? you mean fo rthe crash?

for my upgrading all you need to do is ad the line in UNITS.TXT to the unit of your choice with UpgradeTo followed by the unit name. the cost is deducted based on shield difference times your govt's rush gold cost.

i.e for warrior:
UpgradeTo UNIT_SWORDSMAN
UpgradeTo UNIT_LEGION
UpgradeTo UNIT_INFANTRYMAN
UpgradeTo UNIT_MACHINE_GUNNER
UpgradeTo UNIT_HOVER_INFANTRY

also when it says upgradeto then it makes the current unit unavailble/obsolete

Better yet i just added my units.txt that has the upgrading in it. note i added a few extra units like legion and elephant warrior but this was for using resources.

[Tamerlin]

Originally posted by E

a note on my code don't put in the upgradeto units that are available at the same time (ie paratrooper and marine being two separate upgradeto lines in warrior for example) it crashes the game because the game cant decide which.

Thanks for the unit.txt and the instructions, this will allow me to create an upgrade path similar to the Apolyton Pack.

About your quote, do you mean that in the case described above you have to create two different lines or that you should not create two lines for units available at the same time. I suppose that this is the second case but I want to be sure.

[Tamerlin]

Standard APOL Upgrade Paths

I have followed E's instructions and changed the latest AE Units.txt according to the Upgrade Paths previously designed for the Apolyton Pack which is compatible with the Standard Game.

Here is the Units.txt file with the updated Upgrade Paths :

[Tamerlin]

Unit Upgrader

E,

I have tested the Upgrader paths through the Upgrade Paths written in the Units.txt and it works perfectly.

But I have a few comments :

1 - There isn't any pop-up window to warn me that I am upgrading a unit. If my first intention was to put a unit asleep, I am in trouble as my treasury is reduced without having any opportunity to say "no".

2 - There isn't any pop-up window to tell me the cost of an upgrade.

3 - Though a specific button would be the best solution, I still need to know the cost of an upgrade. Why not through a "pop-up comment" when the cursor is over the upgrade button.

[Ekmek]

Awesome work Tamerlin.

I had something to say a unit was being upgraded but a pop-up window is a good idea. I think I know what I have to do. It involves adding it to script.slc. and then make a slic function called unit upgrade. the last part might be a bit tougher because I tried a few functions for it before.

but I'm glad it works and it cuts down on slic.

PS I see that the warrior and swordsman don't have upgrade units is that right?

[Tamerlin]

Originally posted by E
PS I see that the warrior and swordsman don't have upgrade units is that right?

When the upgrade paths were designed we had some talks through a thread.

About the warrior, some players said that the Warriors and the Hoplites don't have the same purpose. The Warrior should not be upgraded to a Hoplite as it would loose its most interesting feature : a two square vision that makes it ideal for early exploration and frontier observation.

Though the warrior should not be allowed to upgrade to Hoplites, I think that we should allow it to upgrade to Pikemen and so on (it would loose its 2 squares vision though). What do you think about it?

About the Swordsman, it was decided that it was a kind of special assault unit without any equivalent elsewhere and that it should not be upgraded. As far as I am concerned, I think that the swordsman should be allowed to upgrade to Infantryman and so on. What do you think about it ?

As soon as some opinions are given, I will do the needed corrections.

[Tamerlin]

Originally posted by E
Awesome work Tamerlin.

Thank you E but I am not sure to deserve such congratulations. You, programmers, are the one doing the real work.

I had something to say a unit was being upgraded but a pop-up window is a good idea. I think I know what I have to do. It involves adding it to script.slc. and then make a slic function called unit upgrade. the last part might be a bit tougher because I tried a few functions for it before.

I think that the pop-up window is the easier way to give the necessary warnings. It is not the easier way for a player when he has to upgrade a lot of units but it is something that we, turn based empire builders, are used to.

but I'm glad it works and it cuts down on slic.

Keep on the good work, E !

[Ekmek]

I agree with both your suggestions. The code also allows the AI to upgrade if it has the money so I'd hate to see old units running around in the modern age, one of my biggest hates about civ3

[Tamerlin]

Originally posted by E
I agree with both your suggestions. The code also allows the AI to upgrade if it has the money so I'd hate to see old units running around in the modern age, one of my biggest hates about civ3

Thanks E !

What are the others thinking about it ? Should we allow the Warrior to upgrade to Pikemen and so on and the Swordsman to Infantry and so on?

[Maquiladora]

I remember some discussion about the upgrade paths, they should have the same roles (in whatever age) between units upgrading to each other IMO. Like no upgrading between defense and attack units. It might also help the AI to keep its particular units in the right place after upgrading.

I havent actually played the playtest with the new units E added though, maybe once last year, so id have to play it again to see what are the upgrade paths. Also with the tweaked diffDB etc.