List caster: /face a target behind you and immediately start casting → cast possible ☺
Non-list caster: /face a target behind you and immediately start casting → cast impossible (target not visible) ☹

This is the case on Uthgard.

This was the case on Live, too (at least in 2007 on Live/GOA). I can’t test if this is the still the case on Live.

I’d consider this a bug. If it was fixed at a later time on Live, would it be possible to apply this fix here, too? If it is not fixed on Live, would it be possible to fix it here on Uthgard anyway?

list caster?

btw this seems should be on bugreports

Ilerget wrote:list caster?

btw this seems should be on bugreports

list casters include ones whom benefit from acuity buff (aka cloth wearers)
ive heard reports of not in view working differently on certain classes, but id say its probably a ping issue

from what i tested they are all the same

u cant cast immediately after /face because theres a small delay before u REALLY face the enemy and this made me learn to use fast turn around with mouse allowing me to start casting faster than using /face (Im talking about cabby which is in the list casters, right?)

even if u switch ur target and directly /face afterwards, u will face the old target.

...jump=> face => no delay.

pythion wrote:ive heard reports of not in view working differently on certain classes, but id say its probably a ping issue

Well, that would mean I have always a different ping on non-list casters. It's reproducible every time, without exceptions. So no, I don't think this is related to ping. It has to do with the difference between non-list and list casters.

pythion wrote:from what i tested they are all the same

To make sure that we are on the same page, it can easily be tested this way:

Quickbarslot 1: /macro Face /face
Quickbarslot 2: any offensive, targeted spell

Target a mob, turn your back to the mob (180°). Now press 1 followed by 2.

If you are a Bard, the Mezz will not be casted because the target is not visible.
If you are a Mentalist, the Mezz will be casted.

Imo that's a custom change for all "quickcast" classes. They made it to circumvent the abuse that you can hinder the caster from quickcasting.
Is it live like? no

Celteen wrote:Imo that's a custom change for all "quickcast" classes. They made it to circumvent the abuse that you can hinder the caster from quickcasting.
Is it live like? no

Are you in fantasy land?

Abydos wrote:

Celteen wrote:Imo that's a custom change for all "quickcast" classes. They made it to circumvent the abuse that you can hinder the caster from quickcasting.
Is it live like? no

Are you in fantasy land?

lol blue stated somewhere that they changed to custom behavior, to prevent the "running trough - out of view"

Magicco wrote:lol blue stated somewhere that they changed to custom behavior, to prevent the "running trough - out of view"

Learn to read. We don't have customized handling for quick casts or "QC-classes" at all. There is no special handling for list/non-list casters in regard to out-of-view behavior. All use the same mechanisms.

/face is a client side command and server will not notice it until the packet for it was sent by the client and received by the server. The cast command can arrive earlier than the position/heading update.

we talk about the "live-like" behaviour of running trough other to get out-of-view for the enemy.

on uth its not possible cause u tweaked sth^^

z z z

Magicco wrote:we talk about the "live-like" behaviour of running trough other to get out-of-view for the enemy.

on uth its not possible cause u tweaked sth^^

Ya, I remember this from some years ago, blue said there was a code that extends the view into the rear arc slightly beyond what live does if one of the people is moving, so that you can't exploit uthgards pings to do run throughs.


I could dig up the thread but don't feel like it. It is still possible to run through here, just MUCH harder to do consistently than live. And ya, that is totally different issue than /face

its a bad thing to not be able to exploit an obvious bug with the game?