Fundamental Game Play Issues

[Arcon]

They need to finally decide on which way round the following options will occur on a confirmation window:
1)
Accept.
Decline
2)
Decline.
Accept.

Bloody annoying using Runic Portal and hitting Cancel every time because on almost every other confirmation window, Accept is the top option.

Streamlining and unifying menu options is one of my top gripes with FFXI. It's like every single menu dialogue was designed by a completely different development team, different designers, different scripters and a guy tossing a coin who makes the decisions.

[Eric]

Streamlining and unifying menu options is one of my top gripes with FFXI. It's like every single menu dialogue was designed by a completely different development team, different designers, different scripters and a guy tossing a coin who makes the decisions.

Not only that, but it seems like every single menu has at least two confirmations for the same thing, to the point where it's ridiculous. Even ones that are used very frequently.

"Select an option"
"Is this the option you have selected?"
"Accept/Decline"
"Are you sure you want to do the requested action?"
"No/Yes"
"Are you really sure you want to proceed? Blah blah blah will happen if you choose this option. "
"Yes/No/Cancel"

I wish there were an option to do the same thing that you can do with synergy--the option to turn off confirmation requests for EVERY SINGLE action. Of course there are important things that should have confirmation requests, but for the majority of the mundane menu surfing we have to do, there is no reason to make it such a tedious process.

[Byrth]

Not only that, but it seems like every single prompt has at least two confirmations for the same thing, to the point where it's ridiculous.

"Select an option"
"Is this the option you have selected?"
"Accept/Decline"
"Are you sure you want to do the requested action?"
"No/Yes"
"Are you really sure you want to proceed? Blah blah blah will happen if you choose this option. "
"Yes/No/Cancel"

I'm really glad they abandoned this for the Porter Moogle.

[Ladycandygem]

Not only that, but it seems like every single menu has at least two confirmations for the same thing, to the point where it's ridiculous. Even ones that are used very frequently.

"Select an option"
"Is this the option you have selected?"
"Accept/Decline"
"Are you sure you want to do the requested action?"
"No/Yes"
"Are you really sure you want to proceed? Blah blah blah will happen if you choose this option. "
"Yes/No/Cancel"

I hate the ones where you have confirmed everything, you cannot cancel out, but then still have to press the button again. So many times at outpost NPCs I've confirmed I want to warp, look away from the screen for a few moment while I zone, and look back to see I have to press the button again because the guy wished me a good trip.

[Alhanelem]

Streamlining and unifying menu options is one of my top gripes with FFXI. It's like every single menu dialogue was designed by a completely different development team, different designers, different scripters and a guy tossing a coin who makes the decisions.

The reason this varies is because for some decisions, especially any that have a cost involved, they don't want you to accidentally do something you didn't want to do, so they make 'no' the default. Other times, when the cost of an error is low/none, they make yes the default. It's not because they like being inconsistent, they're just deciding the risk value of making the wrong decision on a decision-by-decision basis.

Somewhat of a devil's advocate post- If the choices were the same everywhere, mistakes in the first place would be less likely, at least one would expect.

[Kaisha]

It's because every NPC dialog prompt is hard-coded as to why there's no uniformity unfortunately. At least they learned from that one particular mistake when developing XIV.


But I digress, it wouldn't kill them to go through a lot of the heavily used NPCs and streamline the system.

[Motenten]

When you lose connection, it's treated as an error. When the game aborts due to an error, changes to macros and map markers are not saved. This has caused me annoyance dozens of times over the years. Please fix it.

Workaround: Changing macro sets forces a save of the one you were on; the game saves the initial palette's macros to a file in your user directory, then loads the new one. Change the active set after you make adjustments to your macros (just arrow up and then back down) and you don't have to worry about losing them in a crash.

[Hashmalum]

Workaround: Changing macro sets forces a save of the one you were on; the game saves the initial palette's macros to a file in your user directory, then loads the new one. Change the active set after you make adjustments to your macros (just arrow up and then back down) and you don't have to worry about losing them in a crash.

Interesting, thanks. I don't suppose you happen to know a way to force-save map marker changes?

[Motenten]

Interesting, thanks. I don't suppose you happen to know a way to force-save map marker changes?

Unfortunately, no, I don't know how to manage that. I add map markers so rarely, it's never become an issue for me to look into.

[Meyi]

Interesting, thanks. I don't suppose you happen to know a way to force-save map marker changes?

I believe you can save map markers to the server, can't you? I know you can save macros for sure but I think I read map markers save as well. Could be wrong.