HowTo:Edit Unit Files - Revision history

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

2013-01-08T21:29:41Z

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

Nikai: linkfix, sp

2010-08-18T08:37:51Z

linkfix, sp

Halleck: vsnav: re-organizing

2006-04-15T07:39:30Z

vsnav: re-organizing

eddit at 08:32, 22 September 2005

2005-09-22T08:32:11Z

eddit at 08:28, 22 September 2005

2005-09-22T08:28:24Z

eddit at 08:19, 22 September 2005

2005-09-22T08:19:21Z

eddit at 08:18, 22 September 2005

2005-09-22T08:18:21Z

Halleck: vsnav: made HowTo:Edit units.csv previous

2005-07-07T08:05:01Z

vsnav: made HowTo:Edit units.csv previous

Pirx: /* See also */ HowTo:Edit units.csv

2005-05-30T20:12:34Z

‎See also: HowTo:Edit units.csv

Pirx at 17:47, 28 May 2005

2005-05-28T17:47:35Z

@@ Line 57: / Line 57: @@
 * <code><'''Meshfile''' .../></code>
 ** <code>file</code> - Points to a xmesh-file of the ship. Extension <code>.xmesh</code>
-** <code>texturestarttime</code> - ('''optional''') Defines the starting delay of a mesh animation. See [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=9688#9688 forums] for more.
+** <code>texturestarttime</code> - ('''optional''') Defines the starting delay of a mesh animation. See [http://forums.vega-strike.org/viewtopic.php?p=9688#9688 forums] for more.
 *** <code>RANDOM</code> - Random start delay.
 ***time until mesh animation starts
-** <code>startframe</code> - ('''optional''') Defines the starting-frame of a mesh animation. See [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=9688#9688 forums] for more.
+** <code>startframe</code> - ('''optional''') Defines the starting-frame of a mesh animation. See [http://forums.vega-strike.org/viewtopic.php?p=9688#9688 forums] for more.
 *** <code>RANDOM</code> - Random start-frame.
 *** number of start-frame
@@ Line 228: / Line 228: @@
 ==Fileextension differences==
-See also this [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1811 forum thread].
+See also this [http://forums.vega-strike.org/viewtopic.php?t=1811 forum thread].
 * '''<file without extension>'''
 ** default unit file
@@ Line 256: / Line 256: @@
 * [[HowTo:Edit HUDs]]
 * Forum posts
-** [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1811 Unit Differences]
+** [http://forums.vega-strike.org/viewtopic.php?t=1811 Unit Differences]
-** [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=9688#9688 XML Format]
+** [http://forums.vega-strike.org/viewtopic.php?p=9688#9688 XML Format]

@@ Line 47: / Line 47: @@
 ==XML schema==
-The original desciption of the xunit syntax from hellcatv is located in '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data/units/description.xunit?rev=HEAD&content-type=text/vnd.viewcvs-markup CVS (description.xunit)]''' (VSD = 5400 kJ (kilojoules).
+The original description of the xunit syntax from hellcatv is located in '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data/documentation/description.xunit?content-type=text%2Fplain SVN (description.xunit)]''' (VSD = 5400 kJ (kilojoules).
 <code><'''Unit''' ...> </Unit></code> - Marks the begin and the end of the unit(file)
@@ Line 67: / Line 67: @@
 * <code><'''BspMesh'''></code> - ('''optional''') xmesh-file to use for beam and bolt collisions (not drawn) Extension <code>.xmesh</code>
 * <code><'''Mount''' .../></code> - ('''optional''')('''repeatable''') Specifies a weapon mount
-** <code>weapon</code> - Type of weapon (see '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/weapon_list.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup weapon_list.xml]''' in the data directory)
+** <code>weapon</code> - Type of weapon (see '''[http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data/weapon_list.xml?content-type=text%2Fplain weapon_list.xml]''' in the data directory)
-** <code>size</code> - size class(es)/type(s) and if they are capable of autotracking. The single entries are seperated by spaces. e.g: <code>size="LIGHT MEDIUM AUTOTRACKING"</code>
+** <code>size</code> - size class(es)/type(s) and if they are capable of autotracking. The single entries are separated by spaces. e.g: <code>size="LIGHT MEDIUM AUTOTRACKING"</code>
 *** <code>LIGHT</code>
 *** <code>MEDIUM</code>
@@ Line 112: / Line 112: @@
 *** <code>strength</code> - Max hull in VSD
 ** <code><'''Cloak''' .../></code> - ('''optional''') Specifies the ships cloak device
-*** <code>missing</code> - if 1, then no cloak is here. also missing in abserce of optional tag
+*** <code>missing</code> - if 1, then no cloak is here. also missing in absence of optional tag
 *** <code>cloakmin</code> - minimum percentage of cloakedness
 *** <code>cloakglass</code> - boolean whether or not effect 2 is used
@@ Line 160: / Line 160: @@
 ** <code>missing</code> - boolean whether the jump drive is missing (assumed missing in absence of tag)
 * <code><'''description''' ...>...   </description></code> - ('''repeatable''')
-** <code>combatrole</code> - combat role that the ship has (see [http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/vegastrike/data4.x/ai/VegaPriorities.csv?rev=HEAD&content-type=text/plain ai/VegaPriorities.csv] )
+** <code>combatrole</code> - combat role that the ship has (see [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data/ai/VegaPriorities.csv?content-type=text%2Fplain ai/VegaPriorities.csv] )
 ** <code>lang</code> - ('''optional''') Language code for the language the description is written in.
-*** e.g <code>lang='DE'</code> for german language
+*** e.g <code>lang='DE'</code> for German language
 *** See [http://www.xs4all.nl/~margjos/langen.htm this link] for all codes:
-*** If no lang attribute is specified the description is meant to be english. (''is this correct'?')
+*** If no lang attribute is specified the description is meant to be English. (''is this correct'?')
 ** Some cool description of the ship.
 * <code><'''Hold''' ...> ... </Hold></code>
@@ Line 179: / Line 179: @@
 **** <code>file</code> - name of cargo
 **** <code>price</code> - price of cargo
-**** <code>quantity</code> - ammount of cargo
+**** <code>quantity</code> - amount of cargo
 **** <code>mass</code> - mass in tonnes
 **** <code>volume</code> - size of cargo in cargo units
@@ Line 193: / Line 193: @@
 ** <code>size</code> - size of dock port (radius, in meters ;-))
 ** <code>dockinternal</code> - ('''optional/unused''') whether the dock port makes the ship disappeared. The ship must be smaller than the size of the dock, otherwise it will remain in open space.
-* <code><'''SubUnit''' .../></code> - ('''optional''')('''repeatable''') A Subunt is a (not necessarily) small independant part of your unit. In fact the main unit and the subunit are two different ships (units) patched together at a certain point (x,y,z see below). If a subunit is destroyed the remaining parts will fly into space like the remainings of any other ship ... e.g turrets
+* <code><'''SubUnit''' .../></code> - ('''optional''')('''repeatable''') A Subunit is a (not necessarily) small independent part of your unit. In fact the main unit and the subunit are two different ships (units) patched together at a certain point (x,y,z see below). If a subunit is destroyed the remaining parts will fly into space like the remainings of any other ship ... e.g turrets
-** <code>file</code> - unit file that can be referenced frmo toplevel units
+** <code>file</code> - unit file that can be referenced from toplevel units
 ** <code>siz</code> - size class (which sizes it can hold)
 ** <code>x</code>,<code>y</code>,<code>z</code> - location of subunit (in meters ;-))

@@ Line 2: / Line 2: @@
 | previous=[[HowTo:Edit units.csv|Edit units.csv]]
 | up=[[HowTos]]
-| next=[[HowTo:Edit Mesh Files|Edit Mesh Files]]
+| next=[[HowTo:Edit HUDs|Editing HUDs]]
 }}
 ----
@@ Line 265: / Line 265: @@
 | previous=[[HowTo:Edit units.csv|Edit units.csv]]
 | up=[[HowTos]]
-| next=[[HowTo:Edit Mesh Files|Edit Mesh Files]]
+| next=[[HowTo:Edit HUDs|Editing HUDs]]
 }}
 [[Category:HowTos|Edit Unit Files]]

@@ Line 7: / Line 7: @@
 =EDITING UNIT FILES=
 {{warning_text|
-|text=If you're wondering why you can't find any examples of xunit files in the Vegastrike data set, that's because this file format isn't used anymore. Unit information is stored in {{CVS:Units.csv}} in the data directory instead. You can still use the information on this page to create a unit, just append it to Units.csv using <code>objconv/ucsv.py</code> in the source directory once you're done. The result isn't guaranteed to be perfect, but if everything else is in order the unit should be flyable and viewable in-game. You can then use a spreadsheet program to handle the rest of it.
+|text=If you're wondering why you can't find any examples of xunit files in the Vegastrike data set, that's because this file format isn't used anymore. Unit information is stored in Units.csv in the data directory instead. You can still use the information on this page to create a unit, just append it to Units.csv using <code>objconv/ucsv.py</code> in the source directory once you're done. The result isn't guaranteed to be perfect, but if everything else is in order the unit should be flyable and viewable in-game. You can then use a spreadsheet program to handle the rest of it.
 |}}

@@ Line 7: / Line 7: @@
 =EDITING UNIT FILES=
 {{warning_text|
-|text=If you're wondering why you can't find any examples of xunit files in the Vegastrike data set, that's because this file format isn't used anymore. Unit information is stored in {{CVS:Units.csv}} in the data directory instead. You can still use the information on this page to create a unit, just append it to {{CVS:Units.csv}} using <code>objconv/ucsv.py</code> in the source directory once you're done. The result isn't guaranteed to be perfect, but if everything else is in order the unit should be flyable and viewable in-game. You can then use a spreadsheet program to handle the rest of it.
+|text=If you're wondering why you can't find any examples of xunit files in the Vegastrike data set, that's because this file format isn't used anymore. Unit information is stored in {{CVS:Units.csv}} in the data directory instead. You can still use the information on this page to create a unit, just append it to Units.csv using <code>objconv/ucsv.py</code> in the source directory once you're done. The result isn't guaranteed to be perfect, but if everything else is in order the unit should be flyable and viewable in-game. You can then use a spreadsheet program to handle the rest of it.
 |}}

@@ Line 253: / Line 253: @@
 =See also=
-* Forums
+* [[HowTo:Edit units.csv]]
 ** [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1811 Unit Differences]
 ** [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=9688#9688 XML Format]
-* Other [[HowTos]]
-** [[HowTo:Edit HUDs]]
 ----