Interesting that they do this on hamlet. I see that they have to since you will be scored and the jobs/classes represented adds points. I cant help but wonder if this is something they plan to carry over to other new/old content at some point.


Interesting that they do this on hamlet. I see that they have to since you will be scored and the jobs/classes represented adds points. I cant help but wonder if this is something they plan to carry over to other new/old content at some point.
they should have done that with the last fights.



I think Hamlet defense is a special case, because you get scored on how well you did. This should not be extended to raids/dungeons, etc.

i think it should be extented, for various reasons but mostly cause ppl demand multiple classes for raids and thats just plain stupid
I just want to play my dragoon in peace guys. I like this job locking system
Retired FFXI character: Ranok of Sylph
Sweet. Mining potions for an hour should be fun.


Locking class in raid will just encourage more class stackins because it will have more risk. Careful with what you ask for if you want invites fellow DRGs.
I think their thought was that players should construct a party carefully before entering
And/or the current system will only allow for rewards to be given based on what you do as one class, and it's too complicated to make a program that will reward you based on what you do over several classes.
Probably time constraint issues too.
That said, I doubt we'll be seeing too many DoL/H participating in the actual battles because of this.


the way i interpreted it is dol and doh give crap to the npc outside of the instance for a certain amount of time, then the instance is ready to enter for battle classes.not sure if that's right since i don't care much about it and didn't try to understand it too much.I think their thought was that players should construct a party carefully before entering
And/or the current system will only allow for rewards to be given based on what you do as one class, and it's too complicated to make a program that will reward you based on what you do over several classes.
Probably time constraint issues too.
That said, I doubt we'll be seeing too many DoL/H participating in the actual battles because of this.



It will not. You're clearly unable to see that if you stacked all WAR, or all BLM, or all MNK, or all BRD on CC or AV you'd fail miserably. Locking class/jobs during content means you are encouraging a balanced group that can handle ANY situation. It also encourages developers to be more creative in future mechanics and fights.
Locking classes/jobs and extending this mechanic to dungeons/instances/primals/etc is a wonderful mechanic that promotes group diversity. The current mechanic of "changing to what is most efficient" is garbage and simply requires everyone to have every job leveled up.
Some jobs should have challenging fights or scenarios that they should have to learn to deal with. That's what makes the job unique in the first place. As it stands now, by not wanting job/class locking on content, you're just dumbing down the content and placing huge and unnecessary barriers for new players who want to play the game. Unfortunately with classism and the current ridiculous job swapping during instanced content, you are telling those new players that they can't engage in any activities until they have the proper jobs/classes leveled up.
|
|
![]() |
![]() |
![]() |
|
|
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.
Reply With Quote




