You have to wonder about the mentality of people thinking a week to get something, isn't newbie friendly.
You have to wonder how we used to have no problem with advanced jobs in FFXI or DK in WoW.
You have to wonder about the mentality of people thinking a week to get something, isn't newbie friendly.
You have to wonder how we used to have no problem with advanced jobs in FFXI or DK in WoW.
Devs. had players that actually devoted some time to play their games back then; now people just complain they haven't got time for a monthly service they pay for.
(lol)
Honestly - I was for locking Ninja behind 2.2 to give new people time to play Rogue 1-50 as a class and learn it's lore/mechanics before they had a change to the expanded arsenal a Job crystal brings with it. Which honestly would've made it the first actual "advanced Job" of FFXIV.
Instead;
Week 1/2 = Everyone decides to pick up Rogue/Ninja
- Huge DPS influx
- Dungeon Queues slow to a crawl
- People complain about the Duty Finder & start face rolling F.A.T.E
- Narutards everywhere with chat log emotes
Week 2/3
- Nobody really learns the Job
- Complain it's too OP/Weak/etc.
- People don't know how to build their _____ for Ninja (Stats/Gear/Rotation)
Week 4/5
- People finally start figuring out Ninja (Stats/Gear/Rotations)
- Either OP/Weak or X ability will be broken in some fashion
- Ninja will have at least 1/2 useless cross-class abilities
- Complaining complaints of complainers complaining
Week 5
- Foam mouth gurgle gurgle
Last edited by Dhex; 10-10-2014 at 04:39 PM.
The thing is that a huge amount of players wanting to play Ninja are already past 2.2 so even if you would have locked it behind it, your queue would still be really terrible and all those little Week 1/5 description you made would have happened anyway. Forcing a player to have at least one max level of another character to have access to another is terrible design.
That's just a matter of opinion.The thing is that a huge amount of players wanting to play Ninja are already past 2.2 so even if you would have locked it behind it, your queue would still be really terrible and all those little Week 1/5 description you made would have happened anyway. Forcing a player to have at least one max level of another character to have access to another is terrible design.
Mine is obviously not the same as yours.
Last edited by Omegakiyohime; 10-10-2014 at 08:52 PM.
Your sum up seems valid, except you forgot one thing, low level dungeons will become solo-able with 2.4 so there won't be queues issues (but people will still have no clue how to play the job that's for sure xD)Week 1/2 = Everyone decides to pick up Rogue/Ninja
- Huge DPS influx
- Dungeon Queues slow to a crawl
- People complain about the Duty Finder & start face rolling F.A.T.E
- Narutards everywhere with chat log emotes
Week 2/3
- Nobody really learns the Job
- Complain it's too OP/Weak/etc.
- People don't know how to build their _____ for Ninja (Stats/Gear/Rotation)
Week 4/5
- People finally start figuring out Ninja (Stats/Gear/Rotations)
- Either OP/Weak or X ability will be broken in some fashion
- Ninja will have at least 1/2 useless cross-class abilities
- Complaining complaints of complainers complaining
Week 5
- Foam mouth gurgle gurgle
|
![]() |
![]() |
![]() |
|
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.