Possible small interface target range bug

Mu online season 21 - grand opening

KingTony

Loyal Member
Loyal Member
Oct 15, 2014
302
2
44
Not sure if this is intended or not but seems like a bug to me considering other classes can cast spells just off the screen, but i can't target / shoot anything in the red.

loAs38i.jpg
 
Last edited:

Chriz

Captain Lurker
VIP
Mar 24, 2003
1,198
1
336
315
LOMCN
I think this intended to prevent users using the small inter face from having a higher range.. same happens on my wiz cant hit anything in thoes regions
 

Silencer

Comedian
Golden Oldie
Feb 9, 2008
1,853
48
135
LOMCN HQ with Tai, eating bagels.
I think the point KingTony is making is not whether it should or should not miss those areas, but that it should be the same for everyone; if Archers and Taos cannot hit areas deemed to be 'Off Screen' - then Wizards should not be able to either.
 

KingTony

Loyal Member
Loyal Member
Oct 15, 2014
302
2
44
I think the point KingTony is making is not whether it should or should not miss those areas, but that it should be the same for everyone; if Archers and Taos cannot hit areas deemed to be 'Off Screen' - then Wizards should not be able to either.

This exactly, and if wizzys are hitting off screen and indeed it is a bug i would assume that it's a major and needs fixing asap.
 

GimmeAKitKat

Loyal Member
Loyal Member
Jun 11, 2014
403
0
43
Archers I believe have to be able to put their cursor on centre mass as with all single target spells, so it needs to be on screen. Wizzies/tao's AOE however extend past the screen 1/2 spaces depending on the spell, so the wizzies aren't casting met/blizz on you, they are casting it next to you, 1 space offscreen, the spell itself is extending onto you.

Personally I don't think that extension is an issue, its a part of AOE mechanics, the problem is that you cant see the spell animations if the caster is off screen so have no idea your being hit by met/blizz, you just lose half your health to a blank screen. Im not certain when this changed either as I don't recall this animation issue was present originally.