'You are not facing XXX'

[knockcocker]

This is as bad as ever. Please fix this.

[Indoran]

get rid of facing for spells!

[sandypaws]

Please don't. It's the only thing keeping me from getting DPs to the face on my poor rogue, when going against red-name casters.

[Indoran]

of course as you are not getting lots of spell failure due to lag...

[chickenmaniac]

get rid of facing for spells!

This.

get rid of facing for spells!

And this.

[Syllph]

My favorite is that I waste SP and get on cooldown only to see "You are not facing."

[Pantronic]

get rid of facing for spells!

If I weren't actually facing XXX, I would not be upset about getting that message. Don't get rid of facing, just fix it.

[sandypaws]

of course as you are not getting lots of spell failure due to lag...

Note the caster/divine in sig.
I like the facing mechanic. I -don't- like how lag interfaces with it, but I do like the general mechanic.

[knockcocker]

Note the caster/divine in sig.
I like the facing mechanic. I -don't- like how lag interfaces with it, but I do like the general mechanic.

Right, and it's clearly the targeting that is fubar as spells (mostly*) hit just fine if you don't use a hard target.


*Ignoring the strange quantum tunneling effect of casters/archers which decide to move just as you cast an AOE.
They seldom get hit despite clearly being within the AOE. The game seems to treat them as arriving at their
destination instantaneously.

BTW, I fully expect this to get the 'ignored by a dev' treatment just like the CL/MCL debacle that's been going on
for 18 months plus. I can honestly say this bug (coupled with phantom damage avoidance alluded to above) is
the most serious thing affecting my enjoyment of the game at the moment. If this is not fixed, and the Reconstruct
changes go ahead as they are now, I'm going to struggle to even play this game as a Premium player.

Don't fix breakables, fix bugs which are preventing your paying players from enjoying the game. Thanks.

[ZeebaNeighba]

The game seems to treat them as arriving at their
destination instantaneously.

I have a feeling this is why we have that other bug of casting a hold/dance/stun on a monster and it still slides all over the room for another 15 minutes after getting hit. Which is yet another annoying bug that's been around as long as I've played.

[sandypaws]

I have a feeling this is why we have that other bug of casting a hold/dance/stun on a monster and it still slides all over the room for another 15 minutes after getting hit. Which is yet another annoying bug that's been around as long as I've played.

Probably not, seeing as how the mass hold worked on them in the first place.
Though who knows. Strange things happen. Like with wolves, and how you can't shoot them reliably even though they're attacking your face. Not a problem with lions. Or zombies. Or bears. Just wolves. #$(*#& wolves.

[knockcocker]

Any dev comment? no?

[Bogenbroom]

You know, I really wish they'd get rid of the facing mech for touch spells, if not ranged ones. But then there are lots of cool things they could do for touch spells.

[Indoran]

You know there is no facing in PnP? I know this is not pnp... but... you know also pnp doesn't have LAG... most serious problem to facing is lag... if that lag could remain below 100 ms... facing would be a cool feature... but with lag spiking to 3000 ms at times... (under normal server stress / dont even taking mabar into consideration) well it's just not right for me to lose my sp, have my spell on cooldown then get killed when I clearly killed that thing first

[MrkGrismer]

The 'out of range' when soft-targetting mobs right in front of you seems to have gotten worse recently also.