Versions Compared

Old Version 3

changes.mady.by.user Pstemarie

Saved on

compared with

New Version 4

changes.mady.by.user Lucky

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added tables to how tiles are organized in groups

As explained by Velmar

; NEVERWINTER NIGHTS TILESET FILE
; DO NOT EDIT MANUALLY - UNLESS YOU KNOW WHAT YOU ARE DOING
[GENERAL]Begin of General Section
Name=TTR01The "internal" name. Other files like "doortypes.2da" and "loadscreens.2da" reference to it.
Type=SETSeems obvious.
Version=V1.0I edited this once and the toolset crashed.
Interior=0Set this to "1" to have weatherand day/night FX enabled by default
HasHeightTransition=1If the tileset uses raise/lower and looks for height=1 in [TILE] description
EnvMap=ttr01__ref01The default environment map (used for water textures and the like)
Transition=5The height difference of model placed (in meters) at Height 0 and Height 1. This only describes the models height, and does
not change anything in the tilemodel itself.
DisplayName=1606The name displayed when selecting a tileset in the toolset. It references an entry in dialog.tlk.
Change this to "-1" and add a line
"UnlocalizedName=MY_TILESETS_NAME" to make that name appear instead.
Border=GrassThe Terrain of the Area`s edges
Default=GrassThe default terrain that is placed everywhere when creating a new area using this tileset.
Floor=GrassThe terrain placed when using the "eraser".


[GRASS]The settings for the grass that appears if a walkmeshnode of the tilemodel is set to "3 / grass"
Grass=1Set this to "0" to turn of grass completely. You can then remove the following lines.
Density=5.000How strong the grass grows.
Height=1.200The height of the grass in meters.
AmbientRed=0.500
AmbientGreen=0.600
AmbientBlue=0.300		The colour settings of the grass. RGB settings.
DiffuseRed=0.500
DiffuseGreen=0.600
DiffuseBlue=0.300


[TERRAIN TYPES]
Count=3		The number of terrain types used in the tileset.
[TERRAIN0]First Terrain entry. Make sure ALL count entries in your tileset begin with "0" and the last entry is count-1
Name=GrassThe name of the terrain as it will be used in the [TILE] entries later. (CASE SENSITIVE !)
StrRef=63635

The reference to name-string in "dialog.tlk" leave this out if you create a custom terrain and use

RESREF
RESREF
Grass
STRING
NAME
MyTerrainName

with the ITP-Tool

You can use this combination with CrosserTypes, too.



[CROSSER TYPES]
Count=4		Similar to [TERRAIN TYPES], just for crossers like road and stream
[CROSSER0]
Name=Stream
StrRef=63302




[PRIMARY RULES]
Count=28		The primary rules section. Here is determined what terrain type is allowed to place, and what happens if a certain terrain
type is placed on and next to another.
[PRIMARY RULE0]The first primary rule.Again, watch the count !

The use of Primary Rules is hard to explain. You got to know that terrain is always determined
using the corners (NOT the edges) and if you place something, all tiles adjacent are placed again, too.
(That`s why tiles change around a placed one, even if you just place basic floor tiles)
According to BioWare`s TilesetTutorial, these aren`t really needed and just add some logical pattern to the .SET ( ?! ) .

I`ll explain it the way I read it:

Placed=GrassIf "Grass" is placed....
PlacedHeight=0...and the height of the Tile is 0
Adjacent=Grass
AdjacentHeight=0		...and the adjacent tile`s corner is "Grass" with a height of "0"
Changed=Grass
ChangedHeight=0		...the terrain at the adjacent gets changed to "Grass" with a height of "0".


[SECONDARY RULES]
Count=0		UNKNOWN - it`s never used in any tileset


[TILES]
Count=259		Begin of the [TILE] section. The settings in this section mainly describe the looks and use of a given tilemodel.
We`ll use "ttr01_a11_01" for this example.

Image Modified
The same tile from above and aligned to fit [Tile] entry....

Image Modified

