If you summon your companion (i.e. the chocobo), you can't use Mount Roullete or summon any other mount. You're stuck with the same mount you have since you started playing the game: the chocobo.
Why add more drama/dilemma when there should be none?
Why add the code to prevent players from summoning other mounts for no reason? (more work for you, less fun for us, yes?)
Why make it hard to enjoy the perks of paying more for the game? (most mounts come from CE edition and Veteran rewards)
On top of that you have the code that temporarily removes the chocobo when entering major cities, why can't it be applied for Duty Finder and Story Quest Instances? Or at the very very least not kicking us out of the DF queue when we summon the companion. It's very dumb to get kicked w/o prior warning when you have queued for 30 minutes and want to have the chocobo to help out with the hunting log or quests.
-
04-14-2014, 01:19 AMChestyBearWhy add Mount Roullete and new mounts when you can't really use them?
-
04-16-2014, 04:38 PMTomTom1968
This Game has so many barriers and "not possible" actions I just don't understand why they are even in the Game. I agree to what you said and would like to add something to the list.
- I check the market board or an NPC, receive an invitation, window comes up but I can't accept. Why on Earth can't I accept? Let me accept and continue what I was doing.
- I have my Choccobo out and get an invitation to a group which is not even full (less than 8 people). I can't join because of my choccobo. Why that? Why not just a message that your Choccobo will be sent away when you accept? Or make me just join unless there are already seven people in the group so me and my choccobo would be too much.
I know SE has put a lot of Love and passion into this Game. 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. -
04-18-2014, 04:05 AMRaphaelDDLI'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.Quote:
Originally Posted by TomTom1968
-
04-18-2014, 10:59 PMThemis
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.
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.Quote:
Originally Posted by RaphaelDDL
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.