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

[PyurBlue]

It will impact nothing because all those situations are rare and solved by other players. You're not supposed to be able to change classes while in combat and this exploit bypasses that

Being locked out of changing classes for a completely unreasonable amount of time is far more concerning to me than this exploit could ever be. It would just end up creating a pointless hurdle if you're leveling a side class while waiting for queues or if you're in a party in the open world and one of the party members happens to die for whatever reason. BLU revitalized open world farming, and with that comes competition for the limited spawns we have. It's pretty much an issue with how the class was implemented.

[Crushnight]

a 10 sec delay to switch jobs after using an ability would fix it without forcing people to miss queues since 45s timer (it would be on the player if missed at that point) but programming that in would be a nightmare on top of all the programming needed for 4.55 to 5.0 so i am fine with it being eventually ironed out if possible as it is nowhere near a serious enough issue to warrant immediate dev time

[Awha]

People wanted a more active over world, this is what happens when you have an active over world. Face it you are simply upset because you worked harder and not smarter. Live with it life goes on.

[therpgfanatic]

a 10 sec delay to switch jobs after using an ability would fix it without forcing people to miss queues since 45s timer (it would be on the player if missed at that point) but programming that in would be a nightmare on top of all the programming needed for 4.55 to 5.0 so i am fine with it being eventually ironed out if possible as it is nowhere near a serious enough issue to warrant immediate dev time

Adding a delay before another action can be done is not a "nightmare to code". It's a couple of if statements and a timer. It's a handful lines of code.

I have leveled multiple jobs and never have I ever had a need to switch between jobs rapidly while killing enemies on the overworld map.

That's not how this game is played and you guys know it, you just want to keep abusing an exploit.

[Arya_Leviathan]

a 10 sec delay to switch jobs after using an ability would fix it without forcing people to miss queues since 45s timer (it would be on the player if missed at that point) but programming that in would be a nightmare on top of all the programming needed for 4.55 to 5.0 so i am fine with it being eventually ironed out if possible as it is nowhere near a serious enough issue to warrant immediate dev time

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.

[therpgfanatic]

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.

[Dualgunner]

So submit your application to SE since you apparently know how to accomplish in 5 minutes what their whole team said they're waiting till 5.0 to tackle.

[Arya_Leviathan]

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. 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.

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.

You run a software developer, yet you don't understand that this is an MMO and it has multiple million lines of code and saying that adding "5 minutes of coding" is a simple task and that it won't break the amount of layers of codes all the way back from 1.0 is absolutely astounding.

[Baalfrog]

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.

Thats just the thing though, you shoot Jolt II, and swap classes before you ever enter combat. Because you enter combat when spell hits.

[therpgfanatic]

You run a software developer, yet you don't understand that this is an MMO and it has multiple million lines of code and saying that adding "5 minutes of coding" is a simple task and that it won't break the amount of layers of codes all the way back from 1.0 is absolutely astounding.

It won't break anything because the lines of code related to class swapping is about checking to see what classes you have unlocked and what the gear set is set as when you swap, and if you still have those items in inventory, etc etc.

There isn't tons of code related to class swapping. It's a mechanic not tied to anything else in the game because it's not intended to be used during combat. Putting a timer on the XP earning after a class swap is not a huge deal.