[TILE9]The number of the tile entry
Model=ttr01_a11_01The file reference to "ttr01_a11_01.mdl" and it`s walkmesh file "ttr01_a11_01.wok"
WalkMesh=msb01
TopLeft=Grass
TopLeftHeight=0
TopRight=Water
TopRightHeight=0
BottomLeft=Grass
BottomLeftHeight=0
BottomRight=Grass
BottomRightHeight=1		The tile-description section.
Take a look at above picture and you`ll understand how it`s read.
Remember tiles are always read over corners and if you place a tile, adjacent corners are placed, too.
This starts a "snowball system" of placing tiles.
Note the edges that are left out. It looks like they aren`t affected if you place something, but in fact
the tiles there are affected by the tiles placed at the corners.
Top=
Right=
Bottom=
Left=		Here are the entries for crossers.
Crossers are additionally used over edges, not only over corners.
MainLight1=1
MainLight2=1
SourceLight1=1
SourceLight2=1
AnimLoop1=1
AnimLoop2=1
AnimLoop3=1		This section is used to turn the various tile options on and off.
The options have to be set in the model, else nothing will happen.
If there are no "sl" nodes in the model , no sourcelight (torches) will appear for example.
You`ll see the checkboxes for this section if you rightclick on a tile.
Doors=0The number of doors in the tile. I`ll do an door example further down....
Sounds=0
PathNode=Q

This is a descriptor for the walkmesh type and is used in the pathfinding routines.
Image Modified
The lines describe on which edge the tile can be left/entered.

Orientation=180Turn the Pathnodes with this (in +/- 90 degrees) to tell the engine how the tile can be passed through.
Positve values are Counter-Clockwise Rotations,
Negative Values are Clockwise.
VisibilityNode=ASame as PathNode, but for Line-Of-Sight only - Can be left out if same as PathNode
VisibilityOrientation=0Same as Orientation, but for Line-Of-Sight only- Can be left out if same as PathNode
ImageMap2D=MITR01_A11This is the reference to the image that is displayed on the map for this tile.
(MItr01_a11.tga in this case)
It should be 16x16 px , 24bit TGA.


ON DOORS

Remember the Doors=0 entry above ?
Let`s assume it would have been Doors=1 or more.
In that case the [TILE] entry must be directly followed by
[TILE9DOOR0]This is the entry for the FIRST door in a given tile.
The first part "[TILE9" references to the tile, while "DOOR0]" is the sequential number of the door.
If there would be more than one door in the tile, the next would have to be [TILE9DOOR1] and so on.
Type=65This references to the entry number in "doortypes.2da". If it`s not "=0" it is a TilesetSpecific door.
Entries of "=0" let you place doors from "genericdoors.2da" (simple doors).
Tileset specific doors get auto-placed when the tile is placed, while you have to place simple doors by hand.
X=2.78
Y=0.00
Z=0.00		The position of the door. Values are in meters.
Orientation=-90.0The facing of the door.


[GROUPS]
Count=63

The Groups section and it`s count.
Everything that is not bound in a group is subject to be placed either through
Terrain or Crosser placement and is either considered a Feature or Group,
based on your ITP entry.

Groups are organized X, Y starting from the bottom left

Tile2
Tile1
Tile0


Tile0Tile1Tile2


Tile3Tile4Tile5
Tile0Tile1Tile2


[GROUP3]

The FOURTH group entry (remember, 0 is the first !)

Name=DragSkel_1x2The name of the group. It`s "for your eyes only" as it`s not used elsewhere.
StrRef=63637The reference to dialog.tlk entry.
You can leave this line out if you use a STRING NAME combination with ITP tools.
Rows=1
Columns=2		The size of the Group.
When placing a group it first reads all row "Tile=" entries and then the collumns.
(hope to be right on this)
Tile0=127

The first Tile to be placed with a group and the tile that you have to reference to
with the ITP-entry. So look up the model name of [TILE127], what is "ttr01_o06_01"
And create your ITP:
RESREF
RESREF
ttr01_c06_01
STRING
NAME
DragonSkeleton_1x2

Tile1=128The subsequent tiles. Once a tile is bound, it`s unavailable for Terrain/Crosser placement.

A small trick: if you set a "Tile#=" to "-1" (example: Tile3=-1), a random tile will be placed, according to terrain.

Padding a Set File

When adding tiles to one of the vanilla tilesets, it is a good idea to pad the SET file, leaving room for any future expansion by Beamdog. Padding a SET file is simply adding a blank, or “padded”, entry to the list of tiles in the SET file.

...