stargates work by placing an <Orbitals> inside your system in the location you want.
Code: Select all
<Orbitals distance="75" angle="random">
<Lookup table="StargateOutbound"/>
</orbitals>
They are essentially the same for the functionality and eventually for this challenge, but in vanilla StargateInbound always points towards Heretic (and towards the center of the galaxy), the stargate has 2 beacons at opposite positions around the stargate. StargateOutbound points away from the center of the galaxy and the 2 beacons around the stargate are at 90 degrees from each other. In vanilla, in a normal linear topology, there is always 1 inbound and 1 outbound.
Topology:
This is the example JohnBWatson, I'm going to describe it:
Code: Select all
<!-- Our system map. Here, we define the two systems in the game, as well as their connection to each other and their placement on the galactic map.
A more complex topology, including a more random path from start to end, exists in the main source code. -->
<SystemMap UNID="&smPBLSystemMap;"
name= "Space"
backgroundImage= "&rsWatsonGalaxyMap;"
initialScale= "100"
minScale= "50"
maxScale= "100"
>
<TopologyCreator>
<Stargate from="SE:Outbound" to="DL:Inbound"/>
</TopologyCreator>
<Node ID="SE" x="0" y="0">
<System UNID= "&ssWatsonsStar;"
name= "Watson's Star"
level= "1"
attributes= "humanSpace; newBeyond; mainline;"
/>
</Node>
<Node ID="DL" x="100" y="0">
<System UNID= "&ssDelirium;"
name= "Delirium"
level= "3"
attributes= "humanSpace; newBeyond; mainline;"
/>
</Node>
</SystemMap>
The code starts by declaring the systemmap, in which John places his own background image and name it "Space"
<TopologyCreator> is where the you declare the actual stargate connections, in this case, there is only 2 stargates and 1 connection, from node SE we can travel to node DL.
But what are SE and DL nodes?
This is what we have to declare next: in the <Node> we declare the ID, which at the end is simply a shortened name for the systemnode, X and Y are the coordinates in pixels of the node on the galaxymap.
Then we need the system with its own attributes like name and level.
For this Challenge, your job is to write a <Node> for your own system, I will then assemble all the nodes and systems received from the partecipants in a simple adventure so we can play out all of them