Different E1 image for Nod/GDI

OrangeNero · Commander **Joined**: 11 Jan 2012

I tried to get a side specific image for the Light Infantry E1 but I failed and from what I read in the Drop pod threads there are various hard codes that prevent this. Is there a way around?

Ixonoclast · Posted: Fri Sep 14, 2012 10:50 am Post subject:

Turn the Light Infantry in a technician with a gun (just make it unbuildable), and make two new Light Infanteries, one for Nod one for GDI.

Lin Kuei Ominae · Seth **Joined**: 16 Aug 2006 **Location**: Germany

The only hardcoded use for the light infantry is the drop pod which takes the unit with the ID [E1].
Every other occurance of E1 is ini-coded, thus easy to change. The only restriction is, that survivor and crew units are used for both sides, thus you should add for these a neutral looking double owned unit like the technician.
rules.ini
-change survivor/pilot/crew/etc unit
ai.ini / aifs.ini
-create a duplicate for E1 dual owned teams and give one the GDI E1 and the other the Nod E1 (of course do the other necessary changes to the teamtypes, so they now point to the correct teams; e.g. GDI to the old team and Nod to the cloned new team)

or take a look at mods like TI, as they have done it already, so you can check their ini codes Wink

_________________
SHP Artist of Twisted Insurrection: Nod buildings

Public SHPs
X-Mech Calendar (28 Mechs for GDI and Nod)
5 GDI, 5 Nod, 1 Mutant, 1 Scrin unit, 1 GDI building

Tools
Image Shaper______TMP Shop______C&C Executable Modifier

CCHyper · Defense Minister **Joined**: 07 Apr 2005

I might add a catch to the DropPod code that checks for the existence of E1 and E2 and if they are not found, just revert to say, the Pilot= entry, and if that's empty, just do nothing.

But of course, I need to actually have time to work on the patch to do that...

Bittah Commander · Posted: Fri Sep 14, 2012 3:48 pm Post subject:

A DropPodInfantry= key would be a lot more preferable.

_________________