-
Notifications
You must be signed in to change notification settings - Fork 0
Radoub Formats UTD
UTD files store door blueprints using the GFF format with a high-level API.
UTD (Universal Template Door) files define door templates for NWN modules — standard doors, gates, area transitions. Radoub.Formats provides a typed reader/writer and a dedicated search provider (UtdSearchProvider) for the Marlinspike search engine.
flowchart TB
UTD[UTD File] --> Identity[Identity]
UTD --> Combat[Combat / Physical]
UTD --> Lock[Lock / Trap]
UTD --> Door[Door-Specific]
UTD --> Scripts[Scripts]
Identity --> Name[ResRef, Tag, LocName, Description]
Combat --> HP[HP, Hardness, Saves]
Combat --> Appearance[Appearance, GenericType]
Lock --> LockFields[Lockable, OpenLockDC]
Lock --> TrapFields[TrapFlag, TrapType]
Door --> Transition[LinkedTo, LinkedToFlags]
Door --> LoadScreen[LoadScreenID]
Scripts --> Events[14 Event Scripts]
| Property | Type | Description |
|---|---|---|
| TemplateResRef | string | Blueprint filename (max 16 chars) |
| Tag | string | Door tag (max 32 chars) |
| LocName | CExoLocString | Door name (localized) |
| Description | CExoLocString | Description (localized) |
| Comment | string | Designer comment |
| PaletteID | byte | Toolset palette ID |
| Conversation | string | Associated .dlg file |
| Property | Type | Default | Description |
|---|---|---|---|
| Appearance | uint | 0 | Index into doortypes.2da |
| GenericType | byte | 0 | Index into genericdoors.2da (when Appearance=0) |
| HP | short | 0 | Maximum hit points |
| CurrentHP | short | 0 | Current hit points |
| Hardness | byte | 0 | Damage reduction |
| Fort | byte | 0 | Fortitude save |
| Ref | byte | 0 | Reflex save |
| Will | byte | 0 | Will save |
| Plot | bool | false | Plot object (indestructible) |
| AnimationState | byte | 0 | 0=closed, 1=opened1, 2=opened2 |
Same as UTP — see Radoub-Formats-UTP.
| Property | Type | Default | Description |
|---|---|---|---|
| LinkedTo | string | "" | Area transition target tag |
| LinkedToFlags | byte | 0 | 0=none, 1=door, 2=waypoint |
| LoadScreenID | ushort | 0 | Index into loadscreens.2da (0=destination default) |
14 event scripts, all CResRef (string):
OnClick, OnClosed, OnDamaged, OnDeath, OnDisarm, OnFailToOpen, OnHeartbeat, OnLock, OnMeleeAttacked, OnOpen, OnSpellCastAt, OnTrapTriggered, OnUnlock, OnUserDefined
Door vs Placeable scripts — Doors have OnClick (area transition) and OnFailToOpen. Placeables have OnUsed and OnInvDisturbed.
// Read
var utd = UtdReader.Read("door_met005.utd");
var utd = UtdReader.Read(byteArray);
// Write
UtdWriter.Write(utd, "door_met005.utd");
byte[] bytes = UtdWriter.Write(utd);UtdSearchProvider searches Name, Description, Tag, ResRef, Comment, Conversation, LinkedTo, all 14 scripts, and VarTable. Registered in SearchProviderFactory.
| 2DA File | Field | Purpose |
|---|---|---|
| doortypes.2da | Appearance | Door model (when >0) |
| genericdoors.2da | GenericType | Generic door model (when Appearance=0) |
| loadscreens.2da | LoadScreenID | Area transition loading screen |
| traps.2da | TrapType | Trap effect properties |
See Bioware-Legacy-DoorPlaceableGFF Section 3 (Door Struct).
Home | Index | Radoub-Formats
Page freshness: 2026-05-24
Getting Started
User Guide
Features
Help
- Manifest - Journal Editor
- Quartermaster - Creature/Inventory Editor
- Relique - Item Editor
- Reliquary - Placeable Editor (Alpha)
- Fence - Merchant/Store Editor
- Trebuchet - Radoub Launcher
- Marlinspike - Search and Replace
- Spell Check - Dictionary-based spell checking
- Token System - Dialog tokens and custom colors
Parley Internals
Manifest Internals
Quartermaster Internals
Relique Internals
Reliquary Internals
Fence Internals
Marlinspike (Search Engine)
Trebuchet Internals
Radoub.UI
Library
Low-Level Formats
High-Level Parsers
- JRL Format (.jrl)
- UTI Format (.uti) - Item blueprints
- UTC Format (.utc) - Creature blueprints
- UTM Format (.utm) - Store blueprints
- UTP Format (.utp) - Placeable blueprints
- UTD Format (.utd) - Door blueprints
- ARE Format (.are) - Area properties
- BIC Format (.bic) - Player characters
Original BioWare Aurora Engine file format specifications.
Core Formats
- GFF Format - Generic File Format
- KEY/BIF Format - Resource archives
- ERF Format - Encapsulated resources
- TLK Format - Talk tables
- 2DA Format - Data tables
- Localized Strings
- Common GFF Structs
Object Blueprints
- Creature Format (.utc)
- Item Format (.uti)
- Store Format (.utm)
- Door/Placeable (.utd/.utp)
- Encounter Format (.ute)
- Sound Object (.uts)
- Trigger Format (.utt)
- Waypoint Format (.utw)
Module/Area Files
- Conversation Format (.dlg)
- Journal Format (.jrl)
- Area File Format (.are/.git/.gic)
- Module Info (.ifo)
- Faction Format (.fac)
- Palette/ITP Format (.itp)
- SSF Format - Sound sets
Reference
Page freshness: 2026-05-24