Return of Reckoning

My problem with BA is as you mentioned it unstealths you when you use it and the target isn't in range.

Stealth up to the target, use BA, target moves, BA out of range, unstealth, ...

Try getting in range of a target and give it a half second before using BA. It will usually connect properly then.

Edit: though I'd prefer it to just work.

IB "shield of reprisal" (knockdown) is still very unreliable. Seems to fail in ~80% of the cases.

Apperantly Bo's and bgs can dw now?

Muras visual arm glitch is still there as 25% of the time their mutated arm won't show and it will be just a regular arm both relm mates and Ordo can see it


Also is dark protector working right? I started a Bg today and in an sc I put dp on tesq who was getting hit by 3 and I was not building any hate I fact unless I was directly attacking some one I built no hate from dp

Nice work on the aoe radius. Checked some and they were correct now.

TenTonHammer wrote: Also is dark protector working right? I started a Bg today and in an sc I put dp on tesq who was getting hit by 3 and I was not building any hate I fact unless I was directly attacking some one I built no hate from dp

It only grants you hatred, when you're in combat. That said, it is working wrong. Correctly you enter combat, when your DP target starts a fight. So basically it is working with the exception mentioned above.

Telen wrote:Nice work on the aoe radius. Checked some and they were correct now.

didnt test that, but very good to hear then! gj
but as i wrote yesterday in advice though, i believe that maybe together with that change something went wrong with the autohit range. atm AA range is pretty much zero feet if you count from the targeting circle on the ground of your enemy, to your actual character model.

Also it seems that Guard does simply half the damage for your target, but the Tank receives no dmg at all.


What i also saw though: If you play a WP and port into a SC you have 0 fury. ppl complained that you cannot cast stuff (because clientside says you have 0, allthough server knows you have 250 i believe it was?), but seemingly that works now!

On the other hand Tactic slots and quickbar #1 still resets the first 3 spells in 80% of the time, even though patchnotes mentioned something about tactics fix?

anyway gj on this patch so far! <3

Something extra i have to mention, what disturbs me quite a bit at the moment:

You all know the bug with having a target in range as well as in LoS , but casting on yourself instead. that somehow always occurs together with a strange Bug where i CANNOT press escape button to close down any windows like options, map or my primary and secondary target. To fix this i have to manually click on someone else, press any spell and THEN again i can press escape to remove all windows. that is extremely annoying when im in need of healing myself, while running away, but i cant untarget my stuff with the esc button. pressing tab and getting a new enemy target does not fix that it seems.

hope you can read anything useful out of that explanation, maybe this 'closing bug' gives you a little insight on any bugged packets or so?

noisestorm wrote:but as i wrote yesterday in advice though, i believe that maybe together with that change something went wrong with the autohit range. atm AA range is pretty much zero feet if you count from the targeting circle on the ground of your enemy, to your actual character model.

I tried this on my local and the AA range is correct for me.

with AM as well as with my WP i have to stand nearly inside a Mob to AA him. also heard some WLs complain about it on advice yesterday evening.

And an EDIT: for the escape bug above.. that actually occurs when some casts get Stuck as well for me O_O
I guess it always depends on the spells getting stuck, it seems like it was just coincidence, that this occured together with the LoS stuff.

So to put it in other words again:
If i have any targets, windows , inventory or anything else open and one of my castanimations gets stuck, i cannot use escape to normally close down any of my windows or to lose my targets. i first must resolve the problem with my castbar (cast anything again while it is stuck to unstuck it) and then i can use my escape button as always.

Yeah. Fixing the stuck casting is the proper way to resolve that issue - that occurs when your client is casting but the server isn't, because you cast too early. It's likely that the client keeps trying to send F_INTERRUPT instead of F_PLAYER_INFO, because you have a stuck ability, but the server sees that packet, knows you're not casting, and drops it, so you can't get the client out of the stuck state without casting another ability to break the stuck one.