-

[arakes99]

If the cool down gets upped, please up the DoT as well.. I don't want my bleeder to be unexpectedly nurfed as a conciquence to trying to balance a necessary melee feat.

Honestly I think the feat is fine as is because melees need any help they can get. Its when we see the FvS running around with expose that's a problem IMHO.

It's not possible to change this feat without negatively impacting everyone that uses it in one way or another. What builds deserve full access to a bugged feat to me is based on personal build preferences. A bug should be dealt with across the board in a fair and reasonable matter without singling out those that do and don't deserve access to it.

[chad878262]

At the end of the day, the only 'mandate' that was ever submitted by the community (and I think this was like 3 years ago now, before I joined up) was to fix the auto hit. As stated previously, the autohit cannot be fixed without ruining the feat for a large portion of character builds that frankly might as well not exist without it (i.e. there might be one lonely player out there that would keep his horribly weak/nerfed rogue *cough, Snarfy, COUGH COUGH* but bye and large those builds would no longer exist), meanwhile, the builds that (in general) people get upset about (High BAB's, Gishes, etc) would barely register such a nerf... They hit on the first attack anyway and are using the stacking -3 AC / Round to land more hits and crits.

So, based on the fact that the fix would barely hurt the build types folks wanted to impact while completely relegating a really fun (RP wise), but somewhat weak mechanically build type in to the trash bin, we decided to do nothing. If there is a huge push from the community to nerf it by increasing the cooldown, it will be reviewed and discussed again (though not until bugfixing is done and probably after crafting gets in, IMO). However, unless there is an outcry to make such a change, like many such bugs, we'll leave it alone because so far any attempts to fix the things that folks want fixed have resulted in a worse scenario, which makes doing nothing, overall the best course of action.

[Snarfy]

(i.e. there might be one lonely player out there that would keep his horribly weak/nerfed rogue *cough, Snarfy, COUGH COUGH* but bye and large those builds would no longer exist)

Nuh uh. I would march him straight up a volcano in the Greypeaks and his final moments would look something like this...

[chad878262]

Somehow I think he would still manage to look expressionless and dour throughout the entire fall....then would come back as some sort of undead balenorn with a constantly annoyed, fixed expression.


*stares flatly*
*arches a brow*
*frowns slightly*
*BOOOMM!!!!*

[vbaddict]

I don't see anything wrong with low ab builds being "harmed" by nerfing EW. If a builds viability depends on using a broken and bugged OP feat as a crutch, then that build wasn't viable to begin with. Low ab characters can't hit in melee? Really? Isn't that how, you know, the mechanics in this game are supposed to work? Bugs are there to be fixed, next time don't build around a bug. Also, "characters which are supposed to be using it" are characters with access to evasion, not "sneaks". The feat has absolutely no direct correlation to sneaking whatsoever. Seeing as a longterm solution will obviously never happen (it's been years now), we might as well finally find a simper solution.

So I guess "want to hit something? Be a class with high BAB" Some classes just weren't meant to solo the server.

Before reading this thread I had head about the auto hit problem but did not realize that the stacking AC debuff was a bug. I'm obviously mistaken about the intent behind EW as well. I'm sorry my post irritated Thids. All I can do is adjust my expectations on what a monk is meant to do in the Forgotten Realms setting and graciously accept a possible change to the feat. [I blame childhood viewing of the Kung Fu TV series for my misplaced concept of a monk!]

I would like to add, pointing blame at a player for building around an EW bug is unfair. I used the resources below when planning out my main. If there is a place we can go with more accurate information it needs to be better highlighted in these forums and/or in game. However, I'm guessing this is all we have for now. There are no bug notes on the NWN2 Wiki. Doesn't look like there is anything at all on the BGTSCC Wiki or the forums. If the hard working volunteer staff lacks the manpower document the server's content, maybe the BGTSCC community can show a little patience and understanding towards those learning this game.

NWN2 Wiki - Expose Weakness
BGTSCC Wiki

Forums
Custom and New Feats
Custom Changes

[Blackman D]

but did not realize that the stacking AC debuff was a bug

the stacking AC debuff is not a bug, its suppose to do that

the thing with that was before the work around to it, the debuff always hit because of the auto hit, but now even with the auto hit if you failed to hit the actual AC the debuff will not apply

atm the only real problem with EW is still the auto hit

[vbaddict]

the stacking AC debuff is not a bug, its suppose to do that

the thing with that was before the work around to it, the debuff always hit because of the auto hit, but now even with the auto hit if you failed to hit the actual AC the debuff will not apply

atm the only real problem with EW is still the auto hit

Thanks BMD, glad to hear the attribute of EW that helps my mediocre BAB is not a bug!