Page History

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

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.

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.

1 to 65535 (uint16)

2147483647 (int32)

Functionally: limit of ability score amounts (127, maybe higher with NWNX)

environment.2da

0 - 65535

uint16 used in network and in the engine, it should be fine to use up to 65535 since Subfeat Spells use values above this to identify them.

However this needs fully testing with some potentially clashing ID's to be 100% sure.

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.

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.

Cost Table index is used in the engine as uint8_t

Individual Cost Table values are uint16_t (0 - 65535) for custom 2das, most of the standard ones have other limits.

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.

Used for Item Properties; Enchantment Penalty (attack and damage), Damage Penalty, Decreased AC, Reduced Saving Throws, Attack Penalty

Parameter Table index is used in the engine as uint8_t

Individual Parameter values are uint8_t (0 - 255).

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.

If it's extendable it's subtype so uint16_t max.

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.

Now new ones can be added with savingthrowtypes.2da.

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...

Stored and sent over network as WORD/uint16_t and in the GFF as WORD same as itemprops.

Note Subtype values (which don't get their own lookup table) are stored as uint16_t so 0 - 65535 (although the game may limit the value or cast it into smaller numbers so be careful!).

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.

The server only uses this to validate an item property can exist on a given item (stops scripting adding random properties to random items). Clientside is for some debug function no one can use and Toolset uses it to make the list of what item properties are on what item.

itmwizammo.2da

No network traffic involved, purely clientside and entirely random. If you remove the campaign-only lines (so the random loop choosing them doens't pick them, it doesn't just filter them out before choosing) it'll mean you can use every line, else it'd be good to restrict it to a mere 214,748,364 so it doesn't overflow the loop.

The game should load all the rows.

Note this is a rare 2da file where the columns are hardcoded, and column "1" is always assumed to be "FILENAME".

The amount and priority of sounds and when they can be interrupted.

With EE not sure if they can be dramatically increased or not.

0 - 255

Do not alter or delete the default lines (except maybe the numbers involved) the engine has a lot of hardcoding around them, for spells, player ranges, default monster ranges, etc. TBH easier to leave this alone.

GFF field is set to BYTE (0 - 255) thus the line limit.

The toolset won't load more options but these can be set in the GFF.

This is unused Bioware functionality to replace, on a particular tile, a texture named "replace_tex" by the given texturename linked to in this 2da file. This is...pretty much superceded by an array of texture functions in nwscript now. However who knows you might be able to use it.

Bioware probably intended it for flags more than anything going by the contents. Due to no toolset support you'd be hard pressed using this!

Saved as a BYTE / uint8_t on the GFF ("Tile_ReplaceTex", not settable in the toolset) and sent as such in the network traffic.

All values are hardcoded - but are tied to the LABEL column (by text identifier) not the line ID.

Allows altering the default saving throw types (eg Cold, Fire, Death) and add new ones the client will correctly see.

Need to also edit iprp_saveelement for the item property versions.

GFF field is BYTE (0-255) and the game engine stores it in memory as uint8_t.

The client technically loads this but does nothing with it. It instead hardcodes the values so only 0 and 2 work for PCs. However it does store the values retrieved from soundset.2da referring to this 2da in a uint8_t array.

The toolset could potentially use higher values but do you really need that many categories?

0 - 65535

65535 is the likely limit of this due to having 0xFFFF as the mask for the spell ID in the quickbar.

BIC saving and loading uses WORD (65535) and there may be other assumptions of the engine around uint16_t as well.

Going over this might work for creature and placeable only cast spells but 65K spells is quite a bit!

String tokens like <Man/Woman> used in conversations and in general. See Conversations.

You can actually add your own to this file. I haven't tested if it runs properly serverside (ie GetStringByStrRef) but likely not, instead it sends the data to the client to be sorted locally.

Stops showing (some) swearing in the game clientside if [ui.chat.swear-filter] is enabled in settings.tml.

Servers send messages and clients then filter it. Doesn't stop swearing being sent however, and can't be enabled serverside.

Note the columns cannot be rearranged, about the only 2da this matters.

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.

Limited to BYTE / uint8_t in engine/network traffic, and stored in GFF as BYTE too. See traps.2da for info on how builder-placed unrecoverable traps don't need unique lines.

2147483647 (int32) (8192.36)

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.

xpbaseconst.2da

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.