Page History

...

There are a limit to the amount of lines the engine will properly use for 2da files. This is restricted due to network traffic (even in SP there is a "server" running) since the game was made for dialup so Bioware coded in a lot of practical limits to lower packet sizes (presumably...)

Unused 2da files

Bioware left in some 2da files from early development (before game release). These files are not loaded by the game, toolset or Get2DAString at all and can be ignored. They do get confusing however.

• areaeffects.2da - See persistent.2da instead
• caarmorclass.2da - remnants of armour system?
• catype.2da - remnants of creature parts system?
• combatmodes.2da - Unused references to (a limited set) of combat action modes
• doortype.2da - See doortypes.2da instead
• effectanim.2da - See visualeffects.2da instead
• metamagic.2da - Appears to be unused by the game making all of these hardcoded
• nwconfig.2da - Unused as of NWN:EE since it removes the "settings" nwconfig program.
• nwconfig2.2da - Was this ever used?
• placeabletypes.2da - Should be replaced by the pallet system
• resistancecost.2da - Blank
• soundcatfilters.2da - Replaced probably by rrf_wav.2da and would be toolset specific anyway
• soundtypes.2da - Sounds are not tied to a 2da, but are done by resource name
• treasurescale.2da - I don't think this is used anywhere of note. It'd be used in the toolset I'd guess but there isn't a treasure generation system there.
• vfx_fire_forget.2da - See visualeffects.2da instead

Designer 2da files

These are strictly used by Get2DAString and not used by the game inherently. However the systems they relate to are things like crafting, which is called by default game scripts and conversations the PCs can activate.

They are all prefixed des_ - and being only used by Get2DAString they are serverside only.

There is one special case here: x3restrict.2da is used in the default game spells to restrict polymorph spells when casting on a horse. Added for horse support.

Toolset only 2da files

These are only used by the toolset, not directly by the game:

• environment.2da - Used to load some initial lighting settings in the Area Properties.
• itmwizXXX.2da - Item Wizard 2da files, they relates to what properties are valid for each item type (eg; Melee) and are generated by the wizards.
• repute.2da - Used to define the default reputations of Player, Hostile, Commoner and Merchant in a new module
• rrf_nss.2da - Filters for scripts in the toolset
• rrf_wav.2da - Filters for sounds in the toolset
• waypoint.2da - "waypoint" types, of course in game are never rendered

Client and Serverside 2das

...

It is recommended of course for the server to have copies of everything (if only for Get2DAString lookups) while you can lessen the amount put in client hakpacks or on nwsync if sending certain ones to the client.

Note: If a file is not listed here (or above as a toolset only, or unused one) it might still be used!

Client and Server

Client Only

While many of these are only loaded by the game client, the toolset would still make regular use of them, for instance, to be able to have a blueprint reference a particular wing model on a suitable NPC.

...

...