Tank Stances and WHY???

[Seraphor]

Because when your level gets synced down, all your buff abilities get deactivated - which happens to include your tank stance.
Probably easier to do it that way than having the game figure out which should be shut off, and which should have their effects reduced, and which would be fine to keep activated.

BLU is able to enter duties and maintain Aetherial Mimicry. So I see mo reason why they can't program the same function for just four other abilities.

[aodhan_ofinnegain]

BLU is able to enter duties and maintain Aetherial Mimicry. So I see mo reason why they can't program the same function for just four other abilities.

This was pretty much answered on the last page.

Because all BLU actions are level 1, they don't have restrictions like all the other jobs. Once you obtain a BLU spell it's available regardless of sync (obviously you need to set it first).

[SingularBanana]

I didn't miss anything you said, but you've clearly misunderstood what I've tried to communicate. What you seemed to be asking for was permanent tank stance, with no way to remove it. Perhaps I missed that, but that's the only way for you to never have the issue of having to remember to turn tank stance on. So what you're telling me to do doesn't apply, and even if it did, I've never quibbled about my responsibility as a tank.

No, I wasn't asking for the inability to deactivate it, I'm saying it doesn't make sense that it deactivates by itself since there isn't a single instance of group-required content in the game that is of a level below where tanks receive their stances. I'm fine with having Grit or Iron Will able to be toggled, but when I sync down, it shouldn't turn off because, so far as I'm aware, the reason abilities are disabled when you downsync is that they require a level higher than what you are sync'd to.

In the case of tank stances and the duty/party finders, there isn't a single instance of group content - nowadays, that is - that is below the level at which you receive your tank stance. Ergo, I believe it's unnecessary for it to automatically disable when you are sync'd down in level since there is no point where it would be unavailable to a group.

The sense I get off of it is that when they made the decision to give all tank roles their tank stances at 10 - because they weren't all available at 10 at first - they simply didn't consider/forgot that it wouldn't need to be deactivated. I've seen it as an oversight and not intentional. I could be wrong, I probably am, but that's just how it comes across to me.

Keeping it as an activated ability is fine for cases where you DO want or need a MT/OT, but for regular light party roulettes, it's unnecessary for it to be disabled.

That's my point.

[LeonKeyh]

No, I wasn't asking for the inability to deactivate it, I'm saying it doesn't make sense that it deactivates by itself since there isn't a single instance of group-required content in the game that is of a level below where tanks receive their stances. I'm fine with having Grit or Iron Will able to be toggled, but when I sync down, it shouldn't turn off because, so far as I'm aware, the reason abilities are disabled when you downsync is that they require a level higher than what you are sync'd to.

In the case of tank stances and the duty/party finders, there isn't a single instance of group content - nowadays, that is - that is below the level at which you receive your tank stance. Ergo, I believe it's unnecessary for it to automatically disable when you are sync'd down in level since there is no point where it would be unavailable to a group.

The sense I get off of it is that when they made the decision to give all tank roles their tank stances at 10 - because they weren't all available at 10 at first - they simply didn't consider/forgot that it wouldn't need to be deactivated. I've seen it as an oversight and not intentional. I could be wrong, I probably am, but that's just how it comes across to me.

Keeping it as an activated ability is fine for cases where you DO want or need a MT/OT, but for regular light party roulettes, it's unnecessary for it to be disabled.

That's my point.

The "sync" mechanism, from a programming standpoint _isn't only used in group content_. It's used for FATES and Solo instances as well, both of which have several that are under lvl 10. So, the sync mechanism, whenever it is activated, goes through and removes all buffs that are not attained at Level 1 (i.e. the lowest level that you would sync to). That's it. They didn't create a new sync mechanism specifically for each place that you could possibly sync, they made one that does everything that it needs to do; removes all of your buffs that aren't level 1 buffs, syncs your item levels, syncs your level.

What you're asking them to do is write a new sync mechanism that is only used in DF content.

[SingularBanana]

The "sync" mechanism, from a programming standpoint _isn't only used in group content_. It's used for FATES and Solo instances as well, both of which have several that are under lvl 10. So, the sync mechanism, whenever it is activated, goes through and removes all buffs that are not attained at Level 1 (i.e. the lowest level that you would sync to). That's it. They didn't create a new sync mechanism specifically for each place that you could possibly sync, they made one that does everything that it needs to do; removes all of your buffs that aren't level 1 buffs, syncs your item levels, syncs your level.

What you're asking them to do is write a new sync mechanism that is only used in DF content.

Another valid point, and one I hadn't considered, but then again - why not? So far as I'm aware, it's the only buff that is "Level 10" across the role. I would need to go through all my classes to see what abilities are available at 10 and what shuts off when entering a group-required (without opting for undersized party) duty to see if there's another class or role that has this happen, but you don't really need tank stances for solo-sync'ing content anyway.

You have given me more food for thought, though, and again another angle from which I hadn't looked at it and for that I appreciate the post. I played through the Heavensward and Stormblood days of "Get enough enmity to hold then go dps stance" and frankly, I don't want it to get back to that. That's why they changed tank stance in the first place, to do away with that "requirement" for tanks.

[LeonKeyh]

Another valid point, and one I hadn't considered, but then again - why not? So far as I'm aware, it's the only buff that is "Level 10" across the role. I would need to go through all my classes to see what abilities are available at 10 and what shuts off when entering a group-required (without opting for undersized party) duty to see if there's another class or role that has this happen, but you don't really need tank stances for solo-sync'ing content anyway.

You have given me more food for thought, though, and again another angle from which I hadn't looked at it and for that I appreciate the post. I played through the Heavensward and Stormblood days of "Get enough enmity to hold then go dps stance" and frankly, I don't want it to get back to that. That's why they changed tank stance in the first place, to do away with that "requirement" for tanks.

"Why not" is generally anytime you change code, you create bugs, especially within intertwined functions. From a risk/reward standpoint, it's not worth creating and maintaining 2 separate sets of code that generally do the same thing just so that 1 person in DF doesn't have to hit 1 button while the party loads in/watches a cutscene. Sure, it's annoying, but I would say that it's not worth the dev time to fix.

[SingularBanana]

"Why not" is generally anytime you change code, you create bugs, especially within intertwined functions. From a risk/reward standpoint, it's not worth creating and maintaining 2 separate sets of code that generally do the same thing just so that 1 person in DF doesn't have to hit 1 button while the party loads in/watches a cutscene. Sure, it's annoying, but I would say that it's not worth the dev time to fix.

SE has patched things on the fly that have done pretty simple tasks, from our viewpoint, but I imagine needed lines of code. Like keeping Wanderers out of the Firmament on worlds not their own so they can't take up space for the FATEs. While admittedly this is a much more widespread issue than my tank debate here, they did it. I would imagine it also took a lot more coding to do that than it would to stop tank stances from being deactivated.