ModdingWiki - User contributions [en-gb]

DAT Format (Shadowcaster)

2026-08-06T14:50:54Z

Diema: Initial draft

== Overview ==
[[Shadowcaster]] contains two forms of DAT archive. This page is about the game's WAD-like game data archives. Another page details the [[Cutscene Format (Shadowcaster)|cutscene DAT format]].

A Shadowcaster game-data archive has the following general structure:
<syntaxhighlight lang="cpp">
uint16_t NumRecords; // the number of sub-files contained in this archive.
uint32_t Directory; // an offset from the start of this file to the beginning of the record list.

uint8_t DataRegion[...]; // raw sub-file data. there can be hidden sections here; a sub-file's start does not have to begin right after the end of the previous.

// within each sub-file record is the following format:
uint32_t Offset; // offset to the start of the data, from the beginning of the file.
uint32_t Size; // the sub-file's size in bytes.
uint16_t NameOfs; // a pointer from the beginning of the directory to a null-terminated string. this can be zero.
uint16_t Flags; // in the floppy version, this is always zero. in the CD version, a value of 1 indicates RLE compression.
</syntaxhighlight>

=== Record Names ===
In this format, sub-file records do not have to have a name.

The underlying logic of this is that the game will often request a specific named lump, then refer to unnamed records using an ID offset from that. For example, if the lump named "view" is lump #0, then the game can refer to "view+5" to refer to lump #5, and therefore, lump #5 does not have to store its name. In such a case, <code>NameOfs = 0</code>.

By convention, SLADE and MapCaster notate the names of these lumps as ID offsets from the last named entry found.

== Reading a DAT Archive ==
Adapted from MapCaster GML:
<syntaxhighlight lang="cpp">
NumRecords = buffer_read(buf, buffer_u16);
Directory = buffer_read(buf, buffer_u32);

buffer_seek(buf, buffer_seek_start, Directory);
for(z = 0; z < NumRecords; z++) {
Records[z] = ds_map_create();

r = Records[z];
r[? "Offset"] = buffer_read(buf, buffer_u32);
r[? "Size"] = buffer_read(buf, buffer_u32);
r[? "NameOffset"] = buffer_read(buf, buffer_u16);
r[? "Flags"] = buffer_read(buf, buffer_u16);

// name all lumps
if(r[? "NameOffset"] != 0) {
last_name = 0;
prev_ofs = buffer_tell(buf);

// seek to the name table
buffer_seek(buf, buffer_seek_start, Directory + r[? "NameOffset"]);

r[? "Name"] = ReadString(...); // read until 0x00 is encountered

// go back to where we were before in reading the directory
buffer_seek(buf, buffer_seek_start, prev_ofs);
}
else { // if the lump has no name, treat it as being
// named as an offset from the previous named lump
last_name++;
l = Records[z - last_name];
r[? "Name"] = l[? "Name"] + "+" + string(last_name);
}
}
</syntaxhighlight>

Shadowcaster

2026-08-06T14:39:13Z

Diema: Update to also put DAT format spec in, acknowledge a difference between ravdata and cutscene DATs

{{Stub}}
{{Game Infobox
| Levels = Edit
| Tiles = No
| Sprites = No
| Fullscreen = No
| Sound = Edit
| Music = Edit
| Text = No
| Story = No
| Interface = No
}}

'''Shadowcaster''' is a first-person action RPG with a shapeshifting protagonist. It was developed by [[Raven Software]] and published by [[Origin Systems]].

