Why add Mount Roullete and new mounts when you can't really use them?

[RaphaelDDL]

But sometimes it seems like there are not enough people in their team who do convinience/comfort checks. Looks more like often, the easiest and quickest way for SE is implemented - and it can't be much easier than implementing a pop up message stating "not possible". Of course, adding conditions and decision paths is more complex but come on SE, you can do better than going the easy way of just forbidding things. Make things possible and get rid of the not needed restrictions.

I'm more convinced that they didn't learned enough of MMO environment with FFXI. They should hire people with UI/UX knowledge that also played MMOs for a long time.

[Themis]

On the topic:

Is there no way that the Mount Roulette could only select from "Company Chocobo" whilst a companion is out in the field? That would allow it to be used, whilst only limiting the choice to the only mount you can use whilst a Chocobo is out. At least in the short term, whilst whatever changes necessary are made to the system to allow for other mounts to be used in conjunction with a companion.

I'm more convinced that they didn't learned enough of MMO environment with FFXI. They should hire people with UI/UX knowledge that also played MMOs for a long time.

Y'know, adding in code to an existing system is slightly more complicated than just thinking it up. I also have no idea how much experience Minagawa (the UI/UX director) has with MMOs, but he's in his position because he can be trusted to know what the game needs and what people want.

But again, UI/UX considerations are often impeded by the code behind the systems. Sometimes, it's just not possible to implement a design "just like that". I know some of the struggles because that happens to be part of my job (developing/implementing UI/UX requirements into existing code). And UI/UX is more of an art than a science. Just because 1 idea works in one area, doesn't mean it can be successfully applied in another.