https://wiki.splashdamage.com/index.php?action=history&feed=atom&title=Vehicle_Scripting%3A_Entity_DefinitionVehicle Scripting: Entity Definition - Revision history2026-04-07T18:44:10ZRevision history for this page on the wikiMediaWiki 1.31.0https://wiki.splashdamage.com/index.php?title=Vehicle_Scripting:_Entity_Definition&diff=1420&oldid=prev192.168.0.142 at 16:48, 15 October 20072007-10-15T16:48:44Z<p></p>
<p><b>New page</b></p><div>Talk about how the main definition hooks up the vscript, script, model, etc etc. Controls, sounds, effects.<includeonly><br />
<br />
{{main|Vehicle Scripting: Entity Definition}}</includeonly><noinclude><br />
<br />
= Introduction = <br />
<br />
Entity definitions define spawnable entities. These are the things you can actually spawn in the game. In the case of vehicles these link together all the different parts of the vehicle's definition - the <tt>vehicleDef</tt>, the script, the model, the effects, etc. There are a great many things configured using the vehicle's <tt>entityDef</tt>, all of which are configured using key/value pairs.<br />
<br />
There are base definitions that can be inherited from to reduce the amount of repetition needed - for example <tt>vehicle_base_gdf</tt>.<br />
<br />
= Basics =<br />
<br />
First up there are the keys to set up the links between the major parts of the vehicle:<br />
* <tt>"spawnclass"</tt> - This selects the code class used for the vehicle. The most common one used is <tt>"sdVehicle_RigidBody"</tt>, but there are a couple of custom ones being the <tt>"sdWalker"</tt> used by the Cyclops and the <tt>"sdJetPack"</tt> used by the Icarus.<br />
* <tt>"scriptObject"</tt> - The name of the script object used for the vehicle.<br />
* <tt>"vs_vehicleScript"</tt> - The name of the <tt>vehicleDef</tt> used.<br />
* <tt>"model"</tt> - The name of the <tt>model</tt> to use.<br />
<br />
<br />
<br />
[[Category:Vehicles]]<br />
<br />
</noinclude></div>192.168.0.142