I feel I should apologize for the current station spawning system, since I’m the one who pushed for it. It was the only way to keep both George’s and Wolfy’s stations from showing all over The Backroads in places they had no business being. <.< >.> <.<;
…Aaand I guess that means it’s up to me to help out on this…
Unfortunately, it’s not really easy to limit topology to being
mostly Semesta stations, it tends to be either standard distribution or nothing at all. Probably the easiest way to go about that would be to make stations that inherit from the vanilla stations, but change the encounter frequencies to make them less common.
As for the <TopologyProcessor> and attribute part, the first thing is to get the processors set up. It’ll actually be slightly trickier on this due to the even number of systems, since it makes the territory slightly lopsided no matter which node you start from.
Code: Select all
<SystemMap unid="&tpSemestaSpace;"
displayOn="&smHumanSpace;"
>
<!-- Any system within two gates of Sokyo or Welborn. -->
<TopologyProcessor priority="primaryColony">
<System attributes="semestaSpace">
<Criteria>
<DistanceTo nodeID="Sokyo" min="0" max="2"/>
</Criteria>
</System>
<System attributes="semestaSpace">
<Criteria>
<DistanceTo nodeID="Welborn" min="0" max="2"/>
</Criteria>
</System>
</TopologyProcessor>
</SystemMap>
This will have one system of overlap between the two at Banda, but that’s fine; as long as all of the systems get marked as “semestaSpace”, it’ll all work.
To make the Semesta stations appear in only the marked systems, the following needs added to in the <Encounter> tag:
The vanilla-inherited station copies would need a slightly different version of that to keep them limited to only the new systems:
Code: Select all
systemCriteria="+semestaSpace; -mainline"
Also, I know you didn’t ask for this, but if you were wanting to mark Nusantara as a special node — HQ, capital, or whatnot — you could add this:
Code: Select all
<TopologyProcessor priority="primaryColony">
<System criteria="+nodeID:Nusantara" attributes="semestaHQ"/>
</TopologyProcessor>
This would make it easier to create a specific station that can only appear in that specific system or, conversely, add “-semestaHQ” to the systemCriteria of encounters you want to prohibit.
Do note that, with the above, no vanilla encounters will happen in those systems. At all. If you want to add things like pirates, outlaws, Corporate stations, or any other such, you’ll need to either add the attribute in their systemCriteria with another topology processor or include them in the stations you make inheriting versions of.
Also note that I haven’t checked if attributes like “commonwealthSpace” get added using the DistanceTo feature. If they do and use St. Katherine’s Star as a starting point, “commonwealthSpace”
will get run into the Semesta systems, and there’s just no getting around it. Before you ask: No, there is no current way to remove attributes from systems. That’s something you’d have to pester George about adding in
and I heartily encourage you to do so.
