Cant override <SystemTypes> in an extension?

Post ideas & suggestions you have pertaining to the game here.
Post Reply
User avatar
Periculi
Fleet Officer
Fleet Officer
Posts: 1282
Joined: Sat Oct 13, 2007 7:48 pm
Location: Necroposting in a forum near you

I found this:
george moromisato
Posted: Sat Jan 26, 2008 7:53 am

The ones that work as of 0.98d are:
<DockScreen>
<EncounterTable>
<Globals>
<Image>
<ItemTable>
<ItemType>
<ShipClass>
<ShipEnergyField>
<Sound>
<Sovereign>
<SpaceEnvironmentType>
<StationType>
<SystemType>
And decided to try to place the systems from SS topo 4 into an extension.

I left the UNID at the top of Transcendence, because it wouldn't load without the UNID already there due to being referenced in Transcendence.xml topology- so, the UNID needed to stay in trans.

Thinking this solved it, I loaded the game again. It was unable to build the star systems and exited the game.

I checked and played around with the <tags> to see if something wasn't properly structured.

I can't seem to place the <systemtype> in an extension. Am I missing something?

I tried adding <SystemTypes> to no effect.

It works to put the systems in a Module just fine.
F50
Fleet Officer
Fleet Officer
Posts: 1004
Joined: Sat Mar 11, 2006 5:25 pm

your quote is inconsistent: <systemtype> <SystemTypes>

one caps, one no caps, one s, one no s. Furthermore, your list says <SystemType> is correct.

Perhaps you could edit so I am not confused?
User avatar
Periculi
Fleet Officer
Fleet Officer
Posts: 1282
Joined: Sat Oct 13, 2007 7:48 pm
Location: Necroposting in a forum near you

Within the bowels of Transcendence XML, the structure of the systems is defined in the <SystemTypes> tag with systems being held inside the <SystemType> tags.

Thusly:

Code: Select all

<SystemTypes>
  <Tables>
  </Tables>
<SystemType>
  [...info info info]
</SystemType>

<SystemType>
[...info info info]
</SystemType>

</SystemTypes>
When I placed the systems into the extension, I left the <Tables> in Trans.xml inside a <SystemTypes> tag, then placed the <SystemType> definitions into the extension as per usual arrangements for extensions.

That didn't work, so I placed a <SystemTypes> tag around the entire set of <SystemType> tags in the extension to see if it made a difference. Which it did not.

The first thing I did was to try the tag listed to see if it would work if the <SystemType> was NOT defined in Transcendence. It just won't work for me.

At any rate, I think it works fine as a module. In fact, I have slimmed down my Trans.xml in order to accomodate the 600+ nodes that are in the topo tree now. I put the core items, globals, and dockscreens all in their own modules, as well as the 90+ systems used by the ss topology.
User avatar
Betelgeuse
Fleet Officer
Fleet Officer
Posts: 1920
Joined: Sun Mar 05, 2006 6:31 am

F50, transcendence xml files are case insensitive so SystemTypes is the same as SyStEmTyPeS and systemtypes
Crying is not a proper retort!
F50
Fleet Officer
Fleet Officer
Posts: 1004
Joined: Sat Mar 11, 2006 5:25 pm

Ah, ok. I am used to strongly typed languages like C where AI is different from ai which is different from Ai so I didn't think of that possibillity.
Post Reply