HowTo:Edit Systems:Milkyway - Revision history

Augie.ben.doggie: [vega-bot] [replace] 1 instances of 'http://vegastrike.sourceforge.net/forums' for 'http://forums.vega-strike.org'

2013-01-08T21:29:35Z

[vega-bot] [replace] 1 instances of 'http://vegastrike.sourceforge.net/forums' for 'http://forums.vega-strike.org'

Ghoulsblade2: /* associationg the milky_way.xml planet definitions with the units.csv file */

2010-08-18T16:59:16Z

‎associationg the milky_way.xml planet definitions with the units.csv file

Ghoulsblade2: /* Examples */

2010-08-18T15:30:09Z

‎Examples

Nikai: /* Examples */ linkfix

2010-08-17T08:20:25Z

‎Examples: linkfix

Nikai: /* Autogenerated System Files */ linkfix, sp

2010-08-17T08:18:19Z

‎Autogenerated System Files: linkfix, sp

Turgid Bolk: fixed up the wikicode to stop the italics, maybe someone with more wiki-fu can make it less messy

2007-08-08T05:05:22Z

fixed up the wikicode to stop the italics, maybe someone with more wiki-fu can make it less messy

pyramid: /* Overall description of how they work */

2007-08-06T23:57:14Z

‎Overall description of how they work

Nachtwolf: Added some summary information from my post.

2007-08-06T08:00:25Z

Added some summary information from my post.

peter: cvs->svn

2007-03-11T03:32:29Z

cvs->svn

Melonhead: /* Sector and System Variables */

2006-12-02T03:45:26Z

‎Sector and System Variables

@@ Line 5: / Line 5: @@
 == Overall description of how they work ==