== Tools ==
Some of these may only work if a specific version is used.
{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [http://slade.mancubus.net SLADE]
| Platform = Windows/Mac
| grp = Edit
| map = No
| gfx = Extract
| mus = Edit
| sfx = Edit
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://www.doomworld.com/forum/topic/155625-mapcaster-level-editor-for-shadowcaster/ MapCaster]
| Platform = Windows
| grp = Edit
| map = Edit
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://github.com/darkhaven3/libby Libby]
| Platform = Windows, Linux
| grp = Edit
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

{{BeginGameFileList}}
{{GameFile
| Name = N/A
| Format = [[XMI Format]]
| KnownFormat = Yes
| Desc = Background music
}}
{{GameFile
| Name = N/A
| Format = [[VOC Format]]
| KnownFormat = Yes
| Desc = Sound effects
}}
{{GameFile
| Name = ravdata.dat
| Format = [[DAT Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Data archive
}}
{{GameFile
| Name = *.dat
| Format = [[Cutscene Format (Shadowcaster)]]
| KnownFormat = No
| Desc = Cutscenes
}}
{{GameFile
| Name = *.lib
| Format = [[LIB Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Data archive
}}
{{GameFile
| Name = *.map
| Format = [[MAP Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Level geometry
}}
{{GameFile
| Name = *.ojt
| Format = [[OJT Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Static objects
}}
{{GameFile
| Name = *.itm
| Format = [[ITM Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Items (wands, potions)
}}
{{GameFile
| Name = *.crt
| Format = [[CRT Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Monsters
}}
{{GameFile
| Name = *.arc
| Format = [[ARC Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Monster archetypes
}}
{{GameFile
| Name = *.scr
| Format = [[SCR Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Level scripts
}}
{{GameFile
| Name = *.dor
| Format = [[DOR Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Level doors
}}
{{GameFile
| Name = itemtype.nfo
| Format = [[NFO Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Item definitions
}}
{{EndGameFileList}}

== Links ==
* [http://www.doomworld.com/vb/everything-else/43927-shadowcaster-modding/ RE discussion on the Doomworld forum]
* [http://www.doomworld.com/vb/everything-else/51101-shadowcaster-modding-2-the-remoddening/ Further RE discussion on the Doomworld forum]
* [https://www.doomworld.com/forum/topic/94899-shadowcaster-modding-3-disassembly/ Even more RE discussion on the Doomworld forum, with some disassembly, engine limits and map format investigation]

[[Category:Raven Software]]
[[Category:Origin Systems]]
[[Category:3D]]

Shadowcaster

2026-08-06T14:29:05Z

Diema: MapCaster has been updated to deal directly with LIB format archives.

{{Stub}}
{{Game Infobox
| Levels = Edit
| Tiles = No
| Sprites = No
| Fullscreen = No
| Sound = Edit
| Music = Edit
| Text = No
| Story = No
| Interface = No
}}

'''Shadowcaster''' is a first-person action RPG with a shapeshifting protagonist. It was developed by [[Raven Software]] and published by [[Origin Systems]].

== Tools ==
Some of these may only work if a specific version is used.
{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [http://slade.mancubus.net SLADE]
| Platform = Windows/Mac
| grp = Edit
| map = No
| gfx = Extract
| mus = Edit
| sfx = Edit
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://www.doomworld.com/forum/topic/155625-mapcaster-level-editor-for-shadowcaster/ MapCaster]
| Platform = Windows
| grp = Edit
| map = Edit
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://github.com/darkhaven3/libby Libby]
| Platform = Windows, Linux
| grp = Edit
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

{{BeginGameFileList}}
{{GameFile
| Name = N/A
| Format = [[XMI Format]]
| KnownFormat = Yes
| Desc = Background music
}}
{{GameFile
| Name = N/A
| Format = [[VOC Format]]
| KnownFormat = Yes
| Desc = Sound effects
}}
{{GameFile
| Name = *.lib
| Format = [[LIB Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Data archive
}}
{{GameFile
| Name = *.map
| Format = [[MAP Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Level geometry
}}
{{GameFile
| Name = *.ojt
| Format = [[OJT Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Static objects
}}
{{GameFile
| Name = *.itm
| Format = [[ITM Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Items (wands, potions)
}}
{{GameFile
| Name = *.crt
| Format = [[CRT Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Monsters
}}
{{GameFile
| Name = *.arc
| Format = [[ARC Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Monster archetypes
}}
{{GameFile
| Name = *.scr
| Format = [[SCR Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Level scripts
}}
{{GameFile
| Name = *.dor
| Format = [[DOR Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Level doors
}}
{{GameFile
| Name = itemtype.nfo
| Format = [[NFO Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Item definitions
}}
{{EndGameFileList}}

== Links ==
* [http://www.doomworld.com/vb/everything-else/43927-shadowcaster-modding/ RE discussion on the Doomworld forum]
* [http://www.doomworld.com/vb/everything-else/51101-shadowcaster-modding-2-the-remoddening/ Further RE discussion on the Doomworld forum]
* [https://www.doomworld.com/forum/topic/94899-shadowcaster-modding-3-disassembly/ Even more RE discussion on the Doomworld forum, with some disassembly, engine limits and map format investigation]

[[Category:Raven Software]]
[[Category:Origin Systems]]
[[Category:3D]]

OJT Format (Shadowcaster)

2026-08-06T14:27:18Z

Diema: Initial draft

== Overview ==
[[Shadowcaster]] OJT files describe a list of static objects present in a given level. These files are a linear list of 57-byte records with no header.
<syntaxhighlight lang="cpp">
uint32_t Tag; // does not have to necessarily be unique.
uint32_t Ptr_Prev; // typically if there is a previous OJT record before this one, this is set to sizeof(ojt_record) (57).
uint32_t Ptr_Next; // same as above, but forwards in the file.
uint8_t Collision; // typically zero for a non-solid object, or 1 for a solid one.
uint8_t Gravity; // a bitfield describing the object's relationship to gravity.
// some known values: 0 = no gravity; 1 = hangs from ceiling; 3 = spawn on ceiling, subject to gravity.
char DisplayName[20]; // not used by the game. a string that usually contains the name of the sprite used. seems to be an editor leftover?
uint32_t Pic; // a literal lump number from RAVDATA.DAT. This is the graphic the object will use in the 3D view.
uint32_t Width; // the object's width (or "radius" if you prefer), represented in frac-units (0-63 within a tile).
uint32_t Height; // same as the above, but the object's height along Z+.
uint32_t Unknown;
uint8_t TileX;
uint8_t TileY; // the object's coarse tile X/Y coordinates (0-31 are valid).
uint8_t Sides; // the number of sides the sprite has. for example: 0 = one-sided sprite, 8 = eight-sided sprite (like Doom).
uint16_t SubTileX;
uint16_t SubTileY; // the object's sub-tile X/Y fractional values (0-63 are valid).
</syntaxhighlight>

== Reading an OJT file ==
Adapted from MapCaster GML:
<syntaxhighlight lang="cpp">
for(i = 0; i < NumOjtsInFile; i++) {
ojt.Tag = buffer_read(ojt_file, buffer_u32);
ojt.Ptr_Prev = buffer_read(ojt_file, buffer_u32);
ojt.Ptr_Next = buffer_read(ojt_file, buffer_u32);
ojt.Collision = buffer_read(ojt_file, buffer_u8);
ojt.Gravity = buffer_read(ojt_file, buffer_u8)
ojt.DisplayName = ReadString(20);
ojt.Pic = buffer_read(ojt_file, buffer_u32);
ojt.Width = buffer_read(ojt_file, buffer_u32);
ojt.Height = buffer_read(ojt_file, buffer_u32);
ojt.Unknown = buffer_read(ojt_file, buffer_u32);
ojt.x = buffer_read(ojt_file, buffer_u8) * TILESIZE; // TILESIZE = 64 in Shadowcaster
ojt.y = buffer_read(ojt_file, buffer_u8) * TILESIZE; // TILESIZE = 64 in Shadowcaster
ojt.Sides = buffer_read(ojt_file, buffer_u8);
ojt.x += buffer_read(ojt_file, buffer_u16);
ojt.y += buffer_read(ojt_file, buffer_u16);
}
</syntaxhighlight>

LIB Format (Shadowcaster)

2026-08-06T13:23:17Z

Diema: Initial draft

== Overview ==

[[Shadowcaster]] .lib archives can be considered the "ancestor" of the Doom WAD format. They are mostly similar, realistically only differing in how you are expected to find the sub-file directory.

At the high level, .lib archives consist of a data region, the directory region, and finally the number of records stored at the very end of the file.

=== Data Region ===

The data region is simply every file's contents, concatenated end-to-end. There can possibly be "hidden" sections; one file does not necessarily need to exactly start at the end of the previous, or itself end at the start of the next.

In the case of .lib files, mostly level data and music are stored; graphics are stored in [[DAT Format (Shadowcaster)|DAT files]].

=== Directory ===

The directory immediately precedes the record count, and consists of a number of 21-byte entries with the following format:
<syntaxhighlight lang="cpp">
uint32_t Size;
uint32_t Offset; // from beginning of file
char RecordName[13];
</syntaxhighlight>

=== Record Count ===

Determining how many records are stored in the directory is done by seeking to the end of the file and reading the final uint16_t found there.

== Reading a lib file ==

Adapted from MapCaster GML:
<syntaxhighlight lang="cpp">
// first, we get the number of records and construct a pointer to the start of the directory
buffer_seek(Lib, buffer_seek_start, filesize - 2);
NumRecords = buffer_read(Lib, buffer_u16);
// offset to the start of the directory:
Directory = filesize - 2 - (NumRecords * 21);

// seek to the start of the directory
buffer_seek(Lib, buffer_seek_start, Directory);

// Read all entries until the end
for(i = 0; i < NumRecords; i++) {
Records[i] = ds_map_create();
r = Records[i];
r[? "Size"] = buffer_read(Lib, buffer_u32);
r[? "Offset"] = buffer_read(Lib, buffer_u32);

// read the name string
r[? "Name"] = ReadString(13); // directory subfile names are always exactly 13 bytes and follow 8.3 DOS filename convention, and are null-terminated

}</syntaxhighlight>

SCR Format (Shadowcaster)

2026-07-25T04:35:17Z

Diema:

== Overview ==

[[Shadowcaster]] level scripts (*.SCR) control many special effects and level-flow modifications at runtime. Such effects include changing the level environment values (which sky is drawn if any, colored lighting, fog, and darkness), teleporting the player either to a different level (or within the same one), deleting and spawning static objects or items, locking or unlocking doors, and granting metaforms or experience points. These scripts are based on the concept of conditional lists -- that is, in order for an action to take place, a (series of) condition(s) must be satisfied.

There is no header. Script code begins immediately at the start of the file. A single script block consists of a list of conditions followed immediately by a list of function calls, and finally, a terminator. A script may not begin with a function call; this is explicitly treated as invalid data by the game. Conditions always have the following form:

<syntaxhighlight lang="cpp">int16_t condition_id;
uint8_t evaluation_type;
uint32_t value;</syntaxhighlight>

There is a list of 100 hard-coded conditions the game executable recognizes, many of which are exclusively script-controlled and are not modified directly by the game. In most circumstances, <code>evaluation_type</code> is set to <code>0x83</code> to mean "equal to"; other values are not yet fully known. This is followed by an immediate value to compare against. Scripts contain no explicit flow control and rely entirely on these condition evaluations.

For example, <code>0000 83 05000000</code> will be satisfied if condition #0 is equal to 5.

A single script block may contain many such condition formulations. The function list is only executed if all such conditions are satisfied. The condition list is finished specifying conditions upon encountering a condition with its highest bit set (0x8000). These are function calls. The game contains a list of 41 hard-coded functions that level scripts may call by ID. A function call follows this format:

<syntaxhighlight lang="cpp">int16_t function_id;
uint8_t numargs;
uint32_t args[...];</syntaxhighlight>

For example, <code>0F80 01 0D000000</code> -- function call 15, one argument (0x0D). This plays song ID 13 immediately upon satisfying its preceding condition list.

A function list is finished specifying calls when the game encounters a terminator byte outside of an argument list. A terminator can be 0xFF for single-fire scripts that are "deleted" after they are run, or 0x00 in some cases for repeatable effects. If no more condition/function lists proceed after this terminator byte, the script file is finished.

== Creating a Condition List ==

Condition lists are the first elements in a script, and are the most straightforward to produce, as they always consist of 7-byte records stored one after the other without separation.

Condition lists can be thought of as assembling a single large "if" statement in C/C++-like languages. Once all conditions are satisfied, the functions are then executed.

=== List of Known Conditions ===
==== Qvars (0x00 - 0x3A) ====
Quest variables ("qvars" for short to distinguish them from other hardcoded conditions) are not written by the game executable and can freely be used by the script system. They are preserved between levels and even script heap wipes. These only have special meanings based on what you assign to them in a script yourself.

==== player_coarse_x (0x3C) ====
The X coordinate of the tile the player is currently standing in.

==== player_coarse_y (0x3D) ====
The Y coordinate of the tile the player is currently standing in.

==== levelid (0x3E) ====
The level number the player is currently exploring.

==== held_item (0x3F) ====
The ID within [[NFO Format (Shadowcaster)|itemtype.nfo]] of the object the player is currently holding as their cursor.

==== zeropage (0x40) ====
Whatever value happens to be in the first 4 bytes in DOS low memory.

==== ceilingflag (0x43) ====
Whether the ceiling (5) is drawn on this level, or if sky is drawn instead (0).

==== player_mana (0x45) ====
How much mana the player currently has.

=== Evaluation Types ===

The only properly known evaluation type is 0x83 for "equal to".

The immediate operand value is compared to the value held by the specified condition. If the two are equal, the evaluation passes.

== Creating a Function List ==
Function lists immediately follow the condition list once you are finished specifying conditions. Please note, however, that *you* are responsible for supplying the correct number of arguments; the game will not sanity check your data (it is possible for example to call <code>SP_Teleport()</code> with one argument when four are expected, leading to undefined behavior).

All arguments are always uint32_t.

=== List of Known Functions ===
==== SP_QvarAdd(which_qvar, operand) ====
Function call #0.
<code>qvar.value += operand</code>

==== SP_QvarSetAdd(which_qvar, base, operand) ====
Function call #1.
<code>qvar.value = base + operand</code>

==== SP_QvarSet(which_qvar, base) ====
Function call #2, #3.
<code>qvar.value = base</code>

==== SP_RemoveWall(x, y, ?) ====
Function call #4.

Removes a north/west wall within the tile at x,y. The "?" operand has unclear meaning at this time.

==== SP_Missile(tilex, tiley, direction, type) ====
Function call #5.

Spawn a missile at tilex,tiley moving along direction. Direction goes counter-clockwise starting at 0=east in 90-degree increments. In other words, sane values are 0-3.

==== SP_PlaySound(id) ====
Function call #6.

Play a sound by its internal ID. Some useful values are <code>1 = stone02c.voc</code>, <code>3 = chain01b.voc</code>, <code>5 = splat02b.voc</code>.

==== SP_DeleteObj(tag) ====
Function call #7.

Find one (or many) [[OJT Format (Shadowcaster)|OJT-format]] object(s) by their tag and delete all found objects from the game.

==== SP_MoveObj(tag, destx, desty, ?) ====
Function call #8.

Find one (or many) OJT-format object(s) by their tag and instantly move them to the center of the tile at destx,desty.

==== SP_ChangeTile(tilex, tiley, surface, textureid) ====
Function call #9.

Set the tile's geometry at tilex,tiley with textureid.

Surface can be: <code> 0 = floor, 1 = ceiling, 2 = north_wall, 3 = west_wall</code>. If a wall is specified as the surface type and <code>textureid == 0</code>, that wall and its collision are removed.

==== SP_Teleport(destx, desty, angle, level) ====
Function call #10.

Fade out the screen using colormap grading; move the player to <code>destx, desty</code> on <code>levelid</code> facing in direction <code>angle</code>.

<code>angle</code> ranges from 0-255, with 0 facing east and ascending values rotating counter-clockwise. North is 64, west is 128, and south is 192.

If <code>levelid == 0</code>, the player is teleported within the current level.

==== SP_SetColorMap(id) ====
Function call #11.

Immediately set the current rendering color shading table to internal-ID <code>id</code>.

ITM Format (Shadowcaster)

2026-07-25T03:47:16Z

Diema: (The struct definition was originally copied from an ImHex pattern, I accidentally left two #includes at the top that aren't important)

ITM files are found within SHADOW.LIB and contains a list of 42-byte records, each describing one item in the level. An "item" is distinguished from an "[[OJT Format (Shadowcaster)|object]]" in that items can be picked up and placed in the inventory, and typically have some effect when the player interacts with them (or uses them on scripted static objects in the level).

The following structure describes any individual ITM record.

<syntaxhighlight lang="cpp">
typedef struct {
int32_t tag;
int32_t unknown1;
int32_t unknown2;
int32_t tilex;
int32_t tiley;
int32_t unknown3;
int32_t itemtype;
int32_t stacksize;
int32_t charge;
int16_t tilesubx;
int16_t tilesuby;
int16_t unknown4;
} item_t;
</syntaxhighlight>

=== tag ===
An identifier that scripts can use to address this item. This identifier does not have to be unique.

If the item is referenced in a [[SCR Format (Shadowcaster)|script]], then all items with the referenced tag will be acted upon (such as deleting a group of items at once).

=== tilex, tiley ===
Defines the "integer" component of the item's coordinates, in terms of coarse tile coordinates (0-31). X+ is eastward, and Y+ is southward.

=== itemtype ===
The record ID within [[NFO Format (Shadowcaster)|itemtype.nfo]] that specifies most of this item's properties, such as what spell to cast when a wand is used and what graphics to display.

=== stacksize ===
The game technically supports "stacks" of items, but not very well.

You can use this field to specify if this itm contains multiple of the same (for example, a stack of 5 healing potions). In effect, this acts like a multiplier for the "charge" property.

=== charge ===
How much "mana" or "power" this item contains at spawn. This value is also treated as the maximum mana the item can hold when recharged in a mana pool.

Note however that all effects that an item can use appear to have a fixed amount of mana they require, so it is possible to create "illegal" items that can never store enough mana to execute their effect (you will see "ITEM OUT OF POWER" in the message bar in-game).

=== tilesubx, tilesuby ===
These form the "fractional" component of the item's spawn position. Valid values are 0-63, using the same coordinate system as coarse tilex/tiley. This means that storing 0 in these fields will spawn an item at the northwest most corner of its tile.

SCR Format (Shadowcaster)

2026-07-25T03:45:42Z

Diema: Added a note about terminator bytes

[[Shadowcaster]] level scripts (*.SCR) control many special effects and level-flow modifications at runtime. Such effects include changing the level environment values (which sky is drawn if any, colored lighting, fog, and darkness), teleporting the player either to a different level (or within the same one), deleting and spawning static objects or items, locking or unlocking doors, and granting metaforms or experience points. These scripts are based on the concept of conditional lists -- that is, in order for an action to take place, a (series of) condition(s) must be satisfied.

There is no header. Script code begins immediately at the start of the file. A single script block consists of a list of conditions followed immediately by a list of function calls, and finally, a terminator. A script may not begin with a function call; this is explicitly treated as invalid data by the game. Conditions always have the following form:

<code>int16_t condition_id;

uint8_t evaluation_type;

uint32_t value;</code>

There is a list of 100 hard-coded conditions the game executable recognizes, many of which are exclusively script-controlled and are not modified directly by the game. In most circumstances, <code>evaluation_type</code> is set to <code>0x83</code> to mean "equal to"; other values are not yet fully known. This is followed by an immediate value to compare against. Scripts contain no explicit flow control and rely entirely on these condition evaluations.

For example, <code>0000 83 05000000</code> will be satisfied if condition #0 is equal to 5.

A single script block may contain many such condition formulations. The function list is only executed if all such conditions are satisfied. The condition list is finished specifying conditions upon encountering a condition with its highest bit set (0x8000). These are function calls. The game contains a list of 41 hard-coded functions that level scripts may call by ID. A function call follows this format:

<code>int16_t function_id;

uint8_t numargs;

uint32_t args[...];</code>

For example, <code>0F80 01 0D000000</code> -- function call 15, one argument (0x0D). This plays song ID 13 immediately upon satisfying its preceding condition list.

A function list is finished specifying calls when the game encounters a terminator byte outside of an argument list. A terminator can be 0xFF for single-fire scripts that are "deleted" after they are run, or 0x00 in some cases for repeatable effects. If no more condition/function lists proceed after this terminator byte, the script file is finished.

ITM Format (Shadowcaster)

2026-07-25T03:44:21Z

Diema: Initial draft

ITM files are found within SHADOW.LIB and contains a list of 42-byte records, each describing one item in the level. An "item" is distinguished from an "[[OJT Format (Shadowcaster)|object]]" in that items can be picked up and placed in the inventory, and typically have some effect when the player interacts with them (or uses them on scripted static objects in the level).

The following structure describes any individual ITM record.

<syntaxhighlight lang="cpp">
#include <std/mem.pat>
#include <std/io.pat>

typedef struct {
int32_t tag;
int32_t unknown1;
int32_t unknown2;
int32_t tilex;
int32_t tiley;
int32_t unknown3;
int32_t itemtype;
int32_t stacksize;
int32_t charge;
int16_t tilesubx;
int16_t tilesuby;
int16_t unknown4;
} item_t;
</syntaxhighlight>

=== tag ===
An identifier that scripts can use to address this item. This identifier does not have to be unique.

If the item is referenced in a [[SCR Format (Shadowcaster)|script]], then all items with the referenced tag will be acted upon (such as deleting a group of items at once).

=== tilex, tiley ===
Defines the "integer" component of the item's coordinates, in terms of coarse tile coordinates (0-31). X+ is eastward, and Y+ is southward.

=== itemtype ===
The record ID within [[NFO Format (Shadowcaster)|itemtype.nfo]] that specifies most of this item's properties, such as what spell to cast when a wand is used and what graphics to display.

=== stacksize ===
The game technically supports "stacks" of items, but not very well.

You can use this field to specify if this itm contains multiple of the same (for example, a stack of 5 healing potions). In effect, this acts like a multiplier for the "charge" property.

=== charge ===
How much "mana" or "power" this item contains at spawn. This value is also treated as the maximum mana the item can hold when recharged in a mana pool.

Note however that all effects that an item can use appear to have a fixed amount of mana they require, so it is possible to create "illegal" items that can never store enough mana to execute their effect (you will see "ITEM OUT OF POWER" in the message bar in-game).

=== tilesubx, tilesuby ===
These form the "fractional" component of the item's spawn position. Valid values are 0-63, using the same coordinate system as coarse tilex/tiley. This means that storing 0 in these fields will spawn an item at the northwest most corner of its tile.

SCR Format (Shadowcaster)

2026-07-24T04:13:56Z

Diema: Initial draft -- TODO: properly format known conditions and function call IDs; provide a complete, simple example script

[[Shadowcaster]] level scripts (*.SCR) control many special effects and level-flow modifications at runtime. Such effects include changing the level environment values (which sky is drawn if any, colored lighting, fog, and darkness), teleporting the player either to a different level (or within the same one), deleting and spawning static objects or items, locking or unlocking doors, and granting metaforms or experience points. These scripts are based on the concept of conditional lists -- that is, in order for an action to take place, a (series of) condition(s) must be satisfied.

There is no header. Script code begins immediately at the start of the file. A single script block consists of a list of conditions followed immediately by a list of function calls, and finally, a terminator. A script may not begin with a function call; this is explicitly treated as invalid data by the game. Conditions always have the following form:

<code>int16_t condition_id;

uint8_t evaluation_type;

uint32_t value;</code>

There is a list of 100 hard-coded conditions the game executable recognizes, many of which are exclusively script-controlled and are not modified directly by the game. In most circumstances, <code>evaluation_type</code> is set to <code>0x83</code> to mean "equal to"; other values are not yet fully known. This is followed by an immediate value to compare against. Scripts contain no explicit flow control and rely entirely on these condition evaluations.

For example, <code>0000 83 05000000</code> will be satisfied if condition #0 is equal to 5.

A single script block may contain many such condition formulations. The function list is only executed if all such conditions are satisfied. The condition list is finished specifying conditions upon encountering a condition with its highest bit set (0x8000). These are function calls. The game contains a list of 41 hard-coded functions that level scripts may call by ID. A function call follows this format:

<code>int16_t function_id;

uint8_t numargs;

uint32_t args[...];</code>

For example, <code>0F80 01 0D000000</code> -- function call 15, one argument (0x0D). This plays song ID 13 immediately upon satisfying its preceding condition list.

A function list is finished specifying calls when the game encounters a 0xFF terminator byte outside of an argument list. If no more condition/function lists proceed after this terminator byte, the script file is finished.

File:Mod-Shadowcaster.png

2026-07-24T03:46:17Z

Diema:

MAP Format (Shadowcaster)

2026-07-24T03:42:10Z

Diema: (to conform witih the trend set that formats like Rise of the Triad's RTL format is "2D tile-based", therefore, so must this be.)

{{Map Infobox
| Type = 2D tile-based
| Layers = 9
| Games =
{{Game|Shadowcaster}}
}}

[[Shadowcaster]] contains several different file formats used for storing level data. MAP files contain the tile geometry. They are conceptually similar to [[Wolfenstein 3D]] levels, where like data is stored sequentially and different kinds of data are clearly separated into "layers". However, there is an expanded feature-set.

MAP files all follow the same format and are the same size:

<code>
uint16_t floorpic[32*32];

uint8_t floorheight[32*32];

uint16_t ceilingpic[32*32];

uint8_t ceilingheight[32*32];

uint16_t northwallpic[32*32];

uint8_t northwallheight[32*32];

uint16_t westwallpic[32*32];

uint8_t westwallheight[32*32];

uint8_t unused[32*32];
</code>

Any <code>*wallpic</code> element being set to zero will not be rendered and will not have collision. Floors and ceilings may also be set to zero, but result in rendering garbage. Height values are expressed as growing upwards relative to the player's perspective (so Z=64 is visibly closer to the floor than Z=128 in first person).

For floor/ceiling elements, the height value describes that of the northwestern-most vertex of that tile; the surrounding tiles (north, northwest, and west) will slope to meet that point. However, this feature is unfinished and results in a Doom-like texture bleeding effect that is usually undesirable.

For wall elements, textures "grow upwards" in the Z+ direction, and the height value in the MAP determines the starting/bottom Z of the texture. Walls will render upwards until either there is no more texture to draw (the texture does not tile), or a ceiling is encountered. The inverse is also true if the texture's start height is set below the floor.

The game uses a 1D occlusion array to determine wall visibility and clipping, so if there is a gap above or below the wall because of the way its height value is set, no geometry will be rendered behind it (you cannot see into other parts of the level through such a gap). If the level's environment is set to permit a sky, then sky will be drawn; otherwise, it will be filled with black.

Shadowcaster

2026-07-24T03:39:42Z

Diema:

{{Stub}}
{{Game Infobox
| Levels = Edit
| Tiles = No
| Sprites = No
| Fullscreen = No
| Sound = Edit
| Music = Edit
| Text = No
| Story = No
| Interface = No
}}

'''Shadowcaster''' is a first-person action RPG with a shapeshifting protagonist. It was developed by [[Raven Software]] and published by [[Origin Systems]].

== Tools ==
Some of these may only work if a specific version is used.
{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [http://slade.mancubus.net SLADE]
| Platform = Windows/Mac
| grp = Edit
| map = No
| gfx = Extract
| mus = Edit
| sfx = Edit
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://www.doomworld.com/forum/topic/155625-mapcaster-level-editor-for-shadowcaster/ MapCaster]
| Platform = Windows
| grp = No
| map = Edit
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://github.com/darkhaven3/libby Libby]
| Platform = Windows, Linux
| grp = Edit
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

{{BeginGameFileList}}
{{GameFile
| Name = N/A
| Format = [[XMI Format]]
| KnownFormat = Yes
| Desc = Background music
}}
{{GameFile
| Name = N/A
| Format = [[VOC Format]]
| KnownFormat = Yes
| Desc = Sound effects
}}
{{GameFile
| Name = *.lib
| Format = [[LIB Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Data archive
}}
{{GameFile
| Name = *.map
| Format = [[MAP Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Level geometry
}}
{{GameFile
| Name = *.ojt
| Format = [[OJT Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Static objects
}}
{{GameFile
| Name = *.itm
| Format = [[ITM Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Items (wands, potions)
}}
{{GameFile
| Name = *.crt
| Format = [[CRT Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Monsters
}}
{{GameFile
| Name = *.arc
| Format = [[ARC Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Monster archetypes
}}
{{GameFile
| Name = *.scr
| Format = [[SCR Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Level scripts
}}
{{GameFile
| Name = *.dor
| Format = [[DOR Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Level doors
}}
{{GameFile
| Name = itemtype.nfo
| Format = [[NFO Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Item definitions
}}
{{EndGameFileList}}

== Links ==
* [http://www.doomworld.com/vb/everything-else/43927-shadowcaster-modding/ RE discussion on the Doomworld forum]
* [http://www.doomworld.com/vb/everything-else/51101-shadowcaster-modding-2-the-remoddening/ Further RE discussion on the Doomworld forum]
* [https://www.doomworld.com/forum/topic/94899-shadowcaster-modding-3-disassembly/ Even more RE discussion on the Doomworld forum, with some disassembly, engine limits and map format investigation]

[[Category:Raven Software]]
[[Category:Origin Systems]]
[[Category:3D]]

File:MAP Format (Shadowcaster).png

2026-07-24T03:36:27Z

Diema: A custom Shadowcaster-format MAP built with MapCaster for demonstration purposes.

== Summary ==
A custom Shadowcaster-format MAP built with MapCaster for demonstration purposes.

MAP Format (Shadowcaster)

2026-07-24T03:35:26Z

Diema: Initial draft

{{Map Infobox
| Type = 3D tile-based
| Layers = 9
| Games =
{{Game|Shadowcaster}}
}}

[[Shadowcaster]] contains several different file formats used for storing level data. MAP files contain the tile geometry. They are conceptually similar to [[Wolfenstein 3D]] levels, where like data is stored sequentially and different kinds of data are clearly separated into "layers". However, there is an expanded feature-set.

MAP files all follow the same format and are the same size:

<code>
uint16_t floorpic[32*32];

uint8_t floorheight[32*32];

uint16_t ceilingpic[32*32];

uint8_t ceilingheight[32*32];

uint16_t northwallpic[32*32];

uint8_t northwallheight[32*32];

uint16_t westwallpic[32*32];

uint8_t westwallheight[32*32];

uint8_t unused[32*32];
</code>

Any <code>*wallpic</code> element being set to zero will not be rendered and will not have collision. Floors and ceilings may also be set to zero, but result in rendering garbage. Height values are expressed as growing upwards relative to the player's perspective (so Z=64 is visibly closer to the floor than Z=128 in first person).

For floor/ceiling elements, the height value describes that of the northwestern-most vertex of that tile; the surrounding tiles (north, northwest, and west) will slope to meet that point. However, this feature is unfinished and results in a Doom-like texture bleeding effect that is usually undesirable.

For wall elements, textures "grow upwards" in the Z+ direction, and the height value in the MAP determines the starting/bottom Z of the texture. Walls will render upwards until either there is no more texture to draw (the texture does not tile), or a ceiling is encountered. The inverse is also true if the texture's start height is set below the floor.

The game uses a 1D occlusion array to determine wall visibility and clipping, so if there is a gap above or below the wall because of the way its height value is set, no geometry will be rendered behind it (you cannot see into other parts of the level through such a gap). If the level's environment is set to permit a sky, then sky will be drawn; otherwise, it will be filled with black.

Shadowcaster

2026-07-24T03:24:09Z

Diema:

{{Stub}}
{{Game Infobox
| Levels = No
| Tiles = No
| Sprites = No
| Fullscreen = No
| Sound = Edit
| Music = Edit
| Text = No
| Story = No
| Interface = No
}}

'''Shadowcaster''' is a first-person action RPG with a shapeshifting protagonist. It was developed by [[Raven Software]] and published by [[Origin Systems]].

== Tools ==
Some of these may only work if a specific version is used.
{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [http://slade.mancubus.net SLADE]
| Platform = Windows/Mac
| grp = Edit
| map = No
| gfx = Extract
| mus = Edit
| sfx = Edit
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://www.doomworld.com/forum/topic/155625-mapcaster-level-editor-for-shadowcaster/ MapCaster]
| Platform = Windows
| grp = No
| map = Edit
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://github.com/darkhaven3/libby Libby]
| Platform = Windows, Linux
| grp = Edit
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

{{BeginGameFileList}}
{{GameFile
| Name = N/A
| Format = [[XMI Format]]
| KnownFormat = Yes
| Desc = Background music
}}
{{GameFile
| Name = N/A
| Format = [[VOC Format]]
| KnownFormat = Yes
| Desc = Sound effects
}}
{{GameFile
| Name = *.lib
| Format = [[LIB Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Data archive
}}
{{GameFile
| Name = *.map
| Format = [[MAP Format (Shadowcaster)]]
| KnownFormat = Yes
| Desc = Level geometry
}}
{{GameFile
| Name = *.ojt
| Format = [[OJT Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Static objects
}}
{{GameFile
| Name = *.itm
| Format = [[ITM Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Items (wands, potions)
}}
{{GameFile
| Name = *.crt
| Format = [[CRT Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Monsters
}}
{{GameFile
| Name = *.arc
| Format = [[ARC Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Monster archetypes
}}
{{GameFile
| Name = *.scr
| Format = [[SCR Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Level scripts
}}
{{GameFile
| Name = *.dor
| Format = [[DOR Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Level doors
}}
{{GameFile
| Name = itemtype.nfo
| Format = [[NFO Format (Shadowcaster)]]
| KnownFormat = Partial
| Desc = Item definitions
}}
{{EndGameFileList}}

== Links ==
* [http://www.doomworld.com/vb/everything-else/43927-shadowcaster-modding/ RE discussion on the Doomworld forum]
* [http://www.doomworld.com/vb/everything-else/51101-shadowcaster-modding-2-the-remoddening/ Further RE discussion on the Doomworld forum]
* [https://www.doomworld.com/forum/topic/94899-shadowcaster-modding-3-disassembly/ Even more RE discussion on the Doomworld forum, with some disassembly, engine limits and map format investigation]

[[Category:Raven Software]]
[[Category:Origin Systems]]
[[Category:3D]]

Shadowcaster

2026-07-24T03:13:14Z

Diema: Start adding stuff known about the game data; further format pages to come

{{Stub}}
{{Game Infobox
| Levels = No
| Tiles = No
| Sprites = No
| Fullscreen = No
| Sound = Edit
| Music = Edit
| Text = No
| Story = No
| Interface = No
}}

'''Shadowcaster''' is a first-person action RPG with a shapeshifting protagonist. It was developed by [[Raven Software]] and published by [[Origin Systems]].

== Tools ==
Some of these may only work if a specific version is used.
{{BeginFileFormatTools|Type=game}}
{{FileFormatTool
| Name = [http://slade.mancubus.net SLADE]
| Platform = Windows/Mac
| grp = Edit
| map = No
| gfx = Extract
| mus = Edit
| sfx = Edit
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://www.doomworld.com/forum/topic/155625-mapcaster-level-editor-for-shadowcaster/ MapCaster]
| Platform = Windows
| grp = No
| map = Edit
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{FileFormatTool
| Name = [https://github.com/darkhaven3/libby Libby]
| Platform = Windows, Linux
| grp = Edit
| map = No
| gfx = No
| mus = No
| sfx = No
| txt = No
| sav = No
| exe = No
}}
{{EndFileFormatTools}}

{{BeginGameFileList}}
{{GameFile
| Name = N/A
| Format = [[XMI Format]]
| KnownFormat = Yes
| Desc = Background music
}}
{{GameFile
| Name = N/A
| Format = [[VOC Format]]
| KnownFormat = Yes
| Desc = Sound effects
}}
{{GameFile
| Name = *.lib
| Format = [[Shadowcaster LIB Format]]
| KnownFormat = Yes
| Desc = Data archive
}}
{{GameFile
| Name = *.map
| Format = [[Shadowcaster MAP Format]]
| KnownFormat = Yes
| Desc = Level geometry
}}
{{GameFile
| Name = *.ojt
| Format = [[Shadowcaster OJT Format]]
| KnownFormat = Partial
| Desc = Static objects
}}
{{GameFile
| Name = *.itm
| Format = [[Shadowcaster ITM Format]]
| KnownFormat = Partial
| Desc = Items (wands, potions)
}}
{{GameFile
| Name = *.crt
| Format = [[Shadowcaster CRT Format]]
| KnownFormat = Partial
| Desc = Monsters
}}
{{GameFile
| Name = *.arc
| Format = [[Shadowcaster ARC Format]]
| KnownFormat = Partial
| Desc = Monster archetypes
}}
{{GameFile
| Name = *.scr
| Format = [[Shadowcaster SCR Format]]
| KnownFormat = Partial
| Desc = Level scripts
}}
{{GameFile
| Name = *.dor
| Format = [[Shadowcaster DOR Format]]
| KnownFormat = Partial
| Desc = Level doors
}}
{{GameFile
| Name = itemtype.nfo
| Format = [[Shadowcaster NFO Format]]
| KnownFormat = Partial
| Desc = Item definitions
}}
{{EndGameFileList}}

== Links ==
* [http://www.doomworld.com/vb/everything-else/43927-shadowcaster-modding/ RE discussion on the Doomworld forum]
* [http://www.doomworld.com/vb/everything-else/51101-shadowcaster-modding-2-the-remoddening/ Further RE discussion on the Doomworld forum]
* [https://www.doomworld.com/forum/topic/94899-shadowcaster-modding-3-disassembly/ Even more RE discussion on the Doomworld forum, with some disassembly, engine limits and map format investigation]

[[Category:Raven Software]]
[[Category:Origin Systems]]
[[Category:3D]]