Two questions for SE

[Zoryn]

Re: Two questions for SE

My apologies, I made the wrong assumption. You totally didn't read the problem I was providing a solution for.

You're most likely right.
x3

: D

[Effedup]

Re: Two questions for SE

The "Cannot see the XXXX" has always irritated me a little bit...it seems really random at times. La Thiene Plateau is an obvious example (spend a lot of time there soloing my lowbie jobs), I can shoot through trees and such most of the time, but can't see through a fence that's 2 feet tall? And we've all gotten hung up trying to run over what looks like a tiny little crack in the ground, and always when running for your life from something trying to eat your face :) Also, when a mob can't decide where it wants to stand, so it's jumping around all over the place, hitting me, but I get the "Cannot See" over and over...irritating.

I think my biggest gripe as far as that kind of stuff goes is how mobs can move over terrain that players can't. Not a big issue at all, but can be annoying sometimes when you aggro something that shouldn't even be able to see you.

[Cotners]

Re: Two questions for SE

That's actually a separate issue. "Unable to see" is as far as I can tell a purely client-side restriction, and as such, only applies to players. I suspect if you used a third-party tool you could stop that and cast/ra through walls without pos-hacking at all.

This doesn't work. I wish it did... I can have wireframe mode on and still get the 'unable to see... ' messege.

[Aksannyi]

Re: Two questions for SE

Bugs the CRAP out of me when I'm trying to cast cure on someone and a little fucking TREE is blocking that from taking place.

Also, bugs me that I can stop running and start casting right away, but it's almost always interrupted because the server believes that I'm still running while I start casting. Usually it's something important, like Stoneskin, which I am casting while I'm kiting! Drives me nuts.

[Ziero]

Re: Two questions for SE

If you're running away your best bet is to wrap its path-finding up around enviromental objects like trees.

Or in other words, SERPENTINE!

[Evion]

Re: Two questions for SE

Aksannyi, the "still running so my spell gets interrupted even though I'm not moving" thing REALLY gets me... I understand your pain.

[Yellow Mage]

Re: Two questions for SE

1) The AI doesn't make mistakes about running/casting. When the AI decides to cast, it stops the mob's movements at the exact right moment before casting. The only way you can get a movement-based interrupt on mob casting is with a knockback-causing attack, I believe.

False. Attacks that supposedly give your enemy "knockback" are actually entirely aesthetic. Try Bind, then knockback. On a normal player, this would knock the player out of range, and they'd be unable to run back until bind wore. On a mob, though, they'd look like they were knocked back, but then they'd appear back to where they started, even if Bind hadn't wore. At least, that's what I heard.

What's also kind of annoying is that mobs can jump up/down cliffs semi-freely, whereas I sometimes get blocked by a lump of ground no higher than my tiny Tarutaru foot.

[TheGrandMom]

Re: Two questions for SE

What's also kind of annoying is that mobs can jump up/down cliffs semi-freely, whereas I sometimes get blocked by a lump of ground no higher than my tiny Tarutaru foot.

LOL AMEN to that!

[Lunaryn]

Re: Two questions for SE

This doesn't work. I wish it did... I can have wireframe mode on and still get the 'unable to see... ' messege.

I never said anything about wireframe mode. This is a client-side check, but it has nothing to do with whether you are literally capable of seeing the target (I've been in many many MANY situations where the target was perfectly visible on-screen without any adulteration of the client and still got the "Unable to see" message). As far as I can tell from what I have observed, it's got something to do with whether certain types of obstructions lie on a direct line between the camera and the target, and to some extent based on character positioning as well. I think it makes two different checks, but it most *definitely* isn't checking whether or not something gets rendered/culled. Just that there are often a LOT of 'holes' in obstructions in the game (which is probably also part of why people sometimes glitch into falling under a bridge or running past a zoneline).

[Susurrus]

Re: Two questions for SE

I never understood why I can't shoot/cast on something on the other side of a crack in the ground. Like on the other side of a small lava pit or something. Enemy would normally be in range, I can see it, but I can't shoot it cuz game says the pit in the ground is blocking my view. :(

[Lunaryn]

Re: Two questions for SE

Pit is an obstruction. Just part of the logic the client uses. Basically, if you can't move your camera through it, you can't "see" through it. Excepting for small 'holes' that develop as a result of how line of "sight" paths through the obstructed area.

[Kyleet]

Re: Two questions for SE

It happens a lot to me while pulling. What's really stupid is that the mob can be only a couple steps away, and my character's head is swiveled. She's looking them dead in the eye, and yet "unable to see" them. -.- Most of the time I can't even see what's blocking the view. And I think on a couple occasions my npc fellow has been the so-called obstruction.