Cormyr and the Dalelands

I'm not sure if this is already a thing, so I'm sorry if it is!

High ECL characters (+3, +4) are treated as though their ECL is character levels. (Which is fair!)  They have a lower hard level cap, and they apply for ascension earlier since ECL counts towards when they become Epic level.

But, that's not applied for feats due to ecl not being part of the engine.  Level 18, for a +3 ECL, is really level 21 in all other ways.  

So my question/suggestion is, would they be able to request a feat swap for any epic feat they meet the requirements for, at that level?  They're epic characters at that point, as far as all the drawbacks are concerned.

Per pen and paper rules, ECL is not counted toward your feats.  You earn feats by CLASS level, not character level.

I hear ya Bella, but that's not our implimentation of ECL.  ECL is just an xp penalty in pen and paper to slow progression and keep a party leveling at relative power.  

In CD, since it's a PW and everyone levels seperaretely, we treat it as actual levels.  With good reason; if we didn't, ECLs over time would be too powerful.  But by changing this, we have also shorted them a bit on potential epic feats due to the lower max level cap.

If a character is treated as being epic level in our system, and suffers the xp cap penalties of being epic level, why can they not take an epic feat?

Uhm, No, we don't treat character level the same as class level.  If we did, then there wouldn't be the level caps at character levels instead of class levels.

ECL is not "just an xp penalty" in Pen and Paper.  It's an added set of levels that count toward your total level.  Our implementation is as close to that as we can do with the restraints of NWN1.

The ONLY exception to this is the tier system, whereby ECL characters gain access to tiers by character level instead of class level.

I think I may have misunderstood how we define "epic characters".  Because we do have a situation where you have post-ascension characters unable to qualify for epic feats who's only requirement is the character being of epic level, if they have a high enough ECL.  That's not normily a scenario in pen and paper, since there isn't an "ascension" cap by default and your epic-ness is determined only by class level.

If that's intended, alrighty, and not a big deal.  I never suggested moving feats around if there was any misunderstanding, that's hard-coded and too crazy to bother with.  I suppose too, this only affects a small percentage of the playerbase anyway.

Upon further reflection, I can better see the logic behind why it exists this way.  There are a lot of instances where a certain character/class level is required for a feat.  Epic feats just require 21 class levels, and has nothing to do with ascension.

... Kirin, you ninja-ed my reply.  >.>  

Sometimes it's just more efficient to debate yourself!   

Some of that is pure engine limitation. In other things, we have done some swaps in the past, as standard PNP did exactly that - I seem to remember one of the FR sourcebooks had a Frost Giant with class levels who had epic feats/etc, even though she had less than 20 class levels, because her ECL/etc pushed her over 20th.

Overall it would probably depend on what was being asked for.

Remember, with Epic Spells, you still need access to level 9 spells, for one - but a Level 17 ECL 4 Wizard would be eligible, whereas a Level 17 ECL 2 wouldn't be, nor would a level 15 wizard 4 fighter who was ECL 4.

Make sense?

Not to conflate or confuse things here, but to chime in to make sure I have clarity for my own sake:

So, say you have a 17+ ecl 4 fighter. Assuming you meet all the other prereqs (str 25+, weapon focus, cleave, great cleave, imp crit, overwhelming crit) in such a scenario as you describe above, would the character be eligible to have devastating critical added before hitting 21? I'm not certain if this feat actually requires you to have the 'Epic Character' feat you get at 21 (wiki doesn't say) but it does say it is an epic feat.

Mmm. It's a little ambiguous, but my reading of the p&p rules is that an ECL 17+4 character is an epic character. And epic characters can select epic feats, as long as they meet the other prerequisites.

"Epic characters—those characters whose character level is 21st or higher—are handled slightly differently than nonepic characters. While they continue to gain most of the customary benefits of gaining levels, some benefits are replaced by alternative gains." (DMG 3.5e)

"MONSTERS AS EPIC CHARACTERS: The epic rules in this section also work for monsters with character levels, using the creature's effective character level (ECL) instead of just its class levels." (DMG 3.5e)

"EPIC FEATS: The following feats are available only to epic characters." (DMG 3.5e)

(Emphasis added)

The problem is, this reading of the rules is extremely difficult to do in NWN, both because it would require lots of extra LETOs, and because this reading would /also/ suggest that the ECL epic characters gain epic save and BAB progression instead of normal save and BAB progression. And that stuff is hardcoded. Because of those technical constraints, most NWN servers (understandably) opt for the less reasonable but more technically feasible interpretation of the rules - namely that you need 21 'hit dice' to start getting epic progression instead of normal progression.

That's my reading at least.

I'm pretty sure the example I'm thinking of is in Lost Empire of Faerun, which is the one FR book I can't find my physical copy of -.-

