ARE Format (Area Static Blueprint)

An .are file is an area’s static setup: its name, whether it counts as interior or exterior, its weather and grass, its sun and moon lighting and fog, and the scripts that fire at area level. Everything that moves around in the area, creatures and doors included, lives in the module’s GIT rather than here.

This page documents ARE’s field defaults, the confirmed-dead legacy fields still written by older tools, and the 52-field swoop-racing minigame subsystem. Evidence is drawn from Ghidra decompilation of swkotor.exe (K1 GOG build), cross-checked against a full K1 install’s vanilla .are corpus. The tables below are lookup surfaces, meant to be searched rather than read start to end.

At a Glance

Field Schema

The format’s field families, as an orientation before the full list.

Note

The ARE never gets re-saved. It gets re-copied. When a module is saved, the engine doesn’t parse or rewrite a single ARE field. CSWSModule::SaveModuleFinish hands the area’s static ARE resource to a generic “copy this resource type verbatim” helper, which looks up whatever ARE the resource manager currently has bound for that area and copies it byte-for-byte into the save archive. Every engine rule and clamping behaviour documented on this page (weather truncation, fog clamping, tag lowercasing, and so on) applies only to the initial parse when a module is freshly loaded, never to the save/resume cycle.

The area’s dynamic, session-changeable state, meaning weather, stealth XP, map exploration, cameras and transition flags, lives entirely in the module’s GIT resource instead, not in a re-saved ARE. If you’re building a save-editing tool, patch the GIT; don’t expect to patch an ARE inside a save archive.

Engine Audits & Decompilation

Read from CSWSArea::LoadArea at 0x0050e190 in swkotor.exe. Provenance: derived, not attested. The rows below have not been separately re-derived, so they sit on the reverse-engineering queue.

The initial LoadArea dispatch branches out to parse the .are GFF, .lyt layout, .git instance tracking, and .pth bounds. The engine processes roughly 61 scalar fields, 4 scripts, 3 lists, and a nested minigame struct within the LoadAreaHeader subroutine.

Core Environmental Identity

Interior areas lose their weather If Flags (Bit 0) marks the area as interior, the engine zeroes every weather property on load, discarding whatever the file set.

Weather & Terrain Generation

Area Lighting & Sun/Moon Tracking

KOTOR handles dynamic sunlight constraints separately between Sun and Moon.

DayNightCycle doesn’t inherit its own constructed default. The area constructor sets day_night_cycle = 1 (cycle on) before any GFF read happens, but the read itself uses a hardcoded literal 0 as its fallback, not the constructed value, so an area missing DayNightCycle loads with the cycle forced off, silently overriding what the object was built with. This looks like it could be an engine oversight (the constructor’s own default is never actually reachable through this load path), but intent aside, the mechanism is unambiguous: absent means 0, not 1. IsNight and LightingScheme share the ordinary unconditional-0 pattern with no such mismatch. NoRest, TransPending, TransPendNextID, and TransPendCurrID also carry over a constructed value (all 0/false), same practical outcome as an unconditional default given the single-call-path caveat above.

Grass_Emissive and the entire Dirty* overlay set are confirmed dead in this K1 build, not merely unread. None of their field-name strings, Grass_Emissive, DirtyARGBOne/Two/Three, DirtySizeOne/Two/Three, DirtyFormulaOne/Two/DirtyFormulaThre and DirtyFuncOne/Two/Three, exist anywhere in swkotor.exe’s string table, verified against a binary-wide search that does find every neighbouring Grass_* field. This is stronger than “the loader doesn’t consume it”: no code path in this build can even look these fields up. Treat them the same as DisableTransit/NoHangBack/PlayerOnly/PlayerVsPlayer below, toolset-only and invisible to K1’s engine.

Map Transitions & Saving states

The map block sits behind three gates

The geographic vectors, MapResX and the coordinate structs like WorldPt1X, are read only when all three hold:

1. A minimap TGA or TPC asset matching the level name exists on disk.
2. The Map sub-struct is present in the GFF.
3. MapResX’s resolved value is nonzero.

MapResX reads with an unconditional literal default of 0, so an absent MapResX is a gating sentinel rather than merely a zero. That 0 is tested directly, and where it holds the engine skips NorthAxis, MapPt* and WorldPt* entirely and falls through to a disabled map with MapZoom fixed at 1.

Where the block is read, MapPt goes through a dual path checking whether the field is formally FLOAT or INT. An absent MapPt1X, MapPt1Y, MapPt2X or MapPt2Y resolves to 0 either way: the INT branch reads a literal 0, and the FLOAT branch’s 0.0 survives its floor conversion. NorthAxis defaults to 0. WorldPt1X, WorldPt1Y, WorldPt2X and WorldPt2Y are independent FLOAT reads defaulting to 0.0, with no gating between them.

StealthXPCurrent chains its default off StealthXPMax

Both are snapshotted as DWORDs, and they default by different mechanisms. StealthXPMax uses the ordinary carry-over, its own prior value, zero-initialised by the constructor. StealthXPCurrent defaults to whatever StealthXPMax just resolved to, not to its own prior value.

