Information on 2da files, which are essentially 2 dimensional array tables of information. See the left hand bar for a list of information on specific 2da files.
Note a lot of information on specific 2da files are on different pages, such as Spells and Abilities for spells.2da.
The 2da format is relatively simple, and can be read about in the Bioware documentation. It looks like this:
2DA V2.0 Column1 Column2 Column3 0 Entry1 "Entry2" ****
- The top line must be 2DA V2.0
- You can optionally include a "DEFAULT:" definition for the string that will be returned if there is no data to otherwise return. **** returns a blank string still, but if you request via. Get2DAString() an invalid row or an invalid column entry it will return the DEFAULT: value. No Bioware 2da does this (and likely shouldn't) but may be useful for custom 2da files.
- There may be one or more blank lines before the first line that contains characters, which is considered the header line
- The first column header must be blank, and that column is ignored (is usually a human readable number)
- The first column number IDs can be wrong - the game just reads each new line as a new entry (incremented from 0)
- The second and onwards columns must have the header match the in-game reference loaded, the order of columns doesn't matter. Label columns are generally ignored.
- The first column header must be blank, and that column is ignored (is usually a human readable number)
- Further lines are data rows:
- Column data - but not the header name - can be in double quotes - "text here" - to include spaces. The maximum amount of text in quotes can be 256 characters. Whether or not the game understands that one being in quotes very much depends - see individual 2da notes.
- Column data is separated by one or more whitespace characters (tabs, spaces)
- Blank data is classified with 4 stars: ****
- You can quote the stars ("****") or have a blank quoted field which, of course, is blank ("") but any other combination of stars (less, more, or in single quotes) will be returns literally.
- Entire blank rows are skipped and not counted as data rows. You must define some characters for it to be a data row.
This all comes together to mean some very odd looking 2das can be completely valid.
You can find notes on reading 2DA files in scripts at the Lexicon page for Get2DAString. Main thing to note is on error (no column or row matching etc.) and on blank entries it returns an empty string.
Missing Columns versus Blank Columns (****)
There is different behaviour for certain columns where the column is missing entirely (eg; using a old 1.69 version of a 2da) versus the column being present but blanked (****). A notable example is the additional columns in racialtypes.2da which defaults to the 1.69 implementations if the columns are not present to maintain compatibility, and where **** can actually be counted as "Empty value" instead of "Missing value" meaning different behaviour.
Order of Columns
The game generally won't care what order columns are in except for some minor exceptions;
- swearfilter.2da cannot be rearranged
- The first column of the spell preference 2da files
- itemprops.2da appears to be hardcoded due to the PropColumn in baseitems.2da (although not sure if you can add more columns to it).
It is recommended not to reorder columns on any game 2DA just in case.
Most game read 2da files (if not all) can have custom columns added but these are only useful for Get2DAString (and it's a much better idea to create a custom 2DA file for additional metadata to not hit NWSync 15MB file size limits).
In one instance in NWN:EE this has a valid use case the engine recognises: Additional "Spellbook" columns in spells.2da, which are now referenced by column name in classes.2da.
When a column for a 2da references another 2da, and the entry requires an ID to use from the other 2da (eg feats.2da having a column to link to a line in spells.2da), the ID you must give it is actually the line number offset from base (base being where index 0 starts). This basically just means 2da line ID numbers cannot be skipped, but is mostly only relevant where a persistent server has heavily modified 2da's.
This is a list of the different core 2da files (we're ignoring tileset specific ones but there will be a generic entry for them, plus the multitude of class and package 2das) with a note about the usage for client or server, and line limits (if known). Anything in this list is used by the game, the unused ones are listed later on this page.
Note: If a 2da file is listed as "Server Loaded: No" it would still be recommended to include it in relevant hakpack files if altered since Get2DAString will break, and the size of the files is very tiny in any case.
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...)
|2da file||Brief Description||Client Loaded||Server Loaded||Toolset Loaded||Line Limit||Line Limit Notes|
|actions.2da||List of actions and associated icons / TLK strings used by the GUI||Yes||Yes||No||Hardcoded||This file cannot have alterations to lines made, the references are all hardcoded.|
|ambientmusic.2da||Ambient music tracks||Yes||No||Yes||Unknown||Needs testing. GFF field is stored as INT (-2147483648 to 2147483647).|
|ambientsound.2da||Ambient sound tracks||Yes||No||Yes||Unknown||Needs testing. GFF field is stored as INT (-2147483648 to 2147483647).|
|ammunitiontypes.2da||For the hardcoded ranged weapons, what models to use for certain ammo types (eg; Fire Arrows)||Yes||No||No||Unknown / Hardcoded||Likely hardcoded, so no changes to line amounts allowed.|
|appearance.2da||Creature appearances and base properties like size etc.||Yes||Yes||Yes||Unknown||GFF field is stored as WORD (0 to 65535).|
|appearancesndset.2da||Appearance Sound Set eg what ambient sound they play, referenced by SOUNDAPPTYPE in appearance.2da||Yes||No||Yes?||Unknown||Needs testing. More can be added but not sure about the line limit.|
|armor.2da||List of armor values, although some of this is hardcoded.||Yes||Yes||Yes||Unknown||Needs testing. New AC values can be added but only incrementally (so higher AC, eg: 8, 9, 10 could be added next).|
|baseitems.2da||All the item types in the game (eg: longsword, torch, scroll)||Yes||Yes||Yes||0 - 255||Hardcoded due to network limitations; items may not function as intended.|
|bodybag.2da||The bodybag a creature will leave around.||No||Yes||Yes||0 - 255 likely||Needs testing. GFF field is stored as BYTE (0 to 255)|
|capart.2da||Creature Armor Parts, listing the model names of various bits inside a model for the client to load it properly. This is very unlikely to ever need changing however.||Yes||No||Yes||Hardcoded||Amount of armor nodes are hardcoded.|
|chargenclothes.2da||Clothing available at character generation. Important: This also needs the relevant UTI files (Item Blueprints) client side for the client to load custom clothing. The server picks up on what was chosen and generates it.||Yes||Yes||No||Unknown||Needs testing. No GFF field, is purely loaded by the engine (at chargen client side and on the server side when the client sends over what clothing choice at the end of chargen for that item to load).|
Character classes and main class options. See subpage for further details. Clients need all these parts since clients actually do all their character changes client side and send it to the server to just validate it.
0 - 254
|Hardcoded due to network limitations plus note "255" number is reserved as "CLASS_TYPE_INVALID".|
|cloakmodel.2da||Cloaks model references and options for each model. The server uses this as well as the client to check for validity with script commands changing them.||Yes||Yes||Yes||Unknown||Needs testing but likely 0 - 254 as other parts are.|
|cls_atk_xxx.2da||Standard name for classes.2da "AttackBonusTable" 2da value, defining the Base Attack Bonus progression||Yes||Yes||Yes||60||Classes are limited to 40 levels for PCs and 60 levels (mostly) for NPCs. In any case epic levels (21+) have static progression from epicattacks.2da|
|cls_bfeat_xxx.2da||Standard name for classes.2da "BonusFeatsTable" 2da value, defining the bonus feats a class gets||Yes||Yes||Yes||Unknown||Needs testing but likely the limit here is same as feat.2da|
|cls_feat_xxx.2da||Standard name for classes.2da "FeatsTable" 2da value, defining the feat availability for a class||Yes||Yes||Yes||Unknown||Needs testing but likely the limit here is same as feat.2da|
|cls_pres_xxx.2da||Standard name for classes.2da "PreReqTable" 2da value, defining the prerequisites for taking this (Prestige) class||Yes||Yes||Yes||Unknown||Needs testing but this is hardly going to ever be the longest file.|
|cls_savthr_xxx.2da||Standard name for classes.2da "SavingThrowTable" 2da value, defining the saving throw (Fortitude, Will, Reflex) progression||Yes||Yes||Yes||60||Classes are limited to 40 levels for PCs and 60 levels (mostly) for NPCs. In any case epic levels (21+) have static progression from epicsaves.2da|
|cls_skill_xxx.2da||Standard name for classes.2da "SkillsTable" 2da value, defining the skills the class has available||Yes||Yes||Yes||Unknown (likely 255)||Needs testing but is likely limited to the same size as skills.2da (255 or 32 depending on bugs)|
|cls_spgn_xxx.2da||Standard name for classes.2da "SpellGainTable" 2da value, defining the spells gained each level (How many can be cast per level). Every spellcaster needs this.||Yes||Yes||Yes||60|
Classes are limited to 40 levels for PCs and 60 levels (mostly) for NPCs.
Note in EE that spellcasters are typically limited to level 40 in the engine.
|cls_spkn_xxx.2da||Standard name for classes.2da "SpellKnownTable" 2da value, defining how many spells are known (Eg; for Bards and Sorcerers)||Yes||Yes||Yes||60|
Classes are limited to 40 levels for PCs and 60 levels (mostly) for NPCs.
Note in EE that spellcasters are typically limited to level 40 in the engine.
|cls_stat_xxx.2da||Standard name for classes.2da "StatGainTable" 2da value, defining the stat increases for the class (Eg; Dragon Disciple, Pale Master)||Yes||Yes||Yes||60||Classes are limited to 40 levels for PCs and 60 levels (mostly) for NPCs.|
|creaturesize.2da||File is hardcoded (engine values in ruleset.2da) and only used by the toolset for the names of sizes||No||No||Yes||Hardcoded||Noted in description this is basically hardcoded and is for toolset only use.|
|creaturespeed.2da||File defining the speed of PCs and NPCs||Yes||Yes||Yes||Unknown||Needs testing. This file can be extended but some lines are hardcoded. See creaturespeed.2da|
|crtemplates.2da||This defines some "creature templates" for NPCs such as "Half-Celestial" used in the toolset only. Links to ini files that load items and stat changes onto the creature blueprint.||No||No||Yes||Unknown||Needs testing. Solely for Toolset usage.|
|cursors.2da||Not a complete list of cursors, but used for trigger objects to define some mouse over cursors. Most cursors in the game are hardcoded and for the scripting OnPlayerTarget event you can set your own unrelated to this 2da.||Yes||No||Yes||Likely 255||Needs testing. GFF field is stored as BYTE (0 - 255)|
|damagehitvisual.2da||Damage VFX line sent to the client when a particular damage is inflicted by a weapon.||No||Yes||No||Hardcoded||The amount of damage types is hardcoded.|
|damagelevels.2da||Damage levels, such as "Uninjured" or "Near Death". The amount of HP each level is for is hardcoded, this is purely for clientside TLK loading.||Yes||No||No||Hardcoded||The damage levels are set in the engine, this just displays the right localised TLK string.|
|defaultacsounds.2da||The sounds of each armor when hit, thus leather armour when hit by a sword has the impact effect sound like leather. Only is loaded if the ArmorType column of appearancesndset.2da is blank, and it looks up the chest AC value.||Yes||No||No||Unknown||Needs testing. New AC values can be added but only incrementally (so higher AC, eg: 8, 9, 10 could be added next).|
|des_xxx.2da||These 2da files were used by Bioware designers to have custom systems that work with Get2DAString() in scripts, eg for crafting.||No||Yes||No||N/A||No limits as such apart from what limits 2DA files have naturally|
|diffsettings.2da||Difficulty Settings used by the game, at least the ones Bioware made editable.||Yes||Yes||No||Hardcoded||The amount of difficulty options and what options are editable is hardcoded.|
|disease.2da||Diseases defined by the game for EffectDisease or On Hit: Disease item properties. Clients are sent completed effects, not the information loaded in this file, except the name used On Hit item properties most likely.||Yes||Yes||Yes||Unknown||Needs testing.|
|domains.2da||Domains that by default only Clerics use, but now in EE any spellcaster can be assigned if setup.||Yes||Yes||No||0 - 254 likely||Needs testing. GFF field is stored as BYTE (0 - 255)|
|doortypes.2da||List of doors tied to various tilesets. Clients will load it for most likely the sound reference.||Yes||Yes||Yes||Unknown||Needs testing.|
|effecticons.2da||Effect icons used by the game, now extendable massively in EE with EffectIcon.||Yes||Yes||No|
1 - 255
|This 1 - 255 limit was confirmed in EE for EffectIcon. Previously all effect icons were hardcoded but the network traffic to send them limits the number. Line 0 is invalid.|
|encdifficulty.2da||Encounter difficulty. Used by servers for a multiplier on the "difficulty", and in toolset to set the difficulty.||No||Yes||Yes||Unknown||Needs testing. Not sure if more can be added. GFF field is stored as INT (-2147483648 to 2147483647).|
|encoding.2da||Encoding table. Not included in the game by default.||Yes||Yes||No||0 - 255||Set amount of ASCII encoding characters.|
|encumbrance.2da||Encumberance levels for amount of strength a creature has. Client uses this to show the amount you can carry. Server it is used where the speed is worked out.||Yes||Yes||No||Unknown||Needs testing. Rows go up to 100 but potentially could be extended.|
|Contains the area lighting environmental presets available in the toolset only.||No||No||Yes||Unknown||Needs testing. May be hardcoded.|
|epicattacks.2da||Attack progression for epic levels (21+). Clients and toolset is just for showing numbers.||Yes||Yes||Yes||60||Classes are limited to 40 levels for PCs and 60 levels (mostly) for NPCs. Note the epic levels are 21+ so first 20 lines would be ignored usually.|
|epicsaves.2da||Save progression for epic levels (21+). Clients and toolset is just for showing numbers.||Yes||Yes||Yes||60||Classes are limited to 40 levels for PCs and 60 levels (mostly) for NPCs. Note the epic levels are 21+ so first 20 lines would be ignored usually.|
|excitedduration.2da||"Excited" duration, ie; combat music time! Both options are the same, clients say it loads but is it used for anything? Probably not. It is also probably not worth altering this since...who knows what might happen in the engine. If you know maybe post it here!||Yes but not used?||Yes||No||Hardcoded||The entries here are hardcoded.|
|exptable.2da||Used to figure out when the characters levelup.||No||Yes||No||41||Line 41 is actually making level 40 the highest. EE has some bugs if you go over 40 levels for PCs around spellcasting.|
|feat.2da||Feats available for creatures to take, or are granted to them.||Yes||Yes||Yes|
0 - 32768
uint16 used in network however not recommended to go over 32K even if 65,536 is absolute maximum. There are likely problems with subdial feats if you do this due to how they are identified.
|footstepsounds.2da||Sound files loaded for particular footsteps depending on appearance.||Yes||No||No||Unknown||Needs testing.|
|fractionalcr.2da||Sorts fractional CR for purposes of encounter challenge rating (working out what monsters to spawn).||No||Yes||No||Hardcoded||The amount of lines are hardcoded, although perhaps you can alter bits of it, it may break something.|
|gender.2da||Essentially a list of genders for the toolset, and on clients which TLK string to load for them. Server just uses a coded list (ie like the GENDER_* constants in nwscript) although it might use it via. Get2DAString if needed.||Yes||No||Yes||Hardcoded||Even if you can add more genders you'd need NWNX to have the server end work with them properly.|
|genericdoors.2da||The generic "general" doors and their modes/info.||No||Yes||Yes||Unknown||Needs testing.|
|hen_companion.2da||Animal Companions list. Used for clients to show at levelup, and servers to load the right resref. Toolset doesn't load it since NPCs have these settings wiped.||Yes||Yes||No||Unknown||Needs testing.|
|hen_familiar.2da||Familiar list. Used for clients to show at levelup, and servers to load the right resref. Toolset doesn't load it since NPCs have these settings wiped.||Yes||Yes||No||Unknown||Needs testing.|
|inventorysnds.2da||The sounds when inventory items are moved around the inventory or picked up (column "InvSoundType" in baseitems.2da). Server just sends the column ID number to the client to find the file to play.||Yes||No||No||Unknown||Needs testing.|
Item Property - ability list.
For each IPRP file it's assumed server needs it for item property generation/properties or Get2DAString for crafting. The client will need it for item examining so the right property info is loaded.
|Yes||Yes||Yes||Hardcoded||Number of abilities are hardcoded in the engine.|
|iprp_acmodtype.2da||Item Property - AC modification type.||Yes||Yes||Yes||Hardcoded||5 hardcoded AC types.|
|iprp_addcost.2da||Item Property Cost Table - "Additional"||Yes||Yes||Yes||Unknown||Additional Cost table things like Cursed identifiers can be added here.|
|iprp_additional.2da||Item Property - "Additional"||Yes||Yes||Yes||Unknown||Additional Cost table things like Cursed identifiers can be added here.|
|iprp_aligngrp.2da||Item Property Alignment Groups||Yes||Yes||Yes||Hardcoded||Amount of alignments is hardcoded.|
|iprp_alignment.2da||Item Property Alignments||Yes||Yes||Yes||Hardcoded||Amount of alignments is hardcoded.|
|iprp_ammocost.2da||Unlimited Ammo options. Resref of the "unlimited ammo" to equip depending on if arrow, bolt or bullet.||Yes||Yes||Yes||Unknown||Looks like more could be added.|
|iprp_ammotype.2da||Unlimited Ammo "Ammunition type". Since it's tied to the weapon this is probably only used by the toolset, since the iprp_ammocost.2da determines the TLK string of the actual type (Eg; "Unlimited Fire 1d6")||Yes||Yes||Yes||Hardcoded||As with ranged weapons, ammo is hardcoded to 3 types.|
|iprp_amount.2da||Itme Property "Amount". Is simply 1, 2, 3, 4, 5 with TLK strings "Amount: 1", etc. attached. It used for things like Monster On Hit: Ability Drain [Drains Strength] [Amount: 3]||Yes||Yes||Yes||Unknown||Needs testing.|
|iprp_arcspell.2da||Item Property Arcane Spell Failure amounts.||Yes||Yes||Yes||Unknown||Additional rows can be added (eg: -1, -2)|
|iprp_base1.2da||This is an intentionally blank cost table file referenced as line 0 in iprp_costtable.2da. It is used for any property which has no cost table value for it. How does it work out the cost? well the subtype 2da tends to have a Cost column. Very confusing I know.||Yes||Yes||Yes||Leave alone||Leave it alone blank, it might break things if edited since it's note expected to have anything in it.|
|iprp_bonuscost.2da||Item Property Bonus Cost. Used for ability score increases.||Yes||Yes||Yes||Unknown||Needs testing. However ability scores may overflow/cap if going too high.|
|iprp_chargecost.2da||Item Property Charges / Use or Uses / Day options.||Yes||Yes||Yes||Hardcoded||The amount of these is hardcoded since there is no options in this 2da for what each one is defined as. So no 10 Charges / Use can be added.|
|iprp_color.2da||Item Property Light Color choice.||Yes||Yes||Yes||Hardcoded||The lights relate to particular VFX lines, thus this list is hardcoded (but changing the TLK values and assinging different VFX models/progfx info may work).|
|iprp_combatdam.2da||Item Property Extra Melee Damage type of damage||Yes||Yes||Yes||Hardcoded||Only can have the 3 main physical damage types for this item property.|
Cost Table. This defines what 2da is loaded for each CostTableResRef ID number in itempropdef.2da
You can add new item properties (which are just for the item description or to add/remove cost, and have scripted effects) by adding more rows to this.
|Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_damagecost.2da||Item Property Damage Bonus and EffectDamageShield / some other things that need static and variable bonuses like 1d6 and 2d8.||Yes||Yes||Yes||127 (or possibly 128)|
Certainly going to line 129 or higher works for the server end (damage is done correctly) but the client won't show it correctly in the character sheet because it looks up 2da line as a negative (impossible). Line 159 was tested which had the string "-97 Magical Damage" since 159 - 128 = 31, and 128 - 31 = 97.
It shows correctly on items, and higher lines are safe for NPCs to use.
|iprp_damagetype.2da||Item Property Damage Bonus type of damage to apply. Interestingly has "subdual" and "physical" as options, perhaps hinting at an earlier damage system more aligned to D&D rules.||Yes||Yes||Yes||Hardcoded||Damage types are hardcoded in the engine, although the names can be at least altered here.|
|iprp_damvulcost.2da||Item Property Damage Vulnerability cost table, eg 50% fire vulnerability.||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_feats.2da||Item Property Bonus Feat list. Keeps the amount in the toolset managable but you can extend this to be almost any feat.2da entry (some however will not function).||Yes||Yes||Yes||Unknown||Additional rows can be added for custom feats.|
|iprp_immuncost.2da||Item Property Damage Immunity cost table||Yes||Yes||Yes||Unknown||Additional rows can be added (eg: 15, 20, 30).|
|iprp_immunity.2da||Item Property Immunity: Misc table, eg: Immunity: Death Magic||Yes||Yes||Yes||Hardcoded||This seems a static hardcoded list, engine defined, which has no correlation to the script constants, sadly much smaller too.|
|iprp_kitcost.2da||Item Property Healing Kit cost table||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_lightcost.2da||Item Property Light cost table (Brightness)||Yes||Yes||Yes||Hardcoded||Specific visualeffects.2da lines are loaded with a combination of this and iprp_color.2da. Sadly these are hardcoded although the VFX lines could be altered.|
|iprp_matcost.2da||Item Property Material cost table||Yes||Yes||Yes||Unknown||Additional rows can be added. This property doesn't do anything in the engine and can be altered fine.|
|iprp_material.2da||Item Property Material table||Yes||Yes||Yes||Unknown||Additional rows can be added for new materials available in the toolset. This property doesn't do anything in the engine and can be altered fine.|
|iprp_meleecost.2da||Item Property cost table for a variety of basic +1, +2 etc properties - AC, Attack, Enchantment, Regeneration, etc.||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_monstcost.2da||Item Property Monster Damage cost table.||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_monsterhit.2da||Item Property Monster: On Hit table. It is hardcoded so should probably not be altered.||Yes||Yes||Yes||Hardcoded||These references are hardcoded, even if the 2da is used to load the correct parameter tables.|
|iprp_neg10cost.2da||Used for Item Properties; Ability Score Reduction and Skill Penalty.||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
Used for Item Properties; Enchantment Penalty (attack and damage), Damage Penalty, Decreased AC, Reduced Saving Throws, Attack Penalty
|Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_onhit.2da||Item Property On Hit table, defines all the hardcoded engine On Hit properties and the param1 values (eg; what ability to drain, the duration/change to occur, etc.). The cost table determines the DC.||Yes||Yes||Yes||Hardcoded||This list is hardcoded to engine values. However the sub properties (DC, chance/duration) can be altered for particular ones as noted.|
|iprp_onhitcost.2da||Item Property On Hit cost table (the DC of the On Hit saving throw)||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_onhitdur.2da||Item Property On Hit duration table. Used only for some On Hit properties, it defines things like 5% chance / Duration 5 rounds.||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_onhitspell.2da||Item Property On Hit Cast Spell table. Add more spells to use in this property here.||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_paramtable.2da||Item Property Parameter Table table. In itempropdef.2da the column Param1ResRef refers to this table.||Yes||Yes||Yes||Unknown||Additional rows can be added just needs testing.|
|iprp_poison.2da||Item Property On Hit: Posion. It simply lists the poison ability damage. Otherwise hardcoded.||Yes||Yes||Yes||Hardcoded||The 6 ability scores are all you're going to get.|
|iprp_protection.2da||Item Property Damage Reduction, amount of enchantment needed to penetrate it (eg; +2 would need a +2 weapon to bypass).||Yes||Yes||Yes||Unknown||This is likely hardcoded due to other aspects of the game assuming a +0 to +20 range for DR and enchanted weapon properties. However it might be extendable, but would need a lot of testing.|
|iprp_qualcost.2da||Item Property Quality cost table||Yes||Yes||Yes||Unknown||Needs testing but this is essentially a customisable item property which has no ties to the engine so could be extended fine.|
|iprp_quality.2da||Item Property Quality table||Yes||Yes||Yes||Unknown||As above.|
|iprp_redcost.2da||Item Property Reduced Container Weight cost table (eg: -20%, -40%)||Yes||Yes||Yes||Unknown||Additional rows can be added.|
|iprp_resistcost.2da||Item Property Damage Resistance cost table (Eg: 20/-, 30/-)||Yes||Yes||Yes||Unknown||Additional rows can be added (eg: 1, 2).|
|iprp_saveelement.2da||Item Property: Improved/Decreased Saving Throws. Note there are the entries for Traps, Spells, Law, Chaos, Good and Evil but without valid TLK entries which means they cannot be selected. Adding TLK entries to them allows them to be picked.||Yes||Yes||Yes||Hardcoded||The list is hardcoded, especially since it includes things that are not usual saving throw types (dummied out) like Backstab and Illusion.|
|iprp_savingthrow.2da||Item Property: Improve Saving Throw Specific and Reduce Saving Throw Specific.||Yes||Yes||Yes||Hardcoded||Hardcoded; has "All" plus the 3 base throws Fortitude, Will and Reflex.|
|iprp_skillcost.2da||Item Property: Skill Bonus cost table||Yes||Yes||Yes||Unknown||More values can likely be added needs testing to what extent and what value breaks skills in general (if you remove the cap on bonuses).|
|iprp_soakcost.2da||Item Property: Damage Reduction, the soak value cost table (eg; the 30 in Damage Reduction +15 / Soak 30)||Yes||Yes||Yes||Unknown||Additional rows can be added (eg: 1, 2).|
|iprp_spellcost.2da||Immunity: Specific Spell. Yes you have to add your new spells to this list to have specific immunities on item properties.||Yes||Yes||Yes||Unknown||Needs testing. Likely quite large.|
On Hit: Cast Spell caster level of the spell cast, eg: On Hit: Call Lightning [Level 10]
Really wish this method was used for the Cast Spell property for variable spell levels there! Alas...
|Yes||Yes||Yes||0 - 40 likely||Level 40 caster level is usually the max, might be it can go up higher needs testing.|
|iprp_spelllvcost.2da||Bonus Spell Slot of Level cost table.||Yes||Yes||Yes||Harccoded||Spells only go from level 0 to 9.|
|iprp_spelllvlimm.2da||Immunity: Spells by Level cost table.||Yes||Yes||Yes||Hardcoded||Spells only go from level 0 to 9.|
|iprp_spells.2da||Item Property: Cast Spell spell list. Not just spells, but things like genades and Activate Item is defined as a "spell".||Yes||Yes||Yes||Additional rows can be added, for custom spells.|
|iprp_spellshl.2da||Item Property Immunity: Spell School list.||Yes||Yes||Yes||Hardcoded||The spell school list is hardcoded (although the name references could be changed no new ones can be added).|
|iprp_srcost.2dai||Item Property Spell Resistance cost table.||Yes||Yes||Yes||Values can be edited.|
|iprp_trapcost.2da||Item Property Trap cost table - the index into traps.2da for each trap type at each difficulty level.||Yes||Yes||Yes||Unknown||Needs testing. You can add more difficulties as new columns needs full page on this.|
|iprp_traps.2da||Item Property Trap - this is used to define the cost multiplier for the different trap difficulties.||Yes||Yes||Yes||Unknown||Needs testing. Not hardcoded but unsure of maximum lines.|
|iprp_visualfx.2da||Item Property Visual FX - used for weapon VFX. Extendable with NWN:EE||Yes||Yes||Yes||Unknown||Can be extended for custom weapon VFX.|
|iprp_walk.2da||Item Property Special Walk. In EE you can now define more of these and use them properly.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|iprp_weightcost.2da||Item Property Weight Decrease cost table (eg: 80%, 60%).||Yes||Yes||Yes||Unknown||Additional rows can be added (eg: 0.5, 0.9).|
|iprp_weightinc.2da||Item Property Weight Increase property table (eg: 5_lbs, 10_lbs).||Yes||Yes||Yes||Unknown||Additional rows can be added (eg: 5, 10, 15).|
|itempropdef.2da||Item Property Definitions 2da. This defines what item properties there are in the game. New ones can be added more easily in EE with ItemPropertyCustom, although they show up in the toolset fine.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|itemprops.2da||Item Properties 2da - this defines what items can use what properties. If you want your new item property to be usable on an item it needs adding here. New columns can be added but most new item types reuse an existing column for ease.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended with more columns too.|
|itemvalue.2da||Item Value, controlling the items a character of a certain level can equip if the Game Option "Item Level Restrictions" is on (always off in singleplayer).||Yes||Yes||Yes||0 - 59||Classes cap at 60 so no need to extend.|
|Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizarmor.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizhelmet.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizmelee.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizpotion.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizranged.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizrods.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizscroll.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizstaves.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizthrow.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwiztrap.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|itmwizwands.2da||Toolset only; Item Wizard 2da files||No||No||Yes||Unknown||Item Wizards are not something anyone realistically will edit much so no doubt no one will test this.|
|keymap.2da||Even though it doesn't have identifying ID lines, it appears this is used to determine a lot key bindings (maybe defaults in some cases?)||Yes||Yes||No||Hardcoded||Can't add more keyboard actions|
|lightcolor.2da||Seems to define some lighting colours for main and source lights in the toolset and in game.||Yes||Yes||Yes||0-31||Adding additional rows causes a "List Index Out of Bounds" error in the toolset if you try to edit Tile Properties.|
|loadhints.2da||Load hints used on Load Screens used by the game. Client just gets a random ID to use.||Yes||No||No||Unknown||Needs testing. Since it's not used in network traffic it doubtless can be quite high.|
|loadscreens.2da||Load Screens used by the game.||Yes||Yes||Yes||Unknown||Needs testing.|
|masterfeats.2da||Master Feats contain other feat options inside them, eg; Weapon Focus. See feat.2da as wlel.||Yes||Yes||Yes||Unknown||Needs testing.|
|namefilter.2da||Used to filter bad words from the random name generator (toolset also uses this for creature names).||Yes||Maybe?||Yes||Unknown||Needs testing.|
|packages.2da||Packages are used by the class system to allow people to not bother choosing level up feats/skills. Button can be removed by ruleset.2da nowadays. Server may use it in LevelUpHenchman, and Toolset can generate NPCs using these packages.||Yes||Yes||Yes||0 - 255 for base class but higher otherwise||GFF field stores your first chosen (level 1) package as a BYTE (0 - 255). Other classes like Prestige classes don't need to be lines 0 - 255.|
|packeqXXX.2da||Package - Equipment. Can be defined as any name but this is the standard one.||Yes||Yes||Yes||Unknown||Needs testing.|
|packftXXX.2da||Package - Feats. Can be defined as any name but this is the standard one.||Yes||Yes||Yes||Unknown||Needs testing.|
|packskXXX.2da||Package - Skills. Can be defined as any name but this is the standard one.||Yes||Yes||Yes||Unknown||Needs testing.|
|packspXXX.2da||Package - Spells. Can be defined as any name but this is the standard one.||Yes||Yes||Yes||Unknown||Needs testing.|
|parts_belt.2da||Armor Belt parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_bicep.2da||Armor Bicep parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_chest.2da||Armor Chest parts. This is what really determines the AC of the appearance. The float values are floored.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_foot.2da||Armor Foot parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_forearm.2da||Armor Forearm parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_hand.2da||Armor Hand parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_legs.2da||Armor Legs parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_neck.2da||Armor Neck parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_pelvis.2da||Armor Pelvis parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_robe.2da||Armor Robe parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_shin.2da||Armor Shin parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|parts_shoulder.2da||Armor Shoulder parts.||Yes||Yes||Yes||Unknown||Needs testing. Can be extended.|
|phenotype.2da||The phenotypes available to fuller player models, eg Humans, so they can have horses, or be "Big". Server sends the ID to the client since it's purely model related.||Yes||No||Yes||0 - 20||Needs fully testing but there is a limit of 20 constants in nwscript.nss so this is likely the engine hardcoded limit.|
|placeableobjsnds.2da||The sounds placeable objects make when opened/attacked/etc. Server just sends the right ID line to the client to load the sound.||Yes||No||No||Unknown||Needs testing.|
|placeables.2da||Placeable object appearances and properties||Yes||Yes||Yes||Unknown||Needs testing.|
|poison.2da||Poisons the game uses in EffectPoison. On Hit variant is just pure ability damage.||No||Yes||No||Unknown||Needs testing.|
|polymorph.2da||Polymorphs used by EffectPolymorph which change your character into something else entirely.||No||Yes||No||Unknown||Needs testing.|
|portraits.2da||Portiaits available in the game. Users can use their own portraits (given ruleset.2da settings) but this is the list primarily used.||Yes||Yes||Yes||Unknown||Needs testing. Field is stored as WORD (0 to 65535).|
|pregen.2da||Pregenerated characters available to filter in character select. If in this list and the tickbox "Show Pregenreated Characters" is unticked they disappear as they're filtered out.||Yes||No||No||Unknown||Needs testing.|
The amount and priority of sounds and when they can be interrupted.
With EE not sure if they can be dramatically increased or not.
|Yes||No||No||Hardcoded||The line references look to be hardcoded engine references.|
|progfx.2da||NWN:EE unhardcoded "programmed effects" values.||Yes||No||No||Unknown||Likely same limit as visualeffects.2da if there is one|
|pvpsettings.2da||Toolset only list of PvP settings||No||No||Yes||Hardcoded||The PvP settings are hardcoded in the engine.|
|race_feat_xxx.2da||The feats granted when a race is chosen.||Yes||Yes||Yes||Unknown||Needs testing.|
|racialtypes.2da||Racial types the game has, for players and NPCs||Yes||Yes||Yes||255 likely||Needs testing. GFF field is set to BYTE (0 - 255)|
|ranges.2da||The ranges used for creature perception and spells.||No||Yes||No||Hardcoded||Range types are hardcoded to engine values; don't bother editing this even if they appear fine in the toolset.|
|repadjust.2da||Reputation adjustments the game makes||No||Yes||No||Hardcoded||Hardcoded list, but values can be altered.|
|replacetexture.2da||Not really sure what this does. Tiles related?||Yes||No||No||Unknown||Needs testing.|
|repute.2da||Toolset only defaults for the faction manager the game uses the modules settings.||No||No||Yes||Hardcoded||Hardcoded standard faction list|
|restduration.2da||Time it takes at each level to rest with ActionRest||No||Yes||No||60||Classes are limited to 40 levels for PCs and 60 levels (mostly) for NPCs.|
|rrf_nss.2da||The dropdown in the toolset when opening a script has these categories and simple filters available.||No||No||Yes||Unknown||Needs testing.|
|rrf_wav.2da||The dropdown in the toolset when opening a sound file has these categories and simple filters available.||No||No||Yes||Unknown||Needs testing.|
|ruleset.2da||NWN:EE allows some unhardoding of default feats and values the game uses, some very useful client side only options too.||Yes||Yes||Yes||Hardcoded||All values are hardcoded to particular lines of course.|
|skills.2da||Skills list for players. Note that many lines are hardcoded (eg; Parry) and new skills will be missing relevant skill increasing feats (eg; Skill Focus).||Yes||Yes||Yes||32||Hardcoded due to network limitations to 255 but GUI issues make it a 32 skill limit. May only affect the "Untrained" column however? https://github.com/Beamdog/nwn-issues/issues/171|
|skillvsitemcost.2da||The amount of skill needed by Use Magical Device to equip a particular magic item due to restrictions due to class/alignment/race.||No||Yes||No||Unknown||Needs testing. No doubt it could be increased in numbers though to have more granular control.|
|skyboxes.2da||Skybox model list. Skybox ID from the area is sent to client, server doesn't validate the 2da. Toolset uses it to load the list of available skyboxes.||Yes||No||Yes||Likely 255||Needs testing. GFF field is BYTE (0-255)|
|sounddefaultspos.2da||Default values for toolset placeable sound types||No||No||Yes||Hardcoded||Toolset uses this for the default values of the different placeable sound types.|
|sounddefaultstim.2da||Default values for toolset placeable sound types||No||No||Yes||Hardcoded||Toolset uses this for the default values of the different placeable sound types.|
|soundeax.2da||EAX values are still in the toolset mainly for compatibility, as of EE they are no longer used.||No||No||Yes||Hardcoded||Hardcoded but unused by the game so who cares.|
|soundset.2da||Soundset references.||Yes||No||Yes||65535 Likely||Needs testing. GFF field stores it as WORD (0 to 65535)|
|soundsettype.2da||Column "Type" in soundset.2da refers to this. The categories of soundset file in the toolset, unused out of the toolset however since only 0 matters for chargen (PC voicesets)||No||No||Yes||Unknown||Needs testing.|
|spells.2da||Spells and abilities usable by creatures||Yes||Yes||Yes||4096||Possibly the limit - needs testing, but is to do with 12 bits available for the "spell radial" entry being sent over the network. May have been removed at some point but needs fully testing.|
|spellschools.2da||Spell schools. The amount is hardcoded but you should be able to alter the TLK strings now.||Yes||Yes||No||Hardcoded||Hardcoded list|
|statescripts.2da||State scripts run when under the effect of certain effects, also shows the games default priority list for them||No||Yes||No||Hardcoded||Entirely hardcoded.|
|stringtokens.2da||String tokens like <Man/Woman> used in conversations and in general. See Conversations.||No||Yes||Yes||Unknown||Actions are presumably hard-coded. Action 1 gendered lines (e.g. King/Queen) can be added. That can include new colour tokens (e.g. StartYellow). Other actions have not been investigated,|
|surfacemat.2da||Surface material definitions, such as grass/water/lava. In EE now extended with actions and able to be affected in hakpack files.||Yes||Yes||Yes||64||0 through 63 are valid lines for this in patch 1.84.8193.29 and up.|
|swearfilter.2da||Stops swearing in the game if [ui.chat.swear-filter] is enabled in settings.tml (I think this is a client only option? Needs testing!). Note the columns cannot be rearranged for whatever reason.||Yes||Yes||No||Unknown||Needs testing.|
Tailmodel reference file. Note that Bioware added a lot of "real" models to be used with invisible appearance things for scaling. Bit unnecessary nowadays in EE!
Server just sends the ID number to the client to load the model in this file.
|Yes||No||Yes||Unknown||Given there are over 5000 lines the answer is "High"|
|tilecolor.2da||Loaded by the game but does it do anything or does lightcolor.2da||No||Yes||Unknown||Unknown||Needs testing (if it's even in use).|
|XXX_edge.2da||Tileset edge information. One per tileset.||No||Yes||Yes||Unknown||Needs testing.|
|traps.2da||Traps, which are item properties and the placed on objects/as trap triggers on the ground.||Yes||Yes||Yes||Unknown||Needs testing.|
|vfx_persistent.2da||Persistent VFX, ie items created with EffectAreaOfEffect.||No||Yes||No||0 - 255|
|visualeffects.2da||Visual Effects the game uses, called from the game (see Hardcoded VFX References) or by EffectVisualEffect.||Yes||Yes||No||Unknown||Needs testing.|
|waypoint.2da||Toolset only waypoint definition file. Basically waypoints are not "real" so this defines the different types so they show properly in the toolset with a model.||No||No||Yes||Unknown||Needs testing.|
|weaponsounds.2da||This is a file referenced for sounds from baseitems.2da, what is being used labelled on the left, and the thing it is hitting as a column name.||Yes||No||No||Unknown||Needs testing.|
|weathertypes.2da||Weather related 2da. Server just tells client which line number to load.||Yes||No||No||Unknown||Needs testing.|
Wing models reference file. Wings are things on the back node so can include weapons and scabbards etc.
Server just sends the reference ID number for the client to load.
Used to value the XP given from monsters using the default game XP.
If you set the XP slider in the module to 0 it will disable killer XP from this file, then you can grant your own XP on death.
|No||Yes||No||40 or 60||Players can only be level 40 normally so the file only goes up to 40. NPCs can be 60.|
Unused 2da files
Bioware left in some 2da files from early development (before game release) or they're now unused in NWN:EE. These files are not loaded by the game, toolset or Get2DAString at all and can be ignored. They do get confusing however.
|2da File Name||Type||Notes|
See vfx_persistent.2da instead
|armorparts.2da||Unused||While it appeared to maybe at one time sort the separate armor parts out, it doesn't seem to be used by the toolset and instead the differnet parts_XXX.2da files are used, and for heads it just lists all the models.|
|armourtypes.2da||Unused||While the GFF documentation suggests it is used, the game really just ignores it and uses defaultacsounds.2da to look up which AC value gets which sound effect. 0 being no armor or clothing.|
|caarmorclass.2da||Unused||Early armor class system or holdover from an older game perhaps.|
|categories.2da||Unused||Not loaded by the game, in fact not even a valid 2da file (it's missing line 0). The constants for TALENT_CATEGORY_XXX are just hardcoded in the engine. Adding things to do this does nothing.|
|catype.2da||Unused||"P", "H", "GIHE", "C", "A" - mysterious! category types? Early phenotype listing? Or model complexity listing?|
|combatmodes.2da||Unused||Unused references to (a limited set) of combat action modes|
|doortype.2da||Unused||See doortypes.2da instead|
Pretty much a blank file. See visualeffects.2da instead
|gamespyrooms.2da||1.69 only||Gamespy no longer used / this isn't used|
"Dancing_Scimitar" IPRP 2da file by the looks of it, alas an unusable item property
|iprp_monsterdam.2da||Unused||Seems to be unused since creature weapons use a base item type to define the Monster Damage item property damage. Since it contains an entry for "Bite/Rend" it was probably tested this way and then changed in development.|
|iprp_slotscost.2da||Unused||Blank, maybe at some stage the inventory was more BG style and "slot cost" was to do with extending it.|
|iprp_staminacost.2da||Unused||Blank, obviously no stamina in the game|
|iprp_terraintype.2da||Unused||Blank but would have obviously been used for the "Restriction: Terrain" item property.|
|iprp_trapsize.2da||Unused||Is unused given it's not referenced in any 2da file, and misses the "Epic" mokier so the toolset doesn't use it. Maybe a pre-release had traps of varying ground size and it is a leftover.|
|metamagic.2da||Unused||Appears to be unused by the game making all of these hardcoded references, similar to categories.2da how it looks usable but isn't|
|nwconfig.2da||1.69 only||Unused as of NWN:EE since it removes the "settings" nwconfig program.|
|nwconfig2.2da||1.69 only||Looks like it's something to do with the legacy launcher which popped up before running 1.69|
|placeabletypes.2da||Unused||I think an old toolset 2da, now there are proper pallets for placeable types|
|resistancecost.2da||Unused||Blank 2da file, probably from early dev|
Replaced probably by rrf_wav.2da and would be toolset specific anyway
|soundgain.2da||Unused||Seems to be unused by the game and toolset, but should define the loudness and distance of sounds. Given theg ames default perception range is 45M maybe at one point you could see much further (up to 100M!)|
|soundprovider.2da||1.69 only||As of EE this is no longer used, since it refers to Miles and EAX both of which were replaced with OpenAL|
|soundtypes.2da||Unused||Sounds are not tied to a 2da, but are done by resource name|
|treasurescale.2da||Unused||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. Possibly was part of early Item Wizard generations (instead it gives a magic item range, None to Godly).|
|vfx_fire_forget.2da||Unused||Pretty early dev file, very empty. See visualeffects.2da instead.|
|videoquality.2da||1.69 only||No longer used in EE, was the old 1.69 video quality settings - in the launcher I think|
|Unused||Seems to not be in use when file is altered so likely some old XP system file|
Parts 2da files
**This section applies to ALL parts 2da files EXCEPT parts_robe.2da**
The toolset indexes each part according to the float value assigned to the ACBONUS column in descending order (e.g., 0.00 is listed at the top and 8.00 at the bottom of the Toolset dropdown menus). You can sort parts with the same ACBONUS value using the two digits to the right of the decimal in the float value (e.g., 0.01, 0.02, 0.03).
The ACBONUS column is NOT used by any parts 2da EXCEPT parts_chest.2da. Here, the float value is used to determine the AC of that particular chest piece. However, only the digit to the left of the decimal matters - as in other parts 2da files, the right digits can be used to index chest pieces within their respective ACBONUS values (e.g., 8.01, 8.02, 8.03, etc.).
NOTE, in most cases a body part's model number will NEVER match its number in the Toolset dropdown menu.
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.
Client and Serverside 2das
The game as a whole is made up of the client and the server. A singleplayer game essentially runs both at once for the local user - of course other players may still join if it is created as a network game. Therefore it is important to understand which is which, since some 2da files you don't need to include at all in hakpack or nwsync resource lists, and can be left in the .mod or override folder on a PW server perfectly fine.
The client ones tend to be based around levelling up, appeareances, visuals (icons, vfx, textures, etc.) and sounds (the latter 3 servers don't even load of course). Servers need to know about all the resources loaded by the game in regards to objects, spells, etc.
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
|2da load reference||2da Name||Notes|
|m_paIPRPCostTables // all of them||All cost tables in iprp_costtable.2da column "Name"||Example: iprp_bonuscost.2da|
|m_pSurfaceMaterialTable||surfacemat.2da||Loaded at game start so you cannot change it in a hakpack file, only in the override folder|
|m_pIPRPLightTable||Not sure - probably iprp_lightcost.2da ?|
Presumably also all the relevant class package 2das
|chargenclothes.2da||Clothing items must be part of the base game, or included in the hak as UTI resources|
|Likely needed for both (chargen needs feat.2da, and server obviously needs it for backend stuff)|
|namefilter.2da||No bad words, naughty! Probably char gen only?|
|swearfilter.2da||No swearing for you!|
|prioritygroups.2da||Sound related but may be just client side (along with some others) usually never edited by hakpacks anyway.|
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.
It is always recommended to have these available on the server if only for Get2DAString lookups.
|2da load reference||2da Name||Notes|
|m_pPartTable||capart.2da||Armor Model appearance related|
|m_pArmorTypesTable||armourtypes.2da||Sounds loading (cloth, leather, plate, chain)|
|m_pTailModelTable||tailmodel.2da||Model appearance related|
|m_pWingModelTable||wingmodel.2da||Model appearance related|
Model appearance related
Note: CopyItemAndModify() may use this server-side in some instances (non-PLT based ones which there are none in the base game).
|m_pCursorTable||cursors.2da||For the cursors for certain default game actions.|
|m_pActionsTable||actions.2da||For GUI icons list (player action list top left)|
|m_pAmbientMusicTable||ambientmusic.2da||Server tells client which line to load, which refers to this for the sound files|
|m_pAmbientSoundTable||ambientsound.2da||Server tells client which line to load, which refers to this for the sound files|
|m_pKeymapTable||keymap.2da||Client GUI default keys/shortcuts|
|m_pDamageLevelTable||GUI showing how damaged something is (Formats the text over creatures heads)|
|m_pEffectIconsTable||effecticons.2da||GUI effect icons (top right, inspect panel on items/characters, character sheet)|
|m_pLoadHintsTable||loadhints.2da||Loading string text loading|
|m_pSwearFilterTable||swearfilter.2da||It's funny how this is here. I presume it alters incoming messages not outgoing ones? Needs testing. Servers can implement changes to PC chat to implement a filter using OnPlayerChat event.|
|m_pPhenoTypeTable||phenotype.2da||Model appearance related|
|m_pWeatherTypesTable||weathertypes.2da||Client is just told which line to load|
|2da load reference||2da Name||Notes|
|Any custom 2da||eg: des_crft_aparts.2da||Loaded with Get2DAString so entirely script based access|
|m_pStateScriptsTable||statescripts.2da||Runs specific scripts|
|m_pPoisonTable||poison.2da||Applies effects / timings of effect changes|
|m_pDiseaseTable||disease.2da||Applies effects / scripts / timing of effect changes|
|m_pRepAdjustmentsTable||repadjust.2da||Engine changes to "reputation" ie; if they're hostile or not.|
|m_pFractionalCRTable||fractionalcr.2da||Works out how much a goblin with 1/4CR is "worth" in the engine XP system/"difficulty" tags (eg; "Easy" enemy when inspected)|
|m_pEncounterDifficultyTable||encdifficulty.2da||The "value" column is loaded when referenced from the encounters GFF|
|m_pCategoryTable||categories.2da||Used by the functions for talents. Some is hardcoded (eg; potion lines). So yeah.|
|m_pExcitedDurationTable||excitedduration.2da||Presumably amount of time in milliseconds (so 10 seconds) the thing is considered in combat after the events listed|
|m_pRestDurationTable||restduration.2da||Amount of milliseconds to sit on the ground for|
|m_pXpBase||xptable.2da||Used for giving out XP|
Note the "45.0M" range for streaming in usable placeables is hardcoded, and a maximum of visibility regardless of values here of any creature object.
|m_pDamageHitVisualTable||damagehitvisual.2da||Sends a relevant visualeffect.2da line number to the client|
|m_pBodyBagTable||bodybag.2da||References a placeables.2da line|
|m_pIPRPMonsterDamageTable||iprp_monstercost.2da||Monster Damage item property table|
|m_pOnHitTable||iprp_onhit.2da||Note this pretty much is hardcoded|
Source of what is referenced by the game engine (not complete - some 2da files seem to be loaded from elsewhere such as swear filters). It relates to this file: https://github.com/nwnxee/unified/blob/master/NWNXLib/API/API/CTwoDimArrays.hpp
// client+server m_paIPRPCostTables // all of them m_pAppearanceTable m_pGenderTable m_pSurfaceMaterialTable m_pVisualEffectTable m_pPersistentVisualEffectTable m_pCreatureSpeedTable m_pDoorTypesTable m_pGenericDoorsTable m_pPlaceablesTable m_pAreaTransitionTable m_pIPRPSpells m_pIPRPLightTable m_pIPRPColor m_pIPRPMelee m_pItemPropDefTable m_pItemPropsTable m_pCreatureSizeTable m_pArmorTable m_pEncumbranceTable m_pPortraitTable m_pPartsChest m_pSpellSchoolTable m_pTrapTable m_pLightColorTable m_pIPRPDamageTable m_pPartsRobe m_pItemValue m_pPackages m_pRuleset // client only m_pPartTable m_pArmorTypesTable m_pTileColorTable m_pReplaceTextureTable m_pTailModelTable m_pWingModelTable m_pCloakModelTable m_pCursorTable m_pActionsTable m_pAmbientMusicTable m_pAmbientSoundTable m_pFootstepSoundsTable m_pAppearanceSoundsTable m_pWeaponSoundsTable m_pDefaultACSoundsTable m_pAmmunitionTypesTable m_pKeymapTable m_pPlaceableSoundsTable m_pDamageLevelTable m_pEffectIconsTable m_pLoadHintsTable m_pSwearFilterTable m_pPhenoTypeTable m_pIPRPVisualFxTable m_pWeatherTypesTable m_pProgFxTable // server only m_pStateScriptsTable m_pPoisonTable m_pDiseaseTable m_pRepAdjustmentsTable m_pFractionalCRTable m_pEncounterDifficultyTable m_pCategoryTable m_pExcitedDurationTable m_pRestDurationTable m_pPartsBelt m_pPartsBicep m_pPartsFoot m_pPartsForearm m_pPartsHand m_pPartsLegs m_pPartsNeck m_pPartsPelvis m_pPartsShin m_pPartsShoulder m_pXpBase m_pAssociatesAnimalCompanionTable m_pAssociatesFamiliarTable m_pSkillVsItemCostTable m_pRangesTable m_pPolymorphTable m_pDamageHitVisualTable m_pBodyBagTable m_pIPRPFeatsTable m_pIPRPMonsterDamageTable m_pOnHitTable m_pOnHitSpellTable m_pOnHitDurationTable m_pIPRPACModTypeTable m_pIPRPWeightIncTable m_pIPRPArcSpell m_pIPRPBonusCostTable m_pIPRPSRCostTable m_pIPRPNeg5CostTable