Posted: Sat Jun 09, 2007 12:18 pm Post subject:
ini files and the veteran system.
With the way veteran and elite is currently handled in the TS/RA2 ini's it is somewhat hard to even see how complete flexibility with units promotions could be archived.
One way is to convert the unit to another unit each time it promots but that could be messy if somone wants 5 levels for each unit resulting in over 500 objects where only 100 realy need to exist.
My suggestion is to make it so anything from the basic unit can be overiden by upgrade steps but still all contained within the same unit deffinition.
An ok suggestion. I agree that key values need to be able to be re-assigned however I seriously do not think 5 veteran systems are needed, I mean, will a unit even get to the 5th system, and then whats the differance between a unit on level 4 and level 5 between a slightly more powerfull weapon?
I think the current Normal - Veteran - Elite system works fine, each level can easily be different from the last making the changes much more noticeable, as long as the veteran / elite system is easily and widely customiseable then thats fine. _________________ QUICK_EDIT
it would , i think, be a bit easier to use that your level2 = {
} _________________ Micro TS
Portable, no campaign, movies or music, just the engine and needed resources for skirmish and lan. QUICK_EDIT
I suppose it comes down to A: which one is easyist to program and B: which one is generaly prefered.
I personally think both my way and the above would work well as it allows an undfined number of levels and for basicly all the tags to be affected. QUICK_EDIT
I suppose it comes down to A: which one is easyist to program and B: which one is generaly prefered.
I personally think both my way and the above would work well as it allows an undfined number of levels and for basicly all the tags to be affected.
indeed, my ini-parser handles that well _________________ Micro TS
Portable, no campaign, movies or music, just the engine and needed resources for skirmish and lan. QUICK_EDIT
Well sure thats good for new weapons that come with veterancy etc, but what about strength, speed, armour, ability to cloak etc?
I think DragonFly's first suggestion was better because that way you could do, for example:
Level2=
{
Cloaked=yes
Amour=superuberconcrete
}
etc, you could even allow the Image tag there so we can make it look different and PhysicalSize, ThreatPosed etc so it can really change and evolve during gameplay. Evolve... yes, it would be an awesome feature for "living" sides and even Tiberium creatures. QUICK_EDIT
Your other way was a lot cleaner, and it means that Judeau doesnt have to add all those separate tags that basically do the same thing. Plus I bet it would be simpler to add more Level1= sections giving us just about as many veterancy levels as we want.
As a side note, Pip and PhysicalSize should be changable. A class 'white' unit might upgrade with veterancy to a class 'red' unit. And same with size, a double barrelled tank might upgrade into a quad barrelled tank with 4 engines and 6 tracks so it wouldnt be the same size.
Furthermore, perhaps Locomotor could be changed. It could upgrade with ability to fly, the ability to go subterranean or turn amphibious. Your first way means the possibilties are almost limitless. QUICK_EDIT
Your other way was a lot cleaner, and it means that Judeau doesnt have to add all those separate tags that basically do the same thing. Plus I bet it would be simpler to add more Level1= sections giving us just about as many veterancy levels as we want.
As a side note, Pip and PhysicalSize should be changable. A class 'white' unit might upgrade with veterancy to a class 'red' unit. And same with size, a double barrelled tank might upgrade into a quad barrelled tank with 4 engines and 6 tracks so it wouldnt be the same size.
Furthermore, perhaps Locomotor could be changed. It could upgrade with ability to fly, the ability to go subterranean or turn amphibious. Your first way means the possibilties are almost limitless.
i was the one who suggested the primary2-3-4-5 way
simply said
you could use Image=NORMAL
Image2=UPGRADED
Locomotor = Hover
Locomotor2 = Fly
get it now ? _________________ Micro TS
Portable, no campaign, movies or music, just the engine and needed resources for skirmish and lan. QUICK_EDIT
heh, though, one problem with that, is that it'd need some troublesome extra ini reading code for a minimal advantage _________________ Micro TS
Portable, no campaign, movies or music, just the engine and needed resources for skirmish and lan. QUICK_EDIT
mayby. But not all code will go into the final product so it isn't that hard to say if it doesn't meet certain minimun standard it won't be incorporated.
eg: Must be in a certain style. Anything that isn't obious must be commented etc. QUICK_EDIT
I was referring more to mods than to official inis.
I understand your concerns, however,I think bad ini coding is the modder's responsibility, I simply allow more stuff. _________________ Micro TS
Portable, no campaign, movies or music, just the engine and needed resources for skirmish and lan. QUICK_EDIT
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
ini files and the veteran system.
