Request to ease conditions for combos

[Buddhsie]

learn to play... seriously. Other groups are doing the combos just fine. So its not the game, its you.

position requirements arent too restrictive. It should be possible to screw up the combo, otherwise all you got in the update was a damage boost instead of a combat system.

The only reason that archers do not have positional requirements is due to the radial distance between them and the target would cause them to run very far to get into the proper position with the risk of an enemy turning, or dieing before they could get there. Unless your silly enough to be locked on a target, melees do not have this issue. they can get to the correct side in a second or less.

Shoot, even while tanking on Glad I can pull off the combo that starts from behind without turning a mob... solo.

I am sorry if you are having issues, but the problem isnt the battle system.

I can guarantee you you aren't as good at combo positioning as I am. That being said I think this issue needs to be addressed for the sake of class balance between melees and Archers. The example being the moogle fight - in which Archer is the preferred damage dealer class was already tackled. The same thing also applies to large groups within strongholds, particularly concerning MRD combo Path of the Storm -> Whirlwind. This being missed by even a single MRD can result in a group wipe.

My point is the intention of the devs was not to let lag or enemy movement come between players completing combos, and I simply proposed an idea that would remove the problem. Please keep your arrogance and critical comments out of the discussion.

[Bahn]

My point is the intention of the devs was not to let lag or enemy movement come between players completing combos, and I simply proposed an idea that would remove the problem. Please keep your arrogance and critical comments out of the discussion.

For the first part, I wholeheartedly agree, for the reasons you and NoctisUmbra stated (and I normally don't agree with him). The position update latency that has been documented on numerous occasions rears its ugly head for these combos. This is not a "lrn2play" issue as the previous poster you were replying to so "eloquently" stated - it's an issue with how the client-server relationship deals with position updates - something we have little control over.

+1 to getting this fixed up - and I think there was another thread requesting this too.