Thread: re: Known Issues After Patch 4.5 (Jan. 17, 18)

Originally Posted by Arya_Leviathan

That wouldn't work either, again, the issue is with the server tic, it's 2-3 seconds. You can easily do an instant cast an ability and swap quickly into another job before the server registers you did any of that, that's how the exploit works. If this was a fix, they would've done this already since 1.0.

I run a software developer.

You don't know what you're talking about. The server can and does restrict how many packets can be sent from the client at once and accepted by the server. Global cooldown is part of this scheme. They can make an adjustment to resolve this which won't require completely re-writing the XP award rules because the core problem is not the rules, but the limited restrictions on class swapping. That's the actual problem. The thing is engineers often think about the most complicated way to address something since coding is very complicated itself, and sometimes miss the more obvious solutions to problems that take much less work to implement.

The solution here is to put class swapping on a timer if you just recently killed an enemy because the problem isn't XP rules but class swapping not having any timers on it to prevent abuse of the XP rules.

Over in WoW if you switch your talents it locks your spells for several minutes to specifically prevent similar kinds of abuse. There's no reason FFXIV cannot do the same since players are not intended to swap classes during combat.