No, I meant that the exp and comp are just part of the name of the ID. Actually the name of the ID doesn't matter. You could call it whatever u want but they use these names to identify what the ship is or what it does but this is just for convenience purposes.aerojet029 wrote: ↑Thu, 6. Dec 18, 22:24 I touched on a few different concepts and the part about expansion and compression came from a quote from the xml script notes. Those notes in the jobs.xml are where i believe it was created in the opening design talk about the game and how it was going to be structured. in the way you have explained it (and correct me if I am wrong) is that they are created through this job, given a tag (Expansion and Compression) and then the factionlogic script takes over how those created units will behave?
interesting
The Factionlogic tag is on all ships and it is so the factionlogic scripts can easily use them because of the tag. The factionlogic scripts should be able to use all of the ships in jobs for their purposes
This here is the important part, and I am not entirely sure on it
Code: Select all
<orders>
<order order="Patrol" default="true">
<param name="range" value="class.cluster"/>
</order>What I don't know is if this is just the default behavior after being built (and then if factionlogic needs it they just take it over) or if this is the defined range it can go always.
) and how much of this mod will be needed. No doubt there will still be a need for it.
![[ external image ]](http://img139.imageshack.us/img139/1769/piratesz.jpg){kind=link}