Well, good luck! Post again if needed. About the other thread. You may think it was a different subject, but it`s the same actually. You learning how to implement a new unit with all there is to it.

You need to develope a basic understanding of how these files work and after that you`ll find it easier to understand the rest.
EDIT: About the units cards. Do you have new ones for them? If you do you`d need to edit some text, otherwise the vanilla files will be loaded because those are packed. Basically you edit the entry in export_units and change what is in the brackets. For example:
Code:
¬----------------
{new_roman_hastati} Hastati
{new_roman_hastati_descr}
Hardy\nSapping Ability\n\nHastati are among the younger men in an early Republican Legion, and form the front line in any battle. They are supposed to wear down an enemy and hold him before the next Roman battle line attacks and carries on the fight. They are, as a result, capable troops in their own right.\n\nThey are armed with two pila that are thrown at the enemy at close range before they close to fight hand-to-hand. They are equipped with a sword, a bronze helmet, a large shield and a breastplate. The pilum (plural, pila) is a cleverly designed spear with a soft iron shaft behind the point; it bends on impact so that it can’t be thrown back and if it’s stuck in someone or something it is a real hindrance to movement.\n\nHistorically, hastati spent their own money on their equipment and often couldn’t afford anything much better. This, along with the age and property requirements, was why they fought as hastati.
{new_roman_hastati_descr_short}
Hastati fight as the leading edge of a Legion, wearing the enemy down for the next wave of attackers.
¬----------------
Then go to the EDU entry and change the line for the dictionary to reflect the new name in export_units. For example:
Code:
type roman hastati
dictionary new_roman_hastati ; Hastati
category infantry
class light
voice_type Light_1
soldier roman_hastati, 40, 0, 1
attributes sea_faring, hide_forest, can_sap
formation 1, 2, 2, 3, 4, square
stat_health 1, 0
stat_pri 11, 2, pilum, 35, 2, thrown, blade, piercing, spear, 25 ,1
stat_pri_attr prec, thrown ap
stat_sec 7, 2, no, 0, 0, melee, simple, piercing, sword, 25 ,1
stat_sec_attr no
stat_pri_armour 5, 4, 5, metal
stat_sec_armour 0, 1, flesh
stat_heat 3
stat_ground 2, 0, 0, 0
stat_mental 6, normal, trained
stat_charge_dist 30
stat_fire_delay 0
stat_food 60, 300
stat_cost 1, 440, 170, 50, 70, 440
ownership roman
You then need to rename the ui cards proper. They need to contain the name of what is next to the dictionary entry in EDU. In the example above:
new_roman_hastati
You need to have two cards. One should be named according to the example:
new_roman_hastati_INFO.tga
and it goes in this location:
Rome - Total War\data\UI\UNIT_INFO\ROMANS_JULII
and the other should be named:
#new_roman_hastati.tga
and it goes in this location:
Rome - Total War\data\UI\UNITS\ROMANS_JULII
Note: those locations do not exist in the RTW vanilla folder so you`ll have to create them.