upgrading commander
Moderator: Moderators
- 1v0ry_k1ng
- Posts: 4656
- Joined: 10 Mar 2006, 10:24
upgrading commander
now everyone knows supcom was a piece of junk, but one cool thing was the ability to upgrade your commander with gadgets. how hard would it be to make somthing that had somthing in its build menu that when clicked, makes somthing nanolathe into existance on it, like an extra arm or weapon? there was a 3rd party OTA unit that was a nano tower with no nano attachment. you could choose what head to build on the nanotower and then it built and worked. how hard would it be to do this with a commander? would it be possible to script it so the commander refuses to move while its building on itself etc?
Impossible to do properly though Zwzsg can give you a shopping list of various hacks that could be used for pretending you can upgrade your commander.
The nanotower was two parts out of necessity, OTA didn't allow immobile builders made by con units. Unless you want to make the commander an immobile factory that can produce a unit that blocks its exit and acts as an upgrade you can't use that approach.
The nanotower was two parts out of necessity, OTA didn't allow immobile builders made by con units. Unless you want to make the commander an immobile factory that can produce a unit that blocks its exit and acts as an upgrade you can't use that approach.
TheRegisteredOne way is very nice and well done, but for a more supcommish feel, I would use a commander that can build an arm, then as soon as the nanoframe of the new arm is spawn, the commander auto-grab it and place it inside its shoulder socket while hiding its former arm, that way you see the commander nanolathing itself an arm. Also, it'd show some spinning blue hoops for added effect. That way, exactly like in SupCom, the commander wouldn't need any structure to upgrade, and must stay immobile when upgrading.
When that arm is completly nanolathed, well, I could let it fire by having the commander being an isfirebase=1;, but I feel it wouldn't be good to have such composite unit, because the arm wouldn't be aware of the commander orders, and the commander wouldn't know where the arm wants to aim. So instead I believe it's better that once the new arm is completly nanolathed, the commander get rid of it some way or another and unhide some of its piece that are modelled just like the new arm, and unjam one of its own sixteen weapons.
I could do it however it would take me:
- 3 hours of modelling and texxing
- 30 mins of FBI'ing, TDF'ing, bp'ing, and doing all those other varied small files
- 15 mins of scripting (= doing what actually matters)
- 20 mins of debugging
- 1 hr of making an animated gif of it
And then, most people would simply choose to forget it, two people would say "OMG script hack! We want everything hard coded! It's so much cleaner to have that same code in the exe instead of the script!", one people would scorn it on the ground it create some minor side-effect. Then two month later exactly the same question-thread would be posted here.
When that arm is completly nanolathed, well, I could let it fire by having the commander being an isfirebase=1;, but I feel it wouldn't be good to have such composite unit, because the arm wouldn't be aware of the commander orders, and the commander wouldn't know where the arm wants to aim. So instead I believe it's better that once the new arm is completly nanolathed, the commander get rid of it some way or another and unhide some of its piece that are modelled just like the new arm, and unjam one of its own sixteen weapons.
I could do it however it would take me:
- 3 hours of modelling and texxing
- 30 mins of FBI'ing, TDF'ing, bp'ing, and doing all those other varied small files
- 15 mins of scripting (= doing what actually matters)
- 20 mins of debugging
- 1 hr of making an animated gif of it
And then, most people would simply choose to forget it, two people would say "OMG script hack! We want everything hard coded! It's so much cleaner to have that same code in the exe instead of the script!", one people would scorn it on the ground it create some minor side-effect. Then two month later exactly the same question-thread would be posted here.
I just wish there were more things you could simulate an upgrade of. E.g. can't have a standard radar and an improved radar AFAIK, can't have upgrades that reduce the damage from certain weapons (damagemodifier always applies to all weapons, obviously can't have jetpacks...
Hm, wait, jetpacks may actually be feasible, make the commander grab the jetpack as described and upon a certain command (would unload work for that?) it unloads the jetpack which makes the jetpack load the commander, on another command the jetpack will unload the commander and the commander will grab it again. Of course that still has the drawback of having two units with hitpoints that are kept track of individually until set HEALTH gets implemented (currently isn't supported). Too bad we can't make it so transports spawn with a unit loaded or at least have a script call that spawns a unit so this'll remain limited to upgrading units...
Hm, wait, jetpacks may actually be feasible, make the commander grab the jetpack as described and upon a certain command (would unload work for that?) it unloads the jetpack which makes the jetpack load the commander, on another command the jetpack will unload the commander and the commander will grab it again. Of course that still has the drawback of having two units with hitpoints that are kept track of individually until set HEALTH gets implemented (currently isn't supported). Too bad we can't make it so transports spawn with a unit loaded or at least have a script call that spawns a unit so this'll remain limited to upgrading units...
Well, certain upgrades could be done by actually having the carried object do the upgrade. Improved radar can be accomplished by carrying an improved radar module that is actually functioning as a radar. Ditto jammer, and possibly shield.
For weapons, couldn't you just disable an old weapon and enable a new one for an upgrade? Rather than tweaking values? Annoying, but woudl it work?
For weapons, couldn't you just disable an old weapon and enable a new one for an upgrade? Rather than tweaking values? Annoying, but woudl it work?
OUr beloved community member Optimus Prime should know everything about this subject.
He released the mod War Evolution a while ago, where you have bots that fight eachother, and get new weapons and things like jetpacks when they gain experience.
It is done in such a way that backpacks, barrels and other gadgets appear on the mechs when they reach a new level. Fully funtional and fun to play.
He released the mod War Evolution a while ago, where you have bots that fight eachother, and get new weapons and things like jetpacks when they gain experience.
It is done in such a way that backpacks, barrels and other gadgets appear on the mechs when they reach a new level. Fully funtional and fun to play.
The other comments in this thread mentioned this method, Optimus Prime did implement it. Take a look at this mod:
http://spring.unknown-files.net/file/18 ... ution_1.7/
http://spring.unknown-files.net/file/18 ... ution_1.7/