-From [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=85622#85622 this forum post], the way it works is:
+From [http://forums.vega-strike.org/viewtopic.php?p=85622#85622 this forum post], the way it works is:
 The universe/milky_way.xml file contains information on planets that are created. The information is used in two ways.

@@ Line 318: / Line 318: @@
 </pre>
-== associationg the milky_way.xml planet definitions with the units.csv file ==
+== associating the milky_way.xml planet definitions with the units.csv file ==
 this is done by taking the var:texture from the milky_way.xml , e.g.

@@ Line 317: / Line 317: @@
 </galaxy>
 </pre>
 =See also=

← Older revision		Revision as of 08:20, 17 August 2010
Line 249:		Line 249:

	==Examples ==		==Examples ==
−	These examples are excerpts from '''[~~https~~://svn.sourceforge.net/~~svnroot~~/vegastrike/trunk/~~data4.x~~/universe/milky_way.xml universe/milky_way.xml]'''	+	These examples are excerpts from '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data/universe/milky_way.xml?content-type=text%2Fplain universe/milky_way.xml]'''

@@ Line 2: / Line 2: @@
 ----
 =Autogenerated System Files=
-Since they are autogenerated, these systems must have some rules so that the generator knows what to make.  These systems are autogenerated from the information contained in the XML file <code>[https://svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x/universe/milky_way.xml universe/milky_way.xml]</code>.
+Since they are autogenerated, these systems must have some rules so that the generator knows what to make.  These systems are autogenerated from the information contained in the XML file <code>[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data/universe/milky_way.xml?content-type=text%2Fplain universe/milky_way.xml]</code>.
 == Overall description of how they work ==
@@ Line 57: / Line 57: @@
 **** <code>< var ... /></code> - <small>(''repeatable'')</small> The variables for each individual planet (var tag to be described later)
 ** <code><'''systems'''> ... </systems></code> - You need it but I don't know why.
-*** <code><'''sector''' ... > ... </sector></code> - <small>(''repeatable'')</small> A sector containg a group of systems.
+*** <code><'''sector''' ... > ... </sector></code> - <small>(''repeatable'')</small> A sector containing a group of systems.
 **** <code>name</code> - the name of the sector. For example, enigma_sector.
 **** <code>< var ... /></code> - <small>(''repeatable'')</small> The default variables for the entire sector (var tag to be described later)
@@ Line 243: / Line 243: @@
 * Using the <code>Faction</code> variable, specify who initially owns the system.
 * Define the number of planets using the <code>num_planets</code> variable. You can also define extra units,  have a nebula or an asteroid field if you want.
-* Specfify the size of the sun using the <code>sun_radius</code> variable.
+* Specify the size of the sun using the <code>sun_radius</code> variable.
 * Define the position of the system in the galaxy using the <code>xyz</code> variable.
 * Specify the Jump destinations using the <code>jumps</code> variable.

@@ Line 10: / Line 10: @@
 . When generating a system, systems have pre-defined tags;
-  <var name="planets" value="a b *c gd bb m"/>
+  <nowiki><var name="planets" value="a b *c gd bb m"/></nowiki>
 Each of those are looked up in this top section based on the "initial" (this was to save space, since planets is used in so many places). "*" means that it is a moon to the previous planet.
@@ Line 29: / Line 29: @@
 If there are multiple textures, you can make the planets variable contain 10 of the planet you want, like:
-  <var name="planets" value="v v v v v v v v v"/>
+  <nowiki><var name="planets" value="v v v v v v v v v"/></nowiki>
 for Volcanic.
@@ Line 38: / Line 38: @@
 However, the generic milky_way statement requires png textures.
-<var name="texture_ext" value="png">
+ <nowiki><var name="texture_ext" value="png"></nowiki>
 That means, if he planet type has only maximum one texture to be randomly selected while generating a random system, a statement for a different file type can be added there.
-[code]<planet name="Volcanic">
+ <planet name="Volcanic">
-        <var name="texture" value="planets/Lava"/>
+        <nowiki> <var name="texture" value="planets/Lava"/>
         <var name="texture_ext" value="jpg"/>
         <var name="initial" value="v"/>
         <var name="lights" value="planets/Lava_light.jpg"/>
-</planet>[/code]
+ </planet></nowiki>
 A problem arises when there are mixed textures with texture_max>0, e.g. Lava.jpg and Lava1.png. In this case a preferred format has to be chosen and remaining textures converted from one to another.

@@ Line 1: / Line 1: @@
 {{parent_link|parent=[[HowTo:Edit_Systems|Edit Systems]]}}
 ----
 =Autogenerated System Files=
 Since they are autogenerated, these systems must have some rules so that the generator knows what to make.  These systems are autogenerated from the information contained in the XML file <code>[https://svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x/universe/milky_way.xml universe/milky_way.xml]</code>.
 ==XML Schema Description==

@@ Line 3: / Line 3: @@
 =Autogenerated System Files=
-Since they are autogenerated, these systems must have some rules so that the generator knows what to make.  These systems are autogenerated from the information contained in the XML file <code>[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/universe/milky_way.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup universe/milky_way.xml]</code>.
+Since they are autogenerated, these systems must have some rules so that the generator knows what to make.  These systems are autogenerated from the information contained in the XML file <code>[https://svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x/universe/milky_way.xml universe/milky_way.xml]</code>.
 ==XML Schema Description==
@@ Line 12: / Line 12: @@
 ** <code><'''systems'''> ... </systems></code> - You need it but I don't know why.
 *** <code><'''sector''' ... > ... </sector></code> - <small>(''repeatable'')</small> A sector containg a group of systems.
-**** <code>name</code> - the name of the sector. For, enigma_sector.
+**** <code>name</code> - the name of the sector. For example, enigma_sector.
 **** <code>< var ... /></code> - <small>(''repeatable'')</small> The default variables for the entire sector (var tag to be described later)
 **** <code><'''system''' ... > ... </system></code> - <small>(''repeatable'')</small> A system (to be a system it must be inside another sector tag).
@@ Line 203: / Line 203: @@
 ==Examples ==
-These examples are excerpts from '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/universe/milky_way.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup universe/milky_way.xml]'''
+These examples are excerpts from '''[https://svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x/universe/milky_way.xml universe/milky_way.xml]'''

@@ Line 90: / Line 90: @@
 * '''planets'''
 ** [[#Variable_Types|Type]]: <code>STRING</code>
-** Description: The possible planet types (defined in the <code><planets></code> section in milky_way.xml) in the system.
+** Description: The possible planet types (defined by the "initial" in the <code><planets></code> section in milky_way.xml) in the system.
 ** Example: <code>< var name="planets" value="a"/></code> One arid planet.
 * '''num_gas_giants'''