New "Macro Strings", Macro's Reborn!

[Arcon]

Macros could definitely use a rehaul, and while this idea doesn't sound bad (maybe a bit complicated), I much prefer this one:
http://forum.square-enix.com/ffxi/th...Simpler-Macros

It would be easier both to implement and to use and has less chance to be abused for botting purposes, and addresses the only real issue with the current macro system, namely gear change lines.

[Selzak]

Macros could definitely use a rehaul, and while this idea doesn't sound bad (maybe a bit complicated), I much prefer this one:
http://forum.square-enix.com/ffxi/th...Simpler-Macros

It would be easier both to implement and to use and has less chance to be abused for botting purposes, and addresses the only real issue with the current macro system, namely gear change lines.

That is almost exactly the idea I had earlier in this thread. I really think something like that would meet everyone's needs, while avoiding any increase in automation as well.

[Coldbrand]

Revamping the UI would go a LONG way towards keeping this game fresh and survivable for the future.

[kingfury]

**EDITED ORIGINAL POST**

Cool alternatives/Similar concepts:
-Selzak's idea(Post 1),(Post 2)
-Tamarsamar's idea
---------
Yep, I wouldn't mind how it gets done, whether my idea or another's, so long as we can reduce the cumbersome task that is gear swapping ^^ As it stands, I'm satisfied knowing that the Dev Team realizes the need to revise the UI of the current macro system. Thanks to the feedback from Camate /salute. Every idea beyond this point is just constructive feedback towards communicating to the Devs what we would like to see before they eventually update the system.

Thanks to everyone that posted feedback so far, and I hope we keep it going until we hear word from the Devs on exactly what we can hope to see in the future. /salute

[kingfury]

Would it be terribly hard to let the "/macro book" and "/macro set" commands receive a similar face lift as the /wait command got with the "<wait ##>"? It would be super great to have that last macro line be used for actually commanding something or including that last piece of gear vs only housing /macro set ## or /macro book ##. Example:

/equip Ammo "Ravager's Orb" <macro set #>
-----
Oh and also(if the latter is not possible, at least this lol):

/macro book ## <macro set ##> (since if you want to jump to another book and set you need to take up two macro lines to do so)
--------
That's gotta be doable Camate!! ^^/
/Kingfury readies drumroll... o.o;

[Krystal]

i gotta say king..you have some VERY GOOD IDEAS for FFXI...honestly...maybe you should apply for the dev team! they could use someone like you!

[kingfury]

i gotta say king..you have some VERY GOOD IDEAS for FFXI...honestly...maybe you should apply for the dev team! they could use someone like you!

---------
/kneel Thank you very much friend for the feedback ^^/ It would be a dream come true, honestly to officially work with/for the Dev Team, of which I would try to pinch myself everyday to make sure was real lol.

After checking out the Careers Page, though, I think I would need a major reference from the inside to even get my foot in the door since they are only hiring what seems to be "Big Wig" positions right now lol ><;

I'm going to submit my resume anyway of course and just /crossfingers in the hopes they need an artist to illustrate little stuff like the occasional event written pieces (like the current Egg Bonanza illustration that's up now) because I would totally rock those out all day lol. Those writers deserve a small web comic page based on all that good writing ^^. Hmmm... maybe that could be apart of my resume submission! o.o But, I'll take anything for that matter ^^

[kingfury]

**EDITED TO ORIGINAL POST**
--------
Would it be terribly hard to let the "/macro book" and "/macro set" commands receive a similar face lift as the /wait command got with the "<wait ##>"? It would be super great to have that last macro line be used for actually commanding something or including that last piece of gear vs only housing /macro set ## or /macro book ##. Example:

/equip Ammo "Ravager's Orb" <macro set #>
-----
Oh and also(if the latter is not possible, at least this lol):

/macro book ## <macro set ##> (since if you want to jump to another book and set you need to take up two macro lines to do so)
------------

I actually should've put this in from the start ><; Camate, if you're at all able to revisit this, this would be super helpful if the Devs could give some feedback on this particular possibility. If they are in fact already working on such an improvement, then all is well ^^ /

[Zumi]

Are you forgetting PS2 limitations won't allow that much in the RAM to be used at once, it only has 32mb. It would definitely have to be in the RAM to work so it won't work unless there was no PS2.

[Arcon]

Are you forgetting PS2 limitations won't allow that much in the RAM to be used at once, it only has 32mb. It would definitely have to be in the RAM to work so it won't work unless there was no PS2.

I'm surprised this wasn't mentioned before, but same as additional macro lines, this would require more space, and if I understand the post correctly, quite a lot. If you store macro strings serverside though, there would be lots of new issues. For one, I don't think the coding would be that simple, it would require a lot of safeguards. Not being able to enter the same string title twice isn't enough to prevent looping, since /macrostring would be a normal command, it could be called within a macro string as well. Disabling that may not be as easy as it sounds, since currently there's no way for SE to know where a command comes from, if it comes from a normal macro, entered manually, or from within a macro string. They would have to change the ways commands are sent/interpreted completely to make it work, for example send an additional overhead to the server every time a command is sent. This would take lots of extra traffic and computation cost though.

If it was stored serverside, it would again have to have some additional safeguards to prevent looping, since one macro could call a macro string several times, or make a macro string execute a macro that contains another macro string, etc. It would have to implement some kind of stack to trace where macro calls are coming from, to prevent looping.

It is a new idea, additional macro lines would, so to speak, just delay the problem. This offers a new solution of being able to combine macros in a new way. However, there's plenty of pitfalls to consider, and maybe from space requirements alone it wouldn't be feasible. Also, I don't know if it's very user friendly, plenty of people don't even understand current macros fully. And I have to say, even I am a bit confused by this idea, especially the grouping thing. I hope SE considers Tamarsama's idea, it seems simpler both to understand/use (in fact, it would make gear macros a lot easier to understand than they are now) as well as being easier to implement. And with some sophisticated coding it could even conserve lots of space, cause it would alleviate the need for so many macro lines, unlike this idea that would add new lines with the respective macro strings.