Item Definition: Difference between revisions
m (→External links: clean up,) |
No edit summary |
||
(7 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
:''Main page at [http://www.gtamodding.com/index.php?title=Item_Definition GTAModding.com]'' | |||
{{IdeSection | {{IdeSection | ||
| noheader = 1 | | noheader = 1 | ||
}} | }} | ||
'''Item definition''' files, | '''Item definition''' files, usually identified by the file extension <code>.ide</code>, are used to declare many different aspects for the map system or to specify special behaviour rules for one of the aspects. They are stored in plain text format, so that they can be opened by any text editing program (like [[Wikipedia:Notepad|Notepad]]), but there are also some tools to simplify editing. | ||
== | == Overview == | ||
The | The ''item definition'' files are split up into several sections. There is no order on how you arrange the sections. Also you do not need to use all the sections in a file. | ||
=== Format and syntax description === | |||
The basic structure of the different sections is pretty simple. Each section starts with a four-character section identifier indicating how the content of the section gets interpreted by the game. The identifier is followed by the definition entries. Each entry takes one line and every line follows certain rules which are described in the articles handling the sections in detail (see below). However lines can also be empty or commented. If so they get ignored by the games' parser. The end of every section are indicated by the terminating string "end". Both (section identifier and terminating string) are not case sensitive, but by default they are written in lower case. | |||
Comments are usually indicated by the character <code>#</code> (number sign). It is possible to add comments to the end of a line, but breaking the line format for the current section using comments may cause the game to crash during loading. It is recommended that a comment should be placed on a separate line. Comments can also be placed outside of sections. | |||
Lines itself are always formatted in the same way differing only in the number of their parameters describing the semantical content of the line. Parameters are usually separated by the character <code>,</code> (comma). [[wp:Whitespace_character|Whitespace characters]] at the beginning or the end of an parameter get trimmed but they are usually used to give the content a more clear structure to make it more easier to read for human. Strings can be encased by the character <code>"</code> (quotation mark), but this is optional and rarely used by default. Also the games' parser uses an invariant culture to parse numerical values and strings. Which means strings are [[Wikipedia:ASCII|ASCII]] encrypted and the decimal separator is <code>.</code> (period). | |||
==== Section example ==== | |||
objs | |||
... | |||
end | |||
=== Sections === | |||
The following table contains basic information about all known sections. For additional information read the articles itself. | |||
{| class="wikitable" | |||
!width="120px"|Identifier | |||
!width="100px"|Supported games | |||
{|class=" | |||
!width=" | |||
!Description | !Description | ||
|- | |- | ||
|<center> | |<center>[[OBJS]]</center>||<center>{{Icon|3}} {{Icon|VC}} {{Icon|SA}} {{Icon|4}}</center>||Most important section: defines objects for the map.<br>Those objects get placed inside the [[INST]] section of the [[Item Placement|item placement files]]. | ||
|- | |- | ||
|<center> | |<center>[[TOBJ]]</center>||<center>{{Icon|3}} {{Icon|VC}} {{Icon|SA}} {{Icon|4}}</center>||Basicly does the same as ''OBJS'', but it has two additional parameters defining the ingame time range the object can get rendered.<br>Those objects get placed inside the ''INST'' section of the ''item placement files''. | ||
|- | |- | ||
|<center> | |<center>[[ANIM]]</center>||<center>{{Icon|SA}} {{Icon|4}}</center>||Basicly does the same as ''OBJS'', but it has one additional parameter identicating an [[IFP]] or [[WAD]] animation file to assign an animation to the object.<br>Those objects get placed inside the ''INST'' section of the ''item placement files''. | ||
|- | |- | ||
|<center> | |<center>[[PEDS]]</center>||<center>{{Icon|3}} {{Icon|VC}} {{Icon|SA}} {{Icon|4}}</center>||Used to define ''"pedestrians"'' (Random [[wikipedia:Non-player_character|NPC's]]). | ||
|- | |- | ||
|<center> | |<center>[[WEAP]]</center>||<center>{{Icon|VC}} {{Icon|SA}} {{Icon|4}}</center>||Used to define weapons. | ||
|- | |- | ||
|<center> | |<center>[[CARS_(IDE_Section)|CARS]]</center>||<center>{{Icon|3}} {{Icon|VC}} {{Icon|SA}} {{Icon|4}}</center>||Used to define vehicles. | ||
|- | |- | ||
|<center> | |<center>[[HIER]]</center>||<center>{{Icon|3}} {{Icon|VC}} {{Icon|SA}} {{Icon|4}}</center>||Partly unknown. Used to define objects for interactions with [[actor|actors]] for example in cutscenes. | ||
|- | |- | ||
|<center> | |<center>[[TXDP]]</center>||<center>{{Icon|SA}} {{Icon|4}}</center>||Used to virtually extend [[TXD|texture dictionaries]]. | ||
|- | |- | ||
|<center> | |<center>[[2DFX]]</center>||<center>{{Icon|3}} {{Icon|VC}}</center>||Used to add particles to objects, defined in one of the sections above (except ''TXDP''). | ||
|- | |- | ||
|<center> | |<center>[[PATH_(IDE_Section)|PATH]]</center>||<center>{{Icon|3}}</center>||Used to create waypoints for random NPC spawns ([[Paths]]). | ||
|- | |- | ||
|<center> | |<center>[[TREE]]</center>||<center>{{Icon|4}}</center>||– | ||
|- | |- | ||
|<center> | |<center>[[TANM]]</center>||<center>{{Icon|4}}</center>||Used to combine ''TOBJ'' and ''ANIM'' sections.<br>Those objects get placed inside the ''INST'' section of the ''item placement files''. | ||
|- | |- | ||
|<center> | |<center>[[MLO]]</center>||<center>{{Icon|4}}</center>||Used to create [[interior]]s. This section does also contain information about the entrace markers (previous [[ENEX]] connections) and dimensions of the interior which influences certain aspects, like the weather, for example. All objects are placed relative to an offset placed using [[MLO+]] inside the [[IPL]] or [[WPL]] file. | ||
|- | |- | ||
|<center> | |<center>[[AMAT]]</center>||<center>{{Icon|4}}</center>||– | ||
|} | |} | ||
== IDE Flags == | |||
=== | |||
'' | Flags are used in order to specify the behaviour of objects. They are interpreted as signed 32-bit integer values where each bit describes a [[wp:Boolean_algebra_(logic)|boolean]] value of a different aspect. The following table shows the standard flags used for objects defined in ''OBJS'', ''TOBJ'' and ''ANIM'' section. | ||
{|width="100%" class="wikitable" | |||
'' | !width="120px"|Flag | ||
!width="100px"|Supported games | |||
!width="25%"|Binary | |||
{|class=" | |||
!width=" | |||
!Description | !Description | ||
|- | |- | ||
|<center> | |<center>-1</center>||<center>–</center>||<center><code>1111 1111 1111 1111 1111 1111</code></center>||Enables all flags. <ref>[[wp:Two%27s_complement|Two's complement]]</ref> Never used by default. | ||
|<center> | |||
|<center> | |||
|- | |- | ||
|<center> | |<center>1</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0000 0000 0001</code></center>||Wet effect (objects appear darker). | ||
|- | |- | ||
|<center> | |<center>2</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0000 0000 0010</code></center>||Indicates that the object gets rendered at night for objects defined in ''TOBJ''. | ||
|- | |- | ||
|<center> | |<center>4</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0000 0000 0100</code></center>||Alpha transparency 1 | ||
|- | |- | ||
|<center> | |<center>8</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0000 0000 1000</code></center>||Alpha transparency 2 | ||
|- | |- | ||
|<center> | |<center>16</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0000 0001 0000</code></center>||Opposite to flag '''2''' | ||
|- | |- | ||
|<center> | |<center>32</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0000 0010 0000</code></center>||Indicates an object to be used inside an interior. | ||
|- | |- | ||
|<center> | |<center>64</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0000 0100 0000</code></center>||Disables the [[COLL#Shadow_Mesh|shadow mesh]] to project a shadow. | ||
|} | |||
{| | |||
|- | |- | ||
|<center> | |<center>128</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0000 1000 0000</code></center>||Object surface will not be [[Wikipedia:Hidden_surface_determination|culled]]. | ||
|- | |- | ||
|<center> | |<center>256</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0001 0000 0000</code></center>||Disables draw distance (Only used for [[LOD]] objects with an ''LOD'' value greater than 299). | ||
|- | |- | ||
|<center> | |<center>512</center>||<center>{{Icon|trilogy}} {{Icon|4}}</center>||<center><code>0000 0000 0000 0010 0000 0000</code></center>||Object is breakable (like glass – additional parameters defined inside the [[object.dat]] file, otherwise there is no effect). | ||
|- | |- | ||
|<center> | |<center>1024</center>||<center>{{Icon|trilogy}}{{Icon|4}}</center>||<center><code>0000 0000 0000 0100 0000 0000</code></center>||Similar to flag '''512''': object first cracks on a strong collision, then it breaks (does also require ''object.dat'' registration). | ||
|- | |- | ||
|<center> | |<center>2048</center>||<center>{{Icon|SA}} {{Icon|4}}</center>||<center><code>0000 0000 0000 1000 0000 0000</code></center>||Indicates an object as an garage door (for more information see [[GRGE#Types_of_doors|GRGE]] – requires ''object.dat'' registration). | ||
|} | |||
'' | |||
|- | |- | ||
|<center> | |<center>4096</center>||<center>{{Icon|SA}} {{Icon|4}}</center>||<center><code>0000 0000 0001 0000 0000 0000</code></center>||Indicates an [[RenderWare_binary_stream_file|multiclump]] object (Object switches from clump ''2'' to clump ''1'' after collision – requires ''object.dat'' registration). | ||
|- | |- | ||
|<center> | |<center>32768</center>||<center>{{Icon|SA}} {{Icon|4}}</center>||<center><code>0000 0000 1000 0000 0000 0000</code></center>||Uses object brightness from the current weather definition (See [[timecyc.dat]] – ''PoleShd''). | ||
|- | |- | ||
|<center> | |<center>65536</center>||<center>{{Icon|SA}} {{Icon|4}}</center>||<center><code>0000 0001 0000 0000 0000 0000</code></center>||Object explodes after getting hit (requires ''object.dat'' registration). | ||
|- | |- | ||
|<center> | |<center>131072</center>||<center>{{Icon|SA}}</center>||<center><code>0000 0010 0000 0000 0000 0000</code></center>||Unknown – apparently some flag for the [[SCM|Script]]. | ||
|- | |- | ||
|<center> | |<center>262144</center>||<center>{{Icon|SA}}</center>||<center><code>0000 0100 0000 0000 0000 0000</code></center>||Unknown – only used 1 time in [[Grand Theft Auto: San Andreas|San Andreas]]. | ||
|- | |- | ||
|<center> | |<center>1048576</center>||<center>{{Icon|SA}}</center>||<center><code>0000 1000 0000 0000 0000 0000</code></center>||Object will switch from clump ''2'' to clump ''1'' after getting sprayed by the player (graffity flag). | ||
|} | |||
'' | |||
|- | |- | ||
|<center> | |<center>2097152</center>||<center>{{Icon|SA}}</center>||<center><code>0001 0000 0000 0000 0000 0000</code></center>||Disables backface culling – as an result the texture will be drawed on both sides of the model (Always enabled for GTA III and [[Grand Theft Auto: Vice City|Vice City]]) | ||
|- | |- | ||
|<center> | |<center>4194304</center>||<center>{{Icon|SA}}</center>||<center><code>0010 0000 0000 0000 0000 0000</code></center>||Unknown – apparently related into physics. | ||
|- | |- | ||
|< | |colspan="4" style="text-align: right;" |<span class="plainlinks" style="font-size: 10px;">[http://www.gtamodding.com/index.php?title=Template:Object-Flags&action=edit edit]</span> | ||
|} | |} | ||
For flags defining different aspects of different definitions read the articles about their sections. | |||
== Difference between GTA III and GTA IV engines == | |||
[[Grand Theft Auto IV]] not only uses different formats to the previous games, it also does not use IDs to identify objects anymore. While [[Grand Theft Auto III]] era games use an ID as an index inside an array of definitions, GTA IV uses the hashes of the model name as a key inside a hash table. For more information about this see [[Map System]]. | |||
=== | == Tools == | ||
=== | * [[KEd]] – By JernejL | ||
* [[MEd]] – By Tonywob | |||
* [http://www.gtagarage.com/mods/show.php?id=4817 IDEditor] – By Xmen | |||
* [http://www.gtaforums.com/index.php?showtopic=402942 IDE-IV in GTA-IV script centre] – by Gforce | |||
* [http://www.aschratt.com/fileview.php?file=1004 FlagValue Calculator] – By Aschratt - Calculates all flagvalues (even those unknown). | |||
=== | == See also == | ||
* [[Item placement]] | |||
* [[Map System]] | |||
* [[Dynamic Object]] | |||
== References == | |||
<references /> | |||
== | == External links == | ||
* [http://www.gtaforums.com/index.php?showtopic=102833 GTAVC IDE Definitions] - topic by ODIE covering specific details of IDE files in GTA VC | |||
* [http://www.gtaforums.com/index.php?showtopic=118193 GTA3/VC Map File Documentation and Troubleshooting] - topic by Opius covering general features of IDE files in GTA3 and GTA VC | |||
= | |||
* [http://www. | |||
* [http://gta-worldmods.t-n-network.de/forum/thread.php?threadid=3382 ID Flagvalue Decoding Project] - project to decode all missing flag values | * [http://gta-worldmods.t-n-network.de/forum/thread.php?threadid=3382 ID Flagvalue Decoding Project] - project to decode all missing flag values | ||
{{fdl}} | |||
{{modding}} | |||
[[Category:Map Formats]][[Category:GTA III Modifications]][[Category:GTA Vice City]] | [[Category:Map Formats]] | ||
[[Category:GTA III Modifications]] | |||
[[Category:GTA Vice City]] | |||
[[Category:Modifications]] | [[Category:Modifications]] |
Revision as of 22:48, 19 February 2011
- Main page at GTAModding.com
IDE Sections:
|
Item definition files, usually identified by the file extension .ide
, are used to declare many different aspects for the map system or to specify special behaviour rules for one of the aspects. They are stored in plain text format, so that they can be opened by any text editing program (like Notepad), but there are also some tools to simplify editing.
Overview
The item definition files are split up into several sections. There is no order on how you arrange the sections. Also you do not need to use all the sections in a file.
Format and syntax description
The basic structure of the different sections is pretty simple. Each section starts with a four-character section identifier indicating how the content of the section gets interpreted by the game. The identifier is followed by the definition entries. Each entry takes one line and every line follows certain rules which are described in the articles handling the sections in detail (see below). However lines can also be empty or commented. If so they get ignored by the games' parser. The end of every section are indicated by the terminating string "end". Both (section identifier and terminating string) are not case sensitive, but by default they are written in lower case.
Comments are usually indicated by the character #
(number sign). It is possible to add comments to the end of a line, but breaking the line format for the current section using comments may cause the game to crash during loading. It is recommended that a comment should be placed on a separate line. Comments can also be placed outside of sections.
Lines itself are always formatted in the same way differing only in the number of their parameters describing the semantical content of the line. Parameters are usually separated by the character ,
(comma). Whitespace characters at the beginning or the end of an parameter get trimmed but they are usually used to give the content a more clear structure to make it more easier to read for human. Strings can be encased by the character "
(quotation mark), but this is optional and rarely used by default. Also the games' parser uses an invariant culture to parse numerical values and strings. Which means strings are ASCII encrypted and the decimal separator is .
(period).
Section example
objs ... end
Sections
The following table contains basic information about all known sections. For additional information read the articles itself.
Identifier | Supported games | Description |
---|---|---|
Most important section: defines objects for the map. Those objects get placed inside the INST section of the item placement files. | ||
Basicly does the same as OBJS, but it has two additional parameters defining the ingame time range the object can get rendered. Those objects get placed inside the INST section of the item placement files. | ||
Basicly does the same as OBJS, but it has one additional parameter identicating an IFP or WAD animation file to assign an animation to the object. Those objects get placed inside the INST section of the item placement files. | ||
Used to define "pedestrians" (Random NPC's). | ||
Used to define weapons. | ||
Used to define vehicles. | ||
Partly unknown. Used to define objects for interactions with actors for example in cutscenes. | ||
Used to virtually extend texture dictionaries. | ||
Used to add particles to objects, defined in one of the sections above (except TXDP). | ||
Used to create waypoints for random NPC spawns (Paths). | ||
– | ||
Used to combine TOBJ and ANIM sections. Those objects get placed inside the INST section of the item placement files. | ||
Used to create interiors. This section does also contain information about the entrace markers (previous ENEX connections) and dimensions of the interior which influences certain aspects, like the weather, for example. All objects are placed relative to an offset placed using MLO+ inside the IPL or WPL file. | ||
– |
IDE Flags
Flags are used in order to specify the behaviour of objects. They are interpreted as signed 32-bit integer values where each bit describes a boolean value of a different aspect. The following table shows the standard flags used for objects defined in OBJS, TOBJ and ANIM section.
Flag | Supported games | Binary | Description |
---|---|---|---|
1111 1111 1111 1111 1111 1111 |
Enables all flags. [1] Never used by default. | ||
0000 0000 0000 0000 0000 0001 |
Wet effect (objects appear darker). | ||
0000 0000 0000 0000 0000 0010 |
Indicates that the object gets rendered at night for objects defined in TOBJ. | ||
0000 0000 0000 0000 0000 0100 |
Alpha transparency 1 | ||
0000 0000 0000 0000 0000 1000 |
Alpha transparency 2 | ||
0000 0000 0000 0000 0001 0000 |
Opposite to flag 2 | ||
0000 0000 0000 0000 0010 0000 |
Indicates an object to be used inside an interior. | ||
0000 0000 0000 0000 0100 0000 |
Disables the shadow mesh to project a shadow. | ||
0000 0000 0000 0000 1000 0000 |
Object surface will not be culled. | ||
0000 0000 0000 0001 0000 0000 |
Disables draw distance (Only used for LOD objects with an LOD value greater than 299). | ||
0000 0000 0000 0010 0000 0000 |
Object is breakable (like glass – additional parameters defined inside the object.dat file, otherwise there is no effect). | ||
0000 0000 0000 0100 0000 0000 |
Similar to flag 512: object first cracks on a strong collision, then it breaks (does also require object.dat registration). | ||
0000 0000 0000 1000 0000 0000 |
Indicates an object as an garage door (for more information see GRGE – requires object.dat registration). | ||
0000 0000 0001 0000 0000 0000 |
Indicates an multiclump object (Object switches from clump 2 to clump 1 after collision – requires object.dat registration). | ||
0000 0000 1000 0000 0000 0000 |
Uses object brightness from the current weather definition (See timecyc.dat – PoleShd). | ||
0000 0001 0000 0000 0000 0000 |
Object explodes after getting hit (requires object.dat registration). | ||
0000 0010 0000 0000 0000 0000 |
Unknown – apparently some flag for the Script. | ||
0000 0100 0000 0000 0000 0000 |
Unknown – only used 1 time in San Andreas. | ||
0000 1000 0000 0000 0000 0000 |
Object will switch from clump 2 to clump 1 after getting sprayed by the player (graffity flag). | ||
0001 0000 0000 0000 0000 0000 |
Disables backface culling – as an result the texture will be drawed on both sides of the model (Always enabled for GTA III and Vice City) | ||
0010 0000 0000 0000 0000 0000 |
Unknown – apparently related into physics. | ||
edit |
For flags defining different aspects of different definitions read the articles about their sections.
Difference between GTA III and GTA IV engines
Grand Theft Auto IV not only uses different formats to the previous games, it also does not use IDs to identify objects anymore. While Grand Theft Auto III era games use an ID as an index inside an array of definitions, GTA IV uses the hashes of the model name as a key inside a hash table. For more information about this see Map System.
Tools
- KEd – By JernejL
- MEd – By Tonywob
- IDEditor – By Xmen
- IDE-IV in GTA-IV script centre – by Gforce
- FlagValue Calculator – By Aschratt - Calculates all flagvalues (even those unknown).
See also
References
External links
- GTAVC IDE Definitions - topic by ODIE covering specific details of IDE files in GTA VC
- GTA3/VC Map File Documentation and Troubleshooting - topic by Opius covering general features of IDE files in GTA3 and GTA VC
- ID Flagvalue Decoding Project - project to decode all missing flag values
This page is licensed under the GNU Free Documentation Licence. This page has a separate license to the CC-BY-SA that applies to most of Grand Theft Wiki.
The full text of the GNU FDL v1.2 is here. Click the "History" button to see the full list of authors. See Grand Theft Wiki:Copyright for more detail on our copyright policy.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. See Grand Theft Wiki:Copyright for more information. |
Technical | IMG | DFF | TXD | IDE | GXT | Handling | Carcols | Dynamic Object |
Mods | Hot Coffee Modification | Create a Mission |
Tools | GGMM |
Game Files | Animviewer.dat/GTAVC | Bink | Default.dat/GTAVC | Chassis Vlo | Fistfite.dat/GTAVC | Flight.dat | Gta vc.dat | Object.dat/GTAVC | OpenGTA2 |Particle.cfg/GTAVC | Particle (SA) | Paths | Ped.dat/GTAVC | Pedgrp.dat/GTAVC | Pedstats.dat/GTAVC | Scenarios.dat | Scripted Path | Surface.dat/GTAVC | Surfaud.dat | TimeCyc Definition | Timecyc.dat/GTAVC | Train.dat/GTAVC | Train.dat/GTAVC | Train.dat/GTAVC | Train2.dat/GTAVC | WAD | WBD-WBN | WPFL | Water.dat | Water.dat/GTAVC | Weapon.dat/GTAVC Weaponinfo.xml |
Multiplayer | Multi Theft Auto, Vice City Multiplayer, San Andreas Multiplayer |