They simply need to make it so that in progress instances are prioritized over fresh ones. I can't fathom why this isn't the case yet :/
They simply need to make it so that in progress instances are prioritized over fresh ones. I can't fathom why this isn't the case yet :/
In short, 1.0 class stacking should come again
Kill trash mobs with all dps as BLM, switch to MNK at the endboss. Keep out of party if you don't have BLM or MNK.
Last edited by Felis; 05-02-2014 at 01:58 AM.
Cannot "like" this enough! I've had a few runs where we lost a member, and I dropped to requeue as the missing job, but only fresh runs were coming up
Sure, this has the potential to give instant satisfaction to all those pesky tanks/healers who constantly withdraw looking for an in-progress run, but on the flip side, the rest of us wouldn't have to deal with the constant withdrawals. Win-win?
Last edited by Skivvy; 05-02-2014 at 02:00 AM.
Personally I think this is an entirely acceptable way of playing the game. In fact, it will fully utilize the Armory system.
- The "Need" function can be locked to the job you first enter with.
Being able to change battle classes should not be an option. We ought to be able to change to a crafting class for emergency repairs, however. That wouldn't affect the dungeon progress, and would be quite handy.
When the world was young, the Sun bestowed upon me his crown; always will I light your darkest hour.
I've dealt with this mechanic in DCUO.
Someone queues as a tank or healer to get a quick instance pop and then switches to dps.
More often than not one of the dps then agree to switch to heals rather than wait even longer for another healer.
The abuser gets a fast queue time and makes someone who has waited patiently to play as DPS switch to something they didn't want to play.
If someone was to do this three or four times before not getting kicked they would still get a group much quicker as a dps.
Everyone should realize in 2014 that if a MMO mechanic can be abused/exploited it will.
You can't balance content with that playstyle.
Either you assume everyone had multiple jobs leveled and then make it impossible for groups filled with single job players or you make it ridiculously easy for groups that do job switches.
These are completely different though. It's like comparing apples to oranges. Job change would have to be triggered by the person requesting to change, not by someone trying to force another to change. I think Skivvy pretty much nailed it to prevent abuse.
I would adjust the last to encompass all of the same logic used to determine when vote kicking is locked, but this would prevent the vast majority of potential abuses.
While dissimilar in implementation, the abuse still operates the same in that: you have a group of say 5 FC members who want an individual member to get loot. Whether it's a vote to allow that member to change to said job or to kick someone they don't want getting the loot, they still hold the majority.
That's not to say that there isn't a solution or workaround, but as we know, solutions usually come after the abuse has run for a few weeks
Server: Sargatanas || Main Job: Scholar || Chocobo: Bonchon
|
![]() |
![]() |
![]() |
|
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.