Bear Warrior: Officially THERE! Sorta.. maybe.. kinda..

[Akroma666]

Attention QC and Valefort

I officially concede to the bear warrior damage argument! After working with Valefort and noticing a bug in his coding with how glove/weapon damage was added, he has fixed the issue and I now feel the damage is PERFECT.

Against undead mobs with 5 DR I deal between 28-34 damage on average. This is EXACTLY where I was trying to push the damage numbers on builds like mine who are powerbuild focused on damage. I now feel basic builds will come shortly behind that for average or RP builders and this will be a perfect happy spot for the class.

I would like to personally thank each and every one of you for putting up with my outcry's and those that helped theory craft solutions with me. Thanks guys!

I will still try and focus on getting a few more combat abilities in the pipeline as well as the prevention to the shift-back con loss death, but for now, the class is working and very playable. See discussion here: viewtopic.php?f=443&t=58104

I encourage everyone to give this revamped class a shot!

[Slade]

Hate to thread-jack, but I'd rather not open a new post for this:

I played my BW over the weekend after a couple months away, and on 3 out of 3 shifts I got hit by the walk-mesh bug that strips all of my gear bonuses (AC, stats, cloak regen, now damage) and then doubles my bear stats. This bug has been around from the very start and really impacts survival.

So I really have to disagree with the "the class is working and very playable" statement. Has there ever been a statement on getting this (class-breaking) bug fixed?

The weapon damage bonus was a much needed addition, though.

[Valefort]

Walkmesh bug ? Can you describe what happened/what happens ?

[Slade]

Any time a shifted BW snags on the terrain while moving--like climbing the stairs in the Orog fort--the "remove polymorph" animation plays: you get the bright lights, you change back to a humanoid, and all your gear buffs are stripped. You then immediately get shifted *back* to bear form, minus gear buffs, but now with double the bear stats. Duration seems to be refreshed, too, but then the polymorph penalties aren't automatically removed when bear form ends and you have to manually revert.

Happens very frequently around ramps and hills. Orog fort, Serpent Hills, High Hedge, basilisks. It's been a consistent problem on every BW I've rolled since release.

It's like the game thinks you're too fat to get through wherever you're going, so it reduces your hitbox to allow you pass but then messes up on reapplying stuff.

[Akroma666]

Any time a shifted BW snags on the terrain while moving--like climbing the stairs in the Orog fort--the "remove polymorph" animation plays: you get the bright lights, you change back to a humanoid, and all your gear buffs are stripped. You then immediately get shifted *back* to bear form, minus gear buffs, but now with double the bear stats. Duration seems to be refreshed, too, but then the polymorph penalties aren't automatically removed when bear form ends and you have to manually revert.

Happens very frequently around ramps and hills. Orog fort, Serpent Hills, High Hedge, basilisks. It's been a consistent problem on every BW I've rolled since release.

It's like the game thinks you're too fat to get through wherever you're going, so it reduces your hitbox to allow you pass but then messes up on reapplying stuff.

Good god Valefort! Is this what I've been trying to figure out since day one?!

[Aspect of Sorrow]

Heightmap / walkmesh has no bearing on any function than the position of a player respective to it and it's measure of pathfinding.

[Endelyon]

I don't think it's a walkmesh issue. I think it's caused by the character being saved while the polymorph is active. A line of code needs to be added to the functions that disables character saving when the PC is polymorphed.

[Akroma666]

I don't think it's a walkmesh issue. I think it's caused by the character being saved while the polymorph is active. A line of code needs to be added to the functions that disables character saving when the PC is polymorphed.

Please..

[Flasmix]

This is rather unbearable. I do enjoy the right to bear arms though.

[Akroma666]

Let's inspire a friendly competition and get this some attention shall we.. to the person who actually fixes and solves this annoying shift back bug, I will pay for one full month of server time ($114.12) or the equal amount to a charity of their choosing!

The bug must be completely squashed and I will be testing it.

[Flasmix]

Disable character saving while in any polymorph/wildshape ability.

Bug fixed.

[Akroma666]

Code it in Flasmix! Get that $$$

[Endelyon]

Let's inspire a friendly competition and get this some attention shall we.. to the person who actually fixes and solves this annoying shift back bug, I will pay for one full month of server time ($114.12) or the equal amount to a charity of their choosing!

The bug must be completely squashed and I will be testing it.

While I'm sure you just mean for it to be a fun competition, this strikes me as dangerously close to monetizing our development process. I'd like to remind our users that while we do accept donations for the server (and in fact subside on them completely to fund its costs) that we don't do so conditionally and a promise of a donation won't get your issue moved to the head of the queue or prioritized in any fashion it already wouldn't be.

We are well aware (in theory) of what is causing the issue and will try to squash this bug in a timely manner, but it won't be given any special treatment.

[Akroma666]

My offer still stands unless you want me to remove it. It could be now or a year from now (good i hope not) and I will still make my donation.

[Slade]

I don't think it's a walkmesh issue. I think it's caused by the character being saved while the polymorph is active. A line of code needs to be added to the functions that disables character saving when the PC is polymorphed.

What determines when a characters saves? I had it happen twice in fifteen seconds yesterday, and then not again for the next twenty minutes while I was actively trying to cause it so I could record it.