150 pages weeeeee
http://forum.square-enix.com/ffxiv/t...-fix-something.
150 pages weeeeee
http://forum.square-enix.com/ffxiv/t...-fix-something.
Cause that boss is a joke and all you have to do is get dispelled, and if you are caster, use sure cast to not get your spell interrupted
(I almost never dodge it neither :P)
Yeah, or be right quick about moving out.. I have read that if you are precise about the dodge (stop moving once you are out of the circle) and start an action (use a spell or skill?) your position checks gets forced and it's actually more effective than just running further out. I still have to try this out since I'm not home, but it sounds true, plus the best times I've dodged everything sucessfully, I was actually also trying to optimize my damage by moving as little as necessary and casting right away (to get more spells off, as a BLM). So guys, if you are having troubles. Please try this strategy.With all indicators in this game, it seems like you have to move before you see it. In this case, you have to watch the boss, once he turns around, just start moving. I know it's not a fix because that's something SE needs to look into but it's a work around for this fight.
P.S.: SE, fix this goddamn issue. : D
Use an ability after moving out of the indicator zones. The client apparently only updates the server when an ability forces it to or every Xms or so. The server also believes anything the client tells it as far as movement/location, which is why hex editing teleportation bots work. You'll also never rubber band in this game, regardless of how bad your lag is, as the server isn't enforcing any movement patterns.
If you want some practice, roll a tank and spend level 15-50 running dungeons, you'll quickly learn to time a hit in as soon as you strafe out of cleaves.
I'm 100% positive about this, and noticed it leveling my PAL after the 2nd or third dungeon dodging AEs. It may take some experimentation to figure out what abilities per class cause an ability check, however I'm positive this works. Either that or I've got some magical copy of FF14 that gives me mystical powers that I'm unaware of.
Last edited by CianaIezuborn; 11-06-2013 at 05:15 AM.
The answer:This... am I seeing this correctly...
OK first... Says who?
Here's what I see since I've been playing this since the beginning of it's existence.
1.) We had a game with zero use for dodging mechanics to start with.
2.) Darkhold was introduced and the need to dodge Ogre slams and Batraal lazers raised a few eyebrows... Let the latency youtube begin.
3.) Ifrit was born and the issue became glaringly painful. It was paired with action lock not allowing you to move when performing an action. You couldn't even cancel.
Ever since this point SE has done nothing but develop ways to avoid lock and make the game feel smooth and seemless. Now we complain about gliding.
What about this to you favors turn-based over action RPG.
I understand what you are trying to say and do here but, you do not understand game engines and programming. The indicator is there because of something called a "hitbox". which is the reason why also you can, in many different games, hit a massive dragon with a melee weapon from miles away. If they were to apply a hit box on moving particles in-game; such as plumes. Trust me you would have more problems than just lag. Game mechanics and engine mechanics are all hidden within the graphics to make the look and feel seem legit. The real issue here is that the hitbox does not register with your toons hitbox and the server/client does not ping back and forth fast enough.The lag is created from poor server management and high game engine output. Basically they made a game engine that their servers can not handle. It will be fixed all it takes is time to work out the engine kinks.
What happens behind the scenes:
Monster ability goes off = red indicator pops
1)Game engine registers your position; along with anyone else's position around the ability - this is a number for the engine, like coordinate.
2)You move calculates your position along with everyone else's position < the problem is here. sometimes when you move because the engine is throwing so much information at the server it lags on return to the client.
3) Ability happens in real time; game uses the information last recorded which could be your new position or your original position depending on how much the sever lagged to send the info back and forth.
A quick way to fix a position issue is to after moving out of the indicator quickly cast/use an ability to send a signal that this ability is being used at this coordinate. This is not something that works every time. "60% of the time it works, every time."
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.