Dev clarifaction on exp switch

[Metalwrath]

For those who were trying to start a witch hunt on players useing the technique.SE themselves have stated they arent counting it as an exploit.


We are making the investigation and addressing of this issue a high priority, but as explained above, it involves changing the core structure of the EXP gaining method, making it difficult to address with a mere hotfix. Currently, we are aiming to address this issue with Patch 5.0.
As a result, using this method for levelling would normally be classified as an exploit, but since we were not able to address this promptly despite it being a known issue, we will not be issuing any penalties for players who are levelling in this way. However, since this was not the intended design, we do not recommend engaging in this behaviour, and exhort players to level in the normal manner as was intended.

Full post here
https://eu.finalfantasyxiv.com/lodes...8f3d8978271a55

[Tint]

lol, they allow exploiting now because they don't have a fix for it?

what's next? allowing RMT and botting too because they don't have a solution for these problems for years now? is cheating in PvP now also allowed?

that's stupid

yesyes, over exaggerating. but it sets a precedence.

[Kurando]

The thing is how do you stop players from using the "exploit" if there isn't enough time to even fix it to begin with? Sure you could report them, but really as long as it stays in the game there isn't really much you can do to stop players from taking advantage of it.

By the time the fix gets done, which is 5.0 from what they said, the number of players actually leveling BLU won't be as high as it is now anyway, so it would be a matter of too little too late isn't it.

[Reynhart]

lol, they allow exploiting now because they don't have a fix for it?

Not really...it's the difference between a "bug" and an "oversight". People are not using a bug, but simply something that wasn't anticipated in the intended workflow of Xp calculation.

The thing is how do you stop players from using the "exploit" if there isn't enough time to even fix it to begin with? Sure you could report them, but really as long as it stays in the game there isn't really much you can do to stop players from taking advantage of it.

Technically, they're simply leveling their job, it's not like they gain a huge advantage over those who don't use it. However, is SE think BLU was overall leveled too fast, they might reevaluate the Xp bonus for the next cap increase.

[Tint]

The thing is how do you stop players from using the "exploit" if there isn't enough time to even fix it to begin with?

Sure they can't stop people from using it. But they don't have to outright allow it...

The Ungarmax exploit also wasn't fixed immediately, and while they didn't banned people who used it out of curiousity, it was actually not allowed to use that exploit until they fixed it.

Not really...it's the difference between a "bug" and an "oversight". People are not using a bug, but simply something that wasn't anticipated in the intended workflow of Xp calculation.

In that statement SE themself says it is an exploit o.ô;

Well... they say it "normally" would be classified as an exploit...

[Vidu]

lol, they allow exploiting now because they don't have a fix for it?

what's next? allowing RMT and botting too because they don't have a solution for these problems for years now? is cheating in PvP now also allowed?

that's stupid

yesyes, over exaggerating. but it sets a precedence.

RMT and botting is hurting (or at the very least: annoying) legit players though - quite frankly I dont get why people are so upset about this "exploit". I leveled my bluemage normally which took about 2 evenings (being mixed up with some spell-hunting).
I couldnt care less if someone else got their levels within 20 minutes since it has absolutly no effect on my experience with the job and the game (very much unlike RMT and botting).

So I'm totally not surprised that this exploit isnt their top priority - it has little to no (negative) impact on anyone besides the person making use of said exploit. No one gains an advantge in some sort of competition (unlike Ungarmax and the whole "World first"-stuff) or preys on limited ressources/destroys markets through botting.

[Metalwrath]

Sure they can't stop people from using it. But they don't have to outright allow it...

The Ungarmax exploit also wasn't fixed immediately, and while they didn't banned people who used it out of curiousity, it was actually not allowed to use that exploit until they fixed it.



In that statement SE themself says it is an exploit o.ô;

Well... they say it "normally" would be classified as an exploit...

Ungarmax was almost immediatly fixed.It went used for months because when the issue was reported said people didnt report it onto the devs which as far as i know led to investigations by SE after.

[Reynhart]

Well... they say it "normally" would be classified as an exploit...

Didn't say it wasn't. Only that it's exploiting something that wasn't anticipated, more than something that doesn't work.
When you work on QA, these two are definitely not the same thing

[Vnolan]

Props to the Devs for how they handled this, but why do players making the leveling process easier get more attention than those that actually affect the game's balance?

what's next? allowing RMT and botting too because they don't have a solution for these problems for years now?

Those are already allowed unofficially, as is hunt radar. It's easy to spot those small FCs that use lvl 70 bots to gather or craft and you can open the PF to see RMT. It's not that they don't have a solution, but not enough players are doing it to warrant a response, or in the case of radar, they just don't care.

[Daralii]

lol, they allow exploiting now because they don't have a fix for it?

what's next? allowing RMT and botting too because they don't have a solution for these problems for years now? is cheating in PvP now also allowed?

that's stupid

yesyes, over exaggerating. but it sets a precedence.

Except it's a precedent they set back in 1.0.