New Windows Version User Interface

[Daniel_Hatcher]

I find this most disturbing, I play with a game controller/keyboard combo because that is what this game was originally designed for, making it so your new UI is keyboard mouse only will disappoint quite a lot of players that were excited by the UI changes, I was looking forward to the UI changes, now I'm disturbed

An onscreen macro palette that never goes wouldn't work with a controller, not unless they removed the traditional macro system.

Then it's kind of pointless.

[Ziyyigo-Tipyigo]

I can has mock-up?

[Finuve]

An onscreen macro palette that never goes wouldn't work with a controller, not unless they removed the traditional macro system.

Then it's kind of pointless.

I agree with wildsprite, last thing I want to do with FFXI is add mouse control, however I do want a UI revamp

just because 3 rows of macros isnt feasible, doesnt mean they couldnt build a 2 macro stack for keyboard/controller and still have the rest of the UI work with keyboard/controller

especially considering if the UI is set to hide the macro palette they already said it will be two rows like it is now

[wildsprite]

An onscreen macro palette that never goes wouldn't work with a controller, not unless they removed the traditional macro system.

Then it's kind of pointless.

I don't see how it wouldn't work with the new system if they wanted it to, if I press my left trigger it brings up 1 palette and I select what I want from it with the arrows,same with the right trigger, I really don't see why they can't make the new system work similar

[Finuve]

so an adendum to my point, with UI scripting available, will I have enough power that I can make the UI work with controller only, or keyboard only?

[saevel]

We have received this request many times before, but there are many issues with this, so we cannot look into this at this time. Similarly, we have no plans to transmit additional data besides what is currently being transmitted between the server and client. Our goal is to improve the operability of what is currently displayed in the current UI. We appreciate your understanding.

And their just shot themselves in the foot.

[Puck]

I wish it would become possible to copy and paste!!!!!

This would be very difficult to implement, so we would like to prioritize implementing the UI first. Based on our workload after that, we may look into this.

But uh... it's already possible through other methods, and not that difficult to do. I don't get why it would be "very difficult."

[Zirael]

I wish it would become possible to copy and paste!!!!!
This would be very difficult to implement, so we would like to prioritize implementing the UI first. Based on our workload after that, we may look into this.

I'm intrigued, does producer Tanaka still use DOS? Copy/Paste is one of the staple PC functions since 1995 (that's almost 20 years ago...), if not earlier. And since we're discussing Windows GUI, this should be here long time ago. Oh, and please don't forget IME for non-JP people!
Also, I recall seeing some funny word-art from /shouts in the past with an obviously copy/pasted text, so it must be possible somehow.
Is it really very difficult to implement copy/paste? Sorry for asking this again, but I'm baffled...

[Muras]

Please increase the number of lines for macros. There are 16 locations that gear can be equipped, so more lines are necessary. I would be happy with about 20 lines.

We have received this request many times before, but there are many issues with this, so we cannot look into this at this time. Similarly, we have no plans to transmit additional data besides what is currently being transmitted between the server and client. Our goal is to improve the operability of what is currently displayed in the current UI. We appreciate your understanding.

If I may make a small suggestion... Wouldn't it be feasible to make individual commands for equipment swaps rather than using a single command that takes up an entire line? For example, if we had these commands:

<main " ">
<sub " ">
<ranged " ">
<ammo " ">
<head " ">
<neck " ">
<L.ear " ">
<R.ear " ">
<body " ">
<hands " ">
<L.ring " ">
<R.ring " ">
<back " ">
<waist " ">
<legs " ">
<feet " ">

Then we can have macro lines like so:

Line 1: /echo TP set
Line 2: <body "Bale Cuirass +2"> <head "Bale Burgeonet +2"> <hands "Bale Gauntlets +2"> <legs "Calmecac Trousers">
Line 3: <feet "Ace's Leggings"> <waist "Goading Belt"> <L.ear "Bale Earring"> <R.ear "Brutal Earring">
Line 4: <neck "Bale Chocker"> <R.ring "Rajas Ring"> <L.ring "Tyrants Ring"> <back "Atheling Mantle">

This should fix the need for more lines and not increase the amount of data being transferred to the servers. You managed to make the /wait command into <wait #> instead, so why not this? I'm not an expert programmer by any means, but I know this isn't impossible.

EDIT: Oh also, think you could add a chat filter to turn off the "Equipment changed." notice? I can't count the amount of times I missed something important a PT member said because I hit a couple equipment macros.

[Zumi]

Oh, and please don't forget IME for non-JP people!

SE can't do this unless they pay MS for licensing fees for the NA and EU versions. The chances of that happening are slim to none given very few people with the NA version would use it.