What Everybody Wants: Shorter, Simpler Macros

[Eadieni]

This is not possible if its done client side, because of the PS2.
However if equipment sets were to be stored on the server .... anything is possible

If you could equip a set of armor, and "save" it to a server storage equipment macro, you could also recall it.

It could fix the problem, but you might see a partial loading every time you call one of those macros.
Still, given that you can load all your macros at once in about 3 seconds from the server after saving, I don't see a problem with a 1-2 second delay when calling an equipment set change macro.

This could also lead to a method that pulls data from the Porter Moogles to be able to summon a set of your favorite armor, rather than piece by piece. Like "Withdraw saved set 8" or something.

I think this is going to have to be the future of FFXI, saving things on the server instead of the client. The PS2 doomed everyone, but in 2003 who would have known the game would go into 2011 and still be popular? Most PS2 online games have had their servers shut down, the fact that EQOA is online still is nothing short of a miracle.

[Arcon]

This is not possible if its done client side, because of the PS2.

As I said before, it should definitely be possible, depending on how it's stored. But even using trivial storage methods the PS2 should still provide plenty of memory to deal with this. Server side could work, but it would require some extra storage on their part, compared to having it distributed among all the players.

[Digi]

How about an idea like this: /equip Main "Item" Head "Item" Legs "Item" allow up to maybe 3 or 4 items to equip per line :3 Less lines but not easier but its a thought.

[Sorka]

I hardly ever gear swap on my jobs because of the lines issues in the macro windows. I know it's silly but I don't want to have to hit several macros just to swap out more than 6 things at a time. This needs to get fixed somehow and damn the PS2 limitations! I'm sick of that excuse, SE. ):<

[Tsukino_Kaji]

Any shortening or simplification is not neccissary. All SE needs to do is add one more line. ONE more line.

[GlobalVariable]

Any shortening or simplification is not neccissary. All SE needs to do is add one more line. ONE more line.

Or a page button?

[GlobalVariable]

semicolon parsing please! /equip head "thing"; /equip hands "thing"; /equip r.ring "thing"; /equip l.ring "thing"...


Alternatively, <equip head "thing">

[Seyomeyo]

Best idea ever. only ammendment I would make is the possible renaming of "/equipset ##" to "/equipset <name>". Naming them would be very convenient, especially given the fact we can already name macro books

[Xilk]

Naming an equipset is by far the most powerful and user-friendly approach to this.
it would take as much memory as the current equip set does... that is to say, not much. Its a few saved tables with 16 entries in each.

Then easily inclued 1 macro line for the exact gear you want for a ja, spell, etc.. It would save tons of time for all players.

[Laraul]

Macros are stored in UTF-16 format... All combined it's less than 300Kb for every possible Macro, Map marker, etc... and these aren't fetched from the HDD until needed...

I would just like an /optimize command... for equipping the optimal gear for a specific job or level. I would also like to cycle thru multiple ways of inventory sorting... like name, job, level, slot, type, etc...