GTAMods Wiki - User contributions [en]

Talk:Referring to GTA Versions

2016-12-18T16:37:42Z

Grovespaz:

Maybe call it '''GTA4 L&D''' instead? Since there'll be at least one other extension/DLC... --[[User:Steve-m|Steve-m]] 18:07, 26 November 2008 (UTC)
:I would go for GTA4 L&D for sure to avoid future confusions. [[User:Seemann|Seemann]] 20:52, 26 November 2008 (UTC)
::I didn't see anyone referring the DLC as L&D before. I just used the most popular shortened title I see in the forums. [[User:Spaceeinstein|Spaceeinstein]] 16:47, 27 November 2008 (UTC)

Is the Steam version of VC not listed for a reason or has it been forgotten? [[User:Grovespaz|Grovespaz]] ([[User talk:Grovespaz|talk]]) 16:37, 18 December 2016 (UTC)

Mission Scripting Tools

2007-04-07T13:13:17Z

Grovespaz: Sanny Builder Info

= Introduction =

A more in depth introduction to mission coding can be found [[Mission Scripting (Overview)|here]], but basically mission coding/scripting is altering the main.scm (and, in SA the script.img file) to run extra game code.

Game code is restricted to a set of commands defined by the game (called OpCodes), which can be used to test and alter certain attributes of ingame objects. Basically, you can do alot with mission scripting (anything done in any of the missions and in between the missions and more), but not everything is controlled by it, it is very difficult to say what is and isn't.

To give you an idea, the OpCode databases ([http://vc-db.webtools4you.net VC] and [http://sa-db.webtools4you.net SA]) have fairly cleverly named the OpCodes (although there are alot of unknown ones).

= Editing =

To open the main.scm file, you will need one of the coding tools, the most common of which are:

== III tools ==
* [http://www.sannybuilder.com Sanny Builder]
* [http://www.tfads.com/gta3code/zips/bwmb47.zip Mission Builder]

== VC tools ==
* [http://www.sannybuilder.com Sanny Builder]
* [http://www.kostelecky.com/craig/mb15.rar Mission Builder]

== SA tools ==
* [http://www.sannybuilder.com Sanny Builder]
* [http://www.joncaruana.com/projects/point/ Point]

== LCS tools ==
* [http://www.sannybuilder.com Sanny Builder] (Can only decompile at this stage)

== VCS tools ==
''None yet.''

{{Tutorial-stub}}

[[Category:Mission Scripting]]

TXD

2006-04-14T15:51:37Z

Grovespaz:

Copyed from Spooky, just to make a start..:
Please note that this is the Vice City format, although it doesnt differ that much..
[http://www.gtaforums.com/index.php?showtopic=112115&st=20 Copied from here]

== The (Vice City) TXD Format ==

The (usual) txd format looks like this:

(22) Texture Dictionary
|
+-+ (1) Data
| |--> Number of Textures (dword)
|
+-+ (21) Texture No. 1
| |-+ (1) Data
| | |--> (all the texture information and the image itself)
| |
| +-- (3) Extension (always empty - size=0) --> MISSING
|
+-+ (21) Texture No. 2
| |-- ... (same as above)
|
+-+ (21) Texture No. 3
|-- ...

(The number in brackets stands for the section type - dword)

These are just the alpha flags and (hopefully) depend on the image type:

8bit without alpha: 9728
8bit with alpha: 9472

32bit without alpha: 1536
32bit with alpha: 1280

DXT1 without alpha: 512
DXT1 with alpha: 256
DXT3 with alpha: 768

The first dword is section type, second section size and third the version id of the renderware file.
TXD files have the same basic format as DFF files and consist of sections with different purpose.
See [http://www.chronetal.co.uk/gta/index.php?page=dff KCows dff documentation] for more infos.
Every section has a 12 byte section header, containing type, size and ver id.
The version id's are:
0x0800FFFF for GTA3,
0x0C02FFFF for VC PS2 and
0x1003FFFF for VC PC
(in the most cases).

(Just the second byte of the dword changes, that's why all values are divisible by 256)

TXD

2006-04-14T15:46:18Z

Grovespaz: The start of the TXD page, just to get things rolling..

Copyed from Spooky, just to make a start..:
Please note that this is the Vice City format, although it doesnt differ that much..

== The (Vice City) TXD Format ==

The (usual) txd format looks like this:

(22) Texture Dictionary
|
+-+ (1) Data
| |--> Number of Textures (dword)
|
+-+ (21) Texture No. 1
| |-+ (1) Data
| | |--> (all the texture information and the image itself)
| |
| +-- (3) Extension (always empty - size=0) --> MISSING
|
+-+ (21) Texture No. 2
| |-- ... (same as above)
|
+-+ (21) Texture No. 3
|-- ...

(The number in brackets stands for the section type - dword)

These are just the alpha flags and (hopefully) depend on the image type:

8bit without alpha: 9728
8bit with alpha: 9472

32bit without alpha: 1536
32bit with alpha: 1280

DXT1 without alpha: 512
DXT1 with alpha: 256
DXT3 with alpha: 768

The first dword is section type, second section size and third the version id of the renderware file.
TXD files have the same basic format as DFF files and consist of sections with different purpose.
See [http://www.chronetal.co.uk/gta/index.php?page=dff KCows dff documentation] for more infos.
Every section has a 12 byte section header, containing type, size and ver id.
The version id's are:
0x0800FFFF for GTA3,
0x0C02FFFF for VC PS2 and
0x1003FFFF for VC PC
(in the most cases).

(Just the second byte of the dword changes, that's why all values are divisible by 256)