On a fresh load both land on 0 either way, so only the mechanism differs. After the read the engine clamps StealthXPCurrent down to StealthXPMax where it exceeds it.

Per-Room EnvAudio

Each entry in the Rooms list carries its own EnvAudio INT, read by LoadAreaHeader alongside that room’s AmbientScale, defaulting to 0 when absent. It’s a genuine per-room reverb/environment-audio zone selector, not inert data: CSWRoom::SetRoomEnvAudioProps matches each room by name and copies its EnvAudio/AmbientScale pair into the client-side audio setup that runs when an area loads. (The exact downstream reverb table or effect it selects wasn’t traced past that per-room handoff.)

Don’t confuse this with a same-named field on the GIT’s own area-level AreaProperties struct (see GIT’s AreaProperties.EnvAudio). That one is a different struct entirely, and unlike this per-room field, it’s never read by anything.

Rooms and PartSounds: Remaining Field Defaults, and Two Confirmed-Dead Fields

No entry-level presence-chain abort exists in either list: the room loop and the nested PartSounds loop both process every index regardless of whether an individual GetListElement call succeeds, so a partially-specified entry is always kept, with each field defaulting independently.

RoomName defaults to an empty string if missing, unconditional. It is the same name SetRoomEnvAudioProps matches against a live room, so an empty RoomName simply never matches anything. AmbientScale defaults to 0.0, unconditional and independently gated from EnvAudio’s own default (the two are read back-to-back but neither gates the other). ForceRating and DisableWeather are confirmed dead the same decisive way as Grass_Emissive/Dirty* above: neither field-name string exists anywhere in swkotor.exe, confirmed by a binary-wide search. Toolset-only in this build.

PartSounds entries: Looping defaults to 0/false, unconditional. ModelPart defaults to an empty string, unconditional. OmenEvent is read as a CExoString, not the INT its name might suggest, confirmed by its sole cross-reference in the binary landing on a ReadFieldCExoString call inside this exact loop, and defaults to an empty string, unconditional. Sound defaults to an empty resref, unconditional; the (possibly-default) result is appended to the room’s sound list regardless of whether the file actually supplied one.

Expansion_List Defaults

Expansion_Name defaults to an empty localized string if missing, unconditional. Expansion_ID defaults to 0, unconditional. The list itself is only processed at all if the Expansion_List field is present in the GFF, a list-level gate rather than a per-entry one. Once inside, no entry is ever dropped for a missing field, same as Rooms/PartSounds above.

The Minigame Struct

Read via CSWMiniGame::Load (0x006723d0). If a minigame context triggers, the .are reads the nested Type (DWORD mapping 1=Swoop, 2=Turret), then the float properties governing movement:

The Player struct, each Enemies list entry, and each Obstacles list entry are three genuinely different shapes rather than siblings sharing one flat layout. Player and Enemies share a common vehicle base (hitpoints, a nested weapon Gun_Banks list, Scripts, Sounds) with Player adding its own movement/track-boundary fields on top, while Obstacles are a much lighter leaf with only a Scripts struct. See the Swoop & Turret Minigame Deep Dive for the full field-by-field breakdown and absent-field defaults.

Implemented Linter Rules (Rakata-Lint)

Phase 1 (intra-resource, no context)

Implemented under rakata_lint::rules::are.

1. ARE-001 (Context Discards): Warns when interior areas (Flags & 1) carry non-zero ChanceRain, ChanceSnow, ChanceLightning, or WindPower; the engine discards weather for interiors.
2. ARE-002 (Weather Truncation): Warns when ChanceRain, ChanceSnow, ChanceLightning, or WindPower exceed 255; the engine truncates these to bytes at runtime.
3. ARE-003 (Fog Clamping): Warns when MoonFogNear/Far or SunFogNear/Far are negative; the engine clamps fog distances to >= 0.0.
4. ARE-004 (Tag Lowercasing): Warns when Tag contains uppercase characters; the engine lowercases area tags on load.
5. ARE-005 (Toolset Fields): Informs when DisableTransit, NoHangBack, PlayerOnly, or PlayerVsPlayer are set; never read by the K1 engine.

Phase 2 (resource existence, requires LintContext)

Implemented under rakata_lint::rules::are_range.

6. ARE-006 (Resref Existence): Warns when any of OnEnter, OnExit, OnHeartbeat, or OnUserDefined (.ncs) does not resolve, or when any Rooms[i].PartSounds[j].Sound (.wav) does not resolve in the configured resource sources.

Pending

• Grass Texture Fallback: Informs when Grass_TexName is empty; the engine treats this as the literal string "grass".
• Texture / MiniGame Resref Existence: DefaultEnvMap, Grass_TexName, and the nested MiniGame model / track / music graph. ResourceTypeCode mapping for engine-specific texture and model packs is still being audited.

Every label the schema declares

Generated from the schema, so no label can be quietly left out. How to read these tables.

What the engine does with each field

Fields nobody has examined

Whether the engine reads these has not been established, which is not the same as establishing that it does not. Where When absent carries an answer, that half is settled.