Main menu
Secondary menu
You are here
IPRP Feats
This project provides a modified iprp_feats.2da file which increases the number of feats available as item properties, from vanilla 63 to 818. They can be easily managed in the toolset and with NWScript functions using provided constants. Except few feat cost tweaks, all modifications introduced by this project are backward-compatible with vanilla NWN.
This project is primarily aimed at module builders, players will have little use of it.
CHANGELOG
1.0 (2017-11-27)
- Initial release.
DESCRIPTION
This project serves following purposes:
- Unlocks all usable feats as item properties.
- Gives those properties cost parameters that fit well with the game.
- Provides a sandbox demo module for interactive testing purposes.
There are at least two other projects that have the same goal:
- IPE - Item Properties Expanded by Ben Harrison
- Community Patch Project by Shadooow
However this project was made from scratch and is not based on any of the above projects. It does not modify other files than iprp_feats.2da.
There are 818 feats that can be used as working item properties thanks to modified iprp_feats.2da file from this project. Previously (vanilla NWN), only 63 feats were available this way. With few exceptions, such as Ki Strike or Curse Song, all of these feats can be used immediately by all classes when added to a wearable item or to PC's creature hide.
One of this project's goals was to make those parameters of newly-added feats as balanced as possible, so they can seamlessly fit into game. For example, if a feat provides poison immunity, it will have the same cost as poison immunity property. Sometimes feats have no simple equivalents or they do not emulate other behaviors, so some artistic license had to be applied.
About 30% of total number of NWN feats was left out by this project. They are listed below together with reasons why they were omitted:
- All feats removed from game code but not from feat.2da.
- All feats with daily use limits, such as Bard Songs. Adding them as item properties gives them unlimited use, breaking game's balance.
- Informative feats that would be confusing whether they work or not: cleric domains, epic character badges, Quick To Master, Small, etc.
- Hardcoded feats and those that work only with specific classes: epic attribute modifiers (Great Wisdom, etc), Bardic Knowledge, Bone Skin, Deathless Vigor, Sacred Defense, Dual Wield, Dragon Abilities, Dragon Armor, HD Increase, Favorite Enemy, Monk AC Bonus and Monk Speed.
- Mount actions (still accessible through radial menu).
Feats added by this project are fully compatible with NWN version 1.69 in terms of NWScript API. This means you can use the IP_CONST_FEAT_* constants and they will work as intended. Because of many new feats, an additional include script, iprp_feat.nss, contains extra constants, all of which have IP_CONST_BONUS_FEAT_* name pattern (notice "BONUS"), for example: IP_CONST_BONUS_FEAT_ALERTNESS.
Most cost parameters of vanilla NWN feat item properties are unchanged by this project. There are few exceptions, though:
- Weapon Finesse: 1.20 -> 1.25 (cosmetic, negligible change).
- Disarm: 1.05 -> 1.50 (adds +1000 gp, probably a vanilla issue).
- Sneak Attack +5d6: 8.0 -> 9.0 (8.0 is for +4d6, vanilla issue).
- Mounted Combat: 0.01 -> 2.0 (added in 1.69, 0.01 = no extra cost).
- Mounted Archery: 0.01 -> 1.0 (added in 1.69, 0.01 = no extra cost).
Project's archive also contains a demo module for testing the new feats.
INSTALLATION
To install, extract contents of hak folder from project's archive into the hak folder of the game. Overwrite all files when asked.
| Attachment | Size |
|---|---|
 iprp_feats_1.0.7z (58) | 31 KB |
 iprp_feats_1.0.txt | 8.47 KB |
Thank you for making this. I have been looking for something like this for a while.
I actually had it done almost exactly a year ago. If unsure what it does, try the demo module.
How is this different from iprp_feats in community patch?
Most differences are summarized in the description above.
This is just my opinion, but I believe that most feat cost parameter values I've chosen are more closer to the game in terms of balance. For example: poison immunity feat has the same cost as poison immunity property (1). I also made some of the epic / overpowered feats really expensive. Again, for example, Devastating Criticals have cost parameter 100, while 100% Energy Resistance have 500.
I also provide an include file with constants, though I do like how in community patch you can get the property by adding 100 to feat's constant. Maybe I'll redo my file in similar fashion.
I am writing because yes I think my system of 100+id is really smart (addign constants you'll hit the max identifier problem soon) and if you make it this way it will be compatible with CPP which is also plus :)
and yes the costs aren't balanced much in CPP didn't have time for that + CPP offers cost reduction/increase property so those not satisfied with cost can change it
OK, I'll try to use the 100+FEAT system. It will be in the next patch.
Could you elaborate on the max identifier issue? It shouldn't a problem as the new constants are in a script.
Perhaps you could also find some time to check the cost parameters here? There is about 100 "controversial" feats that cannot be emulated with other properties and therefore could use some review: circle kick, greater cleave, blind fight, etc.
there is a limit on how many new identifiers you can have between toolset start throwing errors when compiling scripts
identifiers are: constants and functions prototypes/declarations including those base from nwscript.nss. I don't know the exact number but if you put all missing constants from 1.69 into single library and will include that together with for example x2_inc_spells + x3_inc_horse you will hit the issue instantly.