To be honest: for the reasons you cited I think it's best we divert from the core books on this one. As FW and suddenperihelion both noted, the epic system is kinda hard-coded into the engine and exceptionally difficult to change. Thus, the only way to give ECL characters epic feats/progression would be to rig it through LETOs...which would make our already busy LETO'er even busier and mean more time between other LETOs like ECL setups and what-not.

So...as much as I'd love for Voss to be able to get Dev Crit before hitting 21st, I don't think it's worth changing a system that works well enough if it means inconveniencing so many.

The system is not as hard coded as seems to be believed. All epic feats are accessible through feat.2da and can be given different requirements. Creating an underlying system to support selecting epic feats pre-epic levels would be entirely viable. The only limitation I can think of is that the ECL modified PC would need a feat added at a certain level VIA LETO, but this is one of those things that NWNX can solve. On the other hand, using epic AB/save progression is a lot less viable without extensive scripting, admittedly.

The hardcoded part is the AB/save part. In some sense, nothing is "hardcoded" - if you are working with enough NWNX and custom server or client modifications, anything can be changed; in this case, you could put in a custom scripted "level up" function that replaces the default level-up benefits with the corrected levelup benefits using NWNX. But that seems like a lot of work for something that would produce very small benefits (we're really talking about a fairly small change that only lasts a couple levelups).

As for the proposed system of creating a new system for pre-epic selection of epic feats, that's certainly an option. But it's not so clear to me that scripting up an automated system (and making sure it played nice with all the cls_feat_*.2da files) would be all that much less labor-intensive than the LETO route.

I should preface this by mentioning that I'm completely neutral about the issue of if something like this should get done, I just wanted to point out that it's viable and there's an easy way to do it.


I'm saying that this (meaning the idea of them receiving epic feats earlier) is entirely viable with absolutely no scripting provided you're willing to LETO ECL characters once when they ascend. The NWNX component is a convenience to eliminate the need for LETO. It would be a single line looking something like this:

if(iECLAdjustedLevel > 20) NWNXFuncs_AddFeat(oPC, FEAT_EPIC_CHARACTER, iTrueLevel);
The 2da adjustments would also be annoying, but not actually too intensive. The roadmap for completion largely depends on what the PreReqEpic column in feat.2da actually does. I don't know if the engine checks for actual epic levels (21+) or if it checks for the epic character feat (1001) when it's flagged. If it's the latter, this is super easy because you just need to add the feat to the character. If it's the former, you're stuck with a roadmap that looks like this:

1. Parse feat.2da for all entries with PreReqEpic flagged 1.
2. Examine all entries in that list -- check which fields you can use to flag an epic character. PREREQFEAT1 and PREREQFEAT2 might be 100% viable simply because even in cases where there are two feats specified, several times it's not necessary (feat A will require feat B, ergo feat B does not need to be specified). This would be the mildly annoying part.
3. Use the field you have selected to create the flag. Assuming PREREQFEAT1/2, you add FEAT_EPIC_CHARACTER (1001) to the necessary field.
4. Set all of the PreReqEpic flags to 0.

Obviously that's pretty general but since 2da files are trivial to parse you could write something in any language you're comfortable with to do everything except figure out which field you should use.


I'm not sure what the issue with the cls_feat_*.2da files would be? I suppose you could select a feat that you would've been granted later on in some cases, but that's already possible in vanilla NWN IIRC.

That said, in terms of economy of time, the real time waster would be testing the changes. Actually implementing what I talked about above would probably take an hour or two if you're familiar with basic Regex, file parsing, and have a basic knowledge of the .2da format (they're just a plain text tab delimited 2 dimensional array with a fairly simple header).

Then again NWN is a harsh mistress and inclined to piss on everything you try to do, but that's why I mentioned that testing would be the actual painful part.

I'm inclined to leave the system as it stands.  Many more mechanical issues I'd like to look at before this sort of thing tbh.

That won't work as you've written it. But it's an interesting idea, and I think a few minor tweaks could make it work, at least in the overwhelming majority of cases.

I guess it's no longer of general interest to the CD community now that Vincent has said no, but feel free to PM me if you are interested in discussing the technical details more!

I can understand why Vincent doesn't want to implement it, though it's still interesting to talk about.

That said, it's a very general road map, so I'm confused as to what wouldn't work. Can you specify why it won't work as I've written it? If it requires minor tweaks, can you specify what they are? You also stated that there would be a need to make an automated system "play nice" with the cls_feat_*.2da files, but I still don't understand what that means. The cls_feat_*.2da files don't relate to base feat requisites. Can you explain?

I am genuinely curious since you seem to be indicating there's a technical issue and there's no point in not specifying it.