Soul stones really need to be required for 31+ instanced content.

[KageTokage]

I've run into players without their job's respective soul stone in level 31+ content several times now, and I don't think there's been a single occasion where it was a honest mistake and it was always someone wanting to "challenge" either themselves or the group because every time it got pointed out they only responded with dismissive remarks if anything.

Granted, there's the option to kick them if they're proving to be a huge liability, but there shouldn't even be a window open for this to happen in the first place because it's forcing the rest of the group into a lose-lose situation where they have to either carry players who are significantly weaker then they should be due to lacking key skills or face a potentially long wait for replacements if they end up having to remove tanks and/or healers.

[Bearded]

Yes it should be a requirement but maybe not for immediate 31+ content just to allow the genuine new players to deal with levelling, gear and such. Probably after Brayflox's Longstop which is level 32. It's unfair like you say to enter the queue with such a significant disadvantage and expect the rest of the party to basically carry you though it because you will not have access to your job skills, weapons etc.

That said though the Devs probably would not make any changes as you can kick then, after the timer expires but then you have to go through the process of waiting on the timer and then a replacement.

[Stepjam]

Agreed. Maybe have the option to take it off in party finder just in case you have the odd group that wants to run an alliance raid with no crystals or something like that. But for Duty finder, there definitely should be a requirement.

[Iscah]

I suspect it's spaghetti code - the game doesn't seem to be able to recognise them as continuous or something.

I'm particularly thinking of the unicorn mount quest where you have to be a conjurer to progess - it won't respond if you're a WHM, even though they're essentially the same.

I would guess they can make a job auto-equip a soulstone all of the time or none of the time, but can't make it calculate based on level.

[Hycinthus]

I suspect it's spaghetti code - the game doesn't seem to be able to recognise them as continuous or something.

I'm particularly thinking of the unicorn mount quest where you have to be a conjurer to progess - it won't respond if you're a WHM, even though they're essentially the same.

I would guess they can make a job auto-equip a soulstone all of the time or none of the time, but can't make it calculate based on level.

What is spaghetti code?

[Stepjam]

What is spaghetti code?

The game was originally built in a completely different way with a completely different combat system (among other things). And then 1.0 bombed REALLY hard, it was a mess all around. But instead of just shuttering the game, they rebuilt it from the ground up and rereleased it as a Realm Reborn. To do so, they didn't have time to build a new engine from scratch, so they had to rebuild the game off 1.0's code. The problem is that a lot of what they did to make the game more internet friendly (and fun to play) required working against the existing code, so they had to make a lot of short cuts and such to get the game to work.

So basically the game's code is a big mess, like spaghetti. Hence "Spaghetti code". They often run into a lot of technical issues that they gotta work around, which is why the game lacks certain things that are standard in other MMOs (like a better glamour system). Hell, apparently even having height differences can cause issues, in E4S they nearly weren't able to have the mechanic where the platform lowers in certain spots, it was apparently pretty buggy and they had to figure out a way to make it work.

[Ayuhra]

Could be Road to 70.

That thing causes you to speed level so people might be meeting the level reqs for these dungeons but are still locked behind the MSQ for their job stone. You are likely to hit 30 a while before you reach Sylph Management.

[Enkidoh]

The 'spaghetti code' thing is just a stupid meme now - ARR does not use 1.0's code, it uses an entirelly new engine based on components of the Luminous Engine from FFXV (this is accepted fact). There are items, gear and character/enemy models reused from 1.0 but these are rendered in the new engine and are not using "old code".

Limitations with content are simply a result of a hurried development schedule due to needing to get ARR's base systems running and stable in order to meet the mid 2013 launch deadline, and they didn't want to screw up a second time around, so in order to make the base game functional that meant having to make as a closed system that was difficult to change or add new components to (such as glamour), and sacrificing allowances for futureproofing. It's not "spaghetti code" but just code that functions in such a way as to be limiting in how new additions are made (a lot of the problem is much of the processing for things like moving items around in your inventory is done server side instead of client side, so that all impacts on how content is designed for the game.

[dangadget]

Could be Road to 70.

That thing causes you to speed level so people might be meeting the level reqs for these dungeons but are still locked behind the MSQ for their job stone. You are likely to hit 30 a while before you reach Sylph Management.

Yes, but aren't lv30+ dungeons similarly locked behind MSQ progression?
if you can queue into Stone Vigil, you should have already unlocked your job stone quests.

[Iscah]

The 'spaghetti code' thing is just a stupid meme now - ARR does not use 1.0's code...

My understanding is that it doesn't use the code but had to be compatible with it? Certainly for 1.0 players transferring their characters in. And they generally build on top of old systems so it's... maybe not spaghetti but like a weirdly built house with extensions upon extensions but not remodelling the original building.

In the case of jobs, I assume it's still got one foot stuck in wherever that classes were the main thing and/or classes and jobs were both viable options.

Anyway, the age of the coding doesn't change my example about the 2.0 unicorn quest that can't proceed until you remove your WHM job stone so it recognises that you're a conjurer.