New "Macro Strings", Macro's Reborn!

[kingfury]

**POST REVISED(APR/7/2011)**
---------
The Macro String: (Cover Art)
http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-15.jpg
Description:
"Macro Strings" would forever change the way Macro's are used in FFXI by drastically changing the way gear swapping Macro data is called when players use them via the Macro Palette during play. This drastic change would be accomplished by "stringing" together the current 18-line Macro data used to completely change all of the current player's gear and assign them a "String Title" that would then be usable to reference all the macro lines of data at once. The String Title would occupy only one Macro data line, and yet house all the information of a 18-line Macro. This would vastly change the face, efficiency, and power of Macros like never before should this be implemented.

*EDIT* This system would only allow the input of equipment (armor, weapons, ammo, etc.), so to safeguard against possible automation-like macros that would create endless loops. Below, there are 2 really great similar concepts that would offer even simpler alternatives to implementing such a system for those that are less experienced in the art of Macro creation and management, and I would opt to also allow the option of imputing the information manually via a "Strings menu" or something similar, for those that have become experts over the years. Even though it wouldn't technically be necessary with the alternative concepts ("Fashion Moogle", and "/Equipset Command"), having the ability to quickly edit a single macro line with a newly acquired piece of gear on the fly could be intuitive. Based on the possible functionality, however, equipping the new gear and just hitting a "save/update" button would effectively cancel the need for manual input functionality all together, so it would be based on the most intuitive/time saving option in the long run. If new options were to appear that would help players distinguish similar named gear for instance(Example: Having two different "Atlas +2" Great Axes in your inventory at the same time), with new macro syntax, it would definitely help to type it in manually via a Strings Editing menu.

Unlike the other Macro enhancement request in the past that called for more Macro data lines, which would further tighten the noose that is the PS2 limitations; this proposed system is not necessarily adding "more" Macro data lines, but instead adding a new way of managing and calling macro data. Akin to adding new folders which contain list data that can be titled and commanded to perform the nestled list data actions via the macro palette.

System Mechanics:
For example, a WAR setting up his/her macros to quickly equip gear to be used for Raging Rush would be able to create 3 separate macros to do so. In this example, however, the WAR will be setting up the macros using the Macro String system.
-Possible Navigation/Creation of Macro Strings (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=66964&viewfull=1#post66964)
---
Placing String Macros within a Macro:
With the Macro Strings created and named, now would come the easiest part. Simply entering the Macro String's title into the desired Macro line would effectively call all the Macro String data at once. The line data would appear as this:

/Macro String <"Macro String Title 1">
Or this:
/macrostring <"Macro String Title 1">

In this example, the WAR would be using 3 separate Macro Strings on 3 separate Macro lines to swap in the gear for Raging Rush, then using Raging Rush, and finishing off the macro by swapping into full TP gear.
-Entering Macro Strings-1
http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-1.jpg
-----
**EDIT**Macro String Groups** (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=66958&viewfull=1#post66958)
*EDITED OUT OF ORIGINAL POST, BUT NOTED HERE (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=66958&viewfull=1#post66958)*

Additional Notes:
Per each String category, there would be a String Title limit of 20 (could be as low as 10 if necessary). So an example would be: Under the Warrior String Category, there would be up to 20(or 10) String titles. To avoid any potential bloating of the system due to Titling the Strings.(Thanks to Tsukino_Kaji's feedback (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=64071&viewfull=1#post64071))
----
Saving the String data to the Servers would be an option for storing this information.(Thanks to MarkovChain's feedback (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=64182&viewfull=1#post64182))
----
Macro Book, and Macro Set change:
Also, on a side note, 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 #>
-----
This also:
/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)

Macro Syntax/Internal System to differentiate Same Named gear(Ex: Augmented/Trial Weapons)
Possibly add a simple method of differentiating same named equipment/weapons with macro syntax or internal system corrections. Currently, if a player has two or more of the same named augmented trail weapons within their inventory and wish to select a specific one using macros, the error message "You were unable to change your equipped items" pops up. There is no way to do this using macros, so without manually swapping in the equipment/weapon via the equipment menu, you're stuck.

Going the syntax route, perhaps allowing players(or the system could do this automatically) to add 3-4 letter short descriptions similar to macro pallet titles would help.
Example:
/equip Main "Atlas +2 (PDT)" - For the Phys. dmg. taken GA and:
/equip Main "Altas +2 (EVA)" - For an Evasion GA
----
Going the Internal solution route, creating internal tags that the macro system would recognize when using the "Tab" button to pull up the "auto-translated" name of the weapon/equipment.
-------------
Cool alternatives/Similar concepts:
-Selzak's idea ("Fashion Moogle") (Post 1) (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=63782&viewfull=1#post63782),(Post 2) (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=63795&viewfull=1#post63795)
-Tamarsamar's idea ("/Equipset Command") (http://forum.square-enix.com/ffxi/threads/686-What-Everybody-Wants-Shorter-Simpler-Macros)

Closing:
I'm not a programer, but I've seen the Dev Team produce some amazing feats over my years of playing FFXI, and this (at least in my mind) would be easy prey to tackle :) Of course this is just a suggestion for making things better/more efficient, so if my ambitions are too high with this proposal, then maybe it will serve as a bridge to newer thinking and approaches to the subject of improving Macros for all. Thanks /

[Rambus]

Hmm if I understand right are you saying it would be like this

I want to have all tp gear in alt 1
alt 1:
/equip string 1 (insert string 1 name)
/equip string 2 (insert string 2 name)
/equip string 3 (insert string 3 name)


then alt 2 ,3 , 4 be the places for the string?
*alt 2 first line:
/??? "string reference 1"
/equip head "XXX"

i am a bit confused

[Rezeak]

This is just another way for a macro to call a macro but it would fix alot of problems i have have but i would prefer a way to save my gear sets

For example
I put my tp gear on and save as tpset
then i could use /equip tpset
rather than the 10 lines that i need

[kingfury]

Hmm if I understand right are you saying it would be like this
I want to have all tp gear in alt 1
alt 1:
/equip string 1 (insert string 1 name)
/equip string 2 (insert string 2 name)
/equip string 3 (insert string 3 name)
then alt 2 ,3 , 4 be the places for the string?
*alt 2 first line:
/??? "string reference 1"
/equip head "XXX"
i am a bit confused
--------
Close ^^ you would indeed be able to plug in individual Macro String lines like: /macro string <"TP Gear 1"> and equip up to six pieces of equipment just from that one line.
The next option would be to equip all your TP gear with one String Group line: /macro string <"TP Gear (1-3)"> and use up to 18 macro lines. ^^/

[kingfury]

This is just another way for a macro to call a macro but it would fix alot of problems i have have but i would prefer a way to save my gear sets
For example
I put my tp gear on and save as tpset
then i could use /equip tpset
rather than the 10 lines that i need
----------
Yep ^^ And players would be able to save "String Categories", and "Macro String Groups". The Categories would separate your WAR Strings from your other job strings, while your saved String Groups would save all your different types of gear set Strings.

[Rambus]

--------
Close ^^ you would indeed be able to plug in individual Macro String lines like: /macro string <"TP Gear 1"> and equip up to six pieces of equipment just from that one line.
The next option would be to equip all your TP gear with one String Group line: /macro string <"TP Gear (1-3)"> and use up to 18 macro lines. ^^/

I do not know if the game can do /macro string <TP Gear (1-3)> that 1-3 seems it would have problems being read.

I can see this though:
/macro string <TP Gear 1>
/macro string <TP Gear 2>
/macro string <TP Gear 3>

[kingfury]

I'm sure the brains at SE could figure it out :) it's only programing a few characters to interpret "(1-3)" as "Title 1", "Title 2", and "Title 3". If they can program magic storage in the smallest corners of the game, I'm sure they could handle this ^^/

[Rambus]

I am not even sure if they can let man made titles like that let alone a range but can see what they say i guess

[kingfury]

I kind've see it as simple list data contained in a "folder"(the folder being the Macro String)... so something similar like the process of naming your own folders. Once you title the folder, you could program it to just "Play" whatever is inside the folder once you call that title into action(ex. hit a gear swap macro during play). I know I've read about this functionality somewhere in my past, I just gotta find where lol.

Then, the whole "Title (1-3)" thing would be like nestled folders all with list data contained in them. Since they all have similar naming conventions, the programing would just "Play" them in numerical order until it reached the final folder.

Nothing is impossible!! lol

[Selzak]

It's definitely within the game's reach (the basic code for something like this would take all of a couple of hours), but I think the first problems that would arise would be:

1) Exploitation
2) Complexity (on the user end)

I like the idea a lot, but from an objective standpoint I just can't see it fitting into the game.

Another way to handle this would be some kind of Moogle service where they took "snapshots" of what you're currently wearing. Instead of adding a whole new series of code for us to manipulate, a Moogle could take "snapshots" of what you have on and let you name them (up to a finite amount) to use in macros.

You could go to the Fashion Moogle wearing nothing but subligar, have him take a snapshot of you, name it "Nakey", and then use /equip snapshot "Nakey" to revert to that equipment set. If any single piece of equipment from the snapshot is not available when the macro is used, it would fail. If you had the subligar in your bag, it would make you "Nakey" wearing only subligar. I think something like this might be a lot easier to implement.

[kingfury]

It's definitely within the game's reach (the basic code for something like this would take all of a couple of hours), but I think the first problems that would arise would be:
1) Exploitation
2) Complexity (on the user end)
I like the idea a lot, but from an objective standpoint I just can't see it fitting into the game.
Another way to handle this would be some kind of Moogle service where they took "snapshots" of what you're currently wearing. Instead of adding a whole new series of code for us to manipulate, a Moogle could take "snapshots" of what you have on and let you name them (up to a finite amount) to use in macros.
--------
That actually sounds pretty cool as well lol. Thanks for the feedback ^^/
I'm sure that there would have to be a near equally complex(which isn't very complex on either ideas) list of menu options to provide players the freedom to pick and choose which pieces they did or didn't want to be included in those snapshots. Either way, it would be awesome to have ^^
I imagine that everything being proposed here would be no different from doing everything we've done with macro's for years now, but just adding in the titling part. I would think it would feel pretty familiar since we would still have to create the actual macro list to be used via the String function. Again, the Dev team has some smart cookies on board, so I'm sure they could figure it out lol :) Thanks again /salute

[Selzak]

--------
That actually sounds pretty cool as well lol. Thanks for the feedback ^^/
I'm sure that there would have to be a near equally complex list of menu options to provide players the freedom to pick and choose which pieces they did or didn't want to be included in those snapshots. Either way, it would awesome to have ^^
I imagine that everything being proposed here would be no different from doing everything we've done with macro's for years now, but just adding in the titling part. I would think it would feel pretty familiar since we would still have to create the actual macro list to be used via the String function. Again, the Dev team has some smart cookies on board, so I'm sure they could figure it out lol :) Thanks again /salute
The effect would be pretty much exactly the same, the only difference is that you just go to a Moogle wearing the set you want to be in the macro, and get a snapshot instead of writing commands to equip the armor yourself.

From there, you can use the current system to call that snapshot instead of adding a new level to the system that allows you to call macros from within macros (liable to exploitation).


Wasn't trying to replace your idea with my own- it's the same idea, just thinking of how to deal with potential problems. I basically just took your idea and turned it into a black box so that it's easier to work with on both the development and user sides.




--------
That actually sounds pretty cool as well lol. Thanks for the feedback ^^/
I'm sure that there would have to be a near equally complex(which isn't very complex on either ideas) list of menu options to provide players the freedom to pick and choose which pieces they did or didn't want to be included in those snapshots.
This actually occurred to me as well and I edited as you were replying lol.


You could go to the Fashion Moogle wearing nothing but subligar, have him take a snapshot of you, name it "Nakey", and then use /equip snapshot "Nakey" to revert to that equipment set. If any single piece of equipment from the snapshot is not available when the macro is used, it would fail. If you had the subligar in your bag, it would make you "Nakey" wearing only subligar. I think something like this might be a lot easier to implement.

[kingfury]

True indeed /
I tried to put some stop gates for the possible exploitations issues, like the "Duplicating the same Macro String lines twice would not be allowed per 1 Macro(to prevent from endless looping)" and the, "Duplicating Grouped Macro Strings would not be allowed per 1 Macro(to prevent endless looping)".

In my deepest thinking, the system would have to have a built in security system that would flag down and cause such attempts to break the Strings whether done on accident or intentionally.
Even with everything functioning correctly, the system I'm proposing would definitely beef the power of macros to an all time high lol. I suppose I'm trying to create a solution on par to what PC players can accomplish with Windower version macros except in a legit way :D

Oh, no worries, I welcome such feedback with open arms, since I know for a fact more brains trying to solve a problem is far better than one ^^/

[Selzak]

The way you have it might not open up exploits, and it would definitely give players (us!) a lot more to work with...

...but

It's also very complicated for most users, and adding a whole new menu button in and of itself is a big change. I think that hiding the process somehow (like with snapshots) would make it a lot easier to work with on both ends.


Don't get me wrong, I would rather have your original idea. However, I just don't see them doing something that drastic and would like to at least see some form of it (much more applicable, but fewer capabilities) actually show up in the game.


I know for a fact more brains trying to solve a problem is far better than one ^^/
Also this. :)

[kingfury]

The way you have it might not open up exploits, and it would definitely give players (us!) a lot more to work with...
...but
It's also very complicated for most users, and adding a whole new menu button in and of itself is a big change. I think that hiding the process somehow (like with snapshots) would make it a lot easier to work with on both ends.
Don't get me wrong, I would rather have your original idea. However, I just don't see them doing something that drastic and would like to at least see some form of it (much more applicable, but fewer capabilities) actually show up in the game.
Also this. :)
-----------
I'm with ya lol I wouldn't care how it got done so long as it got done! /agreed

Now ya gotta think back to when they added "Macro Books" because that was a pretty major leap forward for our macro systems. Heck I'm still finding new ways to configure my Books lmao ^^ They did that leap in a huge way too by adding 20 fully customizable macro books, all while tossing in the "/macro book/set" syntax to boot. I can't even remember what we had before that update honestly lol ><

All that being said, give me your thoughts on how this concept would compare in difficulty to the macro book system. I would hope it's not as complex/difficult as that was since I tried to make it as simple as possible o.o; lol

[kingfury]

As an additional note: I think you have to give the players of FFXI a bit more credit too in regards to dissecting newly introduced systems. Abyssea is the absolute perfect example of this. I was, and still am amazed at how quickly folks unlocked the secrets of Abyssea. It was like SE put an enormous slab of meat in front of hundreds of sharks lol. At this point, most all of us are just chewing on the bones of Abyssea zones /laugh. I mean, it's only been a few months(9'ish) since Abyssea was introduced to FFXI back on June 21,2010, and we're already hungry for more content ><;

[Selzak]

-----------
I'm with ya lol I wouldn't care how it got done so long as it got done! /agreed

Now ya gotta think back to when they added "Macro Books" because that was a pretty major leap forward for our macro systems. Heck I'm still finding new ways to configure my Books lmao ^^ They did that leap in a huge way too by adding 20 fully customizable macro books, all while tossing in the "/macro book/set" syntax to boot. I can't even remember what we had before that update honestly lol ><

All that being said, give me your thoughts on how this concept would compare in difficulty to the macro book system. I would hope it's not as complex/difficult as that was since I tried to make it as simple as possible o.o; lol
Well Macro Books were essentially just "more macros" not really much going on there. At the time it was surprising because people had been begging for more lines for so long and suddenly we got 20x what we had.

This is new functionality altogether. Strings aren't macros (similar format, but different behaviors), and you'd probably be surprised by how many people don't understand macros as they are now. It might seem like common sense to you, but I'd be willing to bet that a lot of people would have a hard time even grasping the concept of calling commands from outside the macro. Not because they're dumb, but because this sort of thing requires a kind of conceptual understanding of programming that most people don't have.

That's not to say that there aren't some very clever people playing this game, but I think there's an illusion going on where 1% of the playerbase figures everything out and then everyone just works off of it. We're talking about something that everyone would need to actually understand.

[kingfury]

Nah, I'm pretty aware of the tons of folks that don't gear swap lol and you're absolutely right, this system would not be for them ^^ The macro system itself is an optional game feature that players don't have to use at all, but for the majority of seasoned players that have come to master them, this system would be a godsend.

I don't even know what I would do with myself if I only had to use one macro to cover gear swapping, weapon skilling, then back to gear swapping all in one click /stagger. My fingers would probably go through withdraws and accidently hit the macro multiple times out of habit lol. This system would cause me to reformat just about every macro I have, but it would be a breath of fresh air to say the least.

[Flunklesnarkin]

I don't think an extensive update to the macro system would be a good thing..

It would be nice if they could add a few lines to make gear swaps easier tho... hitting 3 or 4 macros to gear swap can be a pita...

Inb4 windower / third party tools >_>

[Tsukino_Kaji]

People should not be allowed to name thier macro strings, it'll take up too much space/information. They should instead of generic labels and macro string will have to be one command like /jobemote or /pcmd.

/macrosrting "String ##"

Otherwise another cool idea KF.

[Rambus]

both ideas would work, like to see what DEV replay is try get one of these in the game

[MarkovChain]

Idk if it's doable and I guess only SE can tell, but I think it would be better that the servers store your macro lines. They could add a menu where you set your lines and store them on the server. This would limit the lag (for example when combining sevral macro in a row).

[kingfury]

People should not be allowed to name thier macro strings, it'll take up too much space/information. They should instead of generic labels and macro string will have to be one command like /jobemote or /pcmd.
/macrosrting "String ##"
Otherwise another cool idea KF.
-------
Dually noted /nod, and great feedback to boot! Thanks Tsukino ^^/ but perhaps there could be a cap on both Single String and Group String titles per String category created. In my example I fabricated up to 20 Group Strings for the WAR example, but based on how powerful these would be, you could probably cap it even lower like 10 and still change the game forever. So maybe at the least, 10 Single String Titles, and 10 Group String Titles. If we could start modest and go up from there, it would be great. In any case I will definitely add this into the OP since your point is very true.

Just think about how much memory had to be blocked out for our 20 Macro Books which allows for naming (short 4-5 letter names, granted) about 200 macro titles per book. That's 4,000 customizable short macro titles. Not to mention whatever the character limit per macro line is. Hopefully with a limit placed on how many strings/group string titles, it would be a easy fit without bloating the system.
Great feedback as always! Thanks again ^^/

[kingfury]

Idk if it's doable and I guess only SE can tell, but I think it would be better that the servers store your macro lines. They could add a menu where you set your lines and store them on the server. This would limit the lag (for example when combining sevral macro in a row).
------
Thanks for the feedback ^^/
As with just about anything we suggest on these boards lol, but I'm hoping it wouldn't be anything too out of scope for the all mighty Dev Team. If anything, they would be able to find a similar solution like Seizak (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=63795&viewfull=1#post63795) did a few post back.

I didn't say so in the OP, but I would definitely opt for the servers to house the data, yes. Thanks for adding that point, I will make sure to edit that into the OP /bow

[kingfury]

both ideas would work, like to see what DEV replay is try get one of these in the game
------
As always, I'm hoping their watchful (and most likely tired ><; ) eyes do the great service and honor of reading my post ^^/ These Community Reps have done an amazing job processing and responding to a a good number of our post here, so even if they didn't reply, I am confident that they indeed will read it at least :) ... but Community Rep replies are much cooler than nothing lol so /crosses fingers

[kingfury]

**EDITED ORIGINAL POST**
Thanks for all the feedback guys /salute

Additional Notes:
Per each String category, there would be a String and Group String Title limit of 20 (could be as low as 10 if necessary). 20 single String titles, and 20 Group String titles. To avoid any potential bloating of the system due to Titling the Strings.(Thanks to Tsukino_Kaji's feedback)
----
Saving the String data to the Servers would be an option for storing this information.(Thanks to MarkovChain's feedback)
----
Cool alternatives:
-Selzak's idea(Post 1),(Post 2)

[kingfury]

It's times like these where I wish I had a few programmer friends to lend their wisdom lol If there is in fact any seasoned programers swimming around on the boards that could shine some light on how complex this concept would be to realistically implement for FFXI, it would be awesome to hear from you ^^ / As well as some refinement/alternative options to achieve the end goal of enhancing macros to these heights.

I'm going to dig around online to find some similar systems to reference that may help communicate it better perhaps than I have in terms of the programming side of things. If I find anything, I'll make sure to post it.

[Selzak]

I don't know any details about the game's code, but I don't think anything about this would be particularly hard to do.

They'd have to add functionality to macros that would let them execute "Strings", and that might be hard depending a lot of different things. A "String" is basically a macro, and an actual "String" call acts kind of like an array. I don't know whether or not that would be hard to implement based on how the game accepts commands, but it is basically adding a second dimension to commands so it might be hard.

/do thing1
-game: ok. *does thing1*

/do thing2
-game: ok. *does thing2*

etc...

--------------------------------------

stuff1 =
{/do thing1
/do thing2}

stuff2 =
{/do thing3
/do thing4}

/do stuff1-2
-game: huh?


One question we have to ask is why we can't already use a macro within a macro, because that's essentially what this is only with the added complexity of calling multiple macros in one command.

[Atomic_Skull]

This is overly complex for the PS2 and almost certainly couldn't be implemented due to memory constraints on that platform.

And while we would all like for them to just drop PS2 support realistically that's not going to happen.

A solution that could be implemented on the PS2 would be to just add a command that jumps to the next macro pallet down and continues running lines similar to how /set jumps to a different macro pallet. The /set command would be used to return to the original macro pallet.

[kingfury]

I don't know any details about the game's code, but I don't think anything about this would be particularly hard to do.
They'd have to add functionality to macros that would let them execute "Strings", and that might be hard depending a lot of different things. A "String" is basically a macro, and an actual "String" call acts kind of like an array. I don't know whether or not that would be hard to implement based on how the game accepts commands, but it is basically adding a second dimension to commands so it might be hard.
/do thing1
-game: ok. *does thing1*
/do thing2
-game: ok. *does thing2*
etc...
--------------------------------------
stuff1 =
{/do thing1
/do thing2}
stuff2 =
{/do thing3
/do thing4}
/do stuff1-2
-game: huh?
One question we have to ask is why we can't already use a macro within a macro, because that's essentially what this is only with the added complexity of calling multiple macros in one command.
--------

Great example ^^/ Yet I would only hope that the problem is this simple!
Looking at your example:
stuff2 =
{/do thing3
/do thing4}

/do stuff1-2
-game: huh?

You're absolutely right based on FFXI's current syntax language. It's like asking an English speaking person to speak Spanish on the spot lol. SE would have to simply teach the system a bit of Spanish so to speak ^^. So the new bits of language would be:

/do stuff 1-3=
{/do thing1
/do thing2
/do thing3}
Where "-" = and/or until you complete
-game: Oooohh! Is that what that means? No problem /wave
-game: *does thing 1, 2, and 3*
-------
I would think the good thing about "programing" is being able to re-teach a system how to process new/old types of data as the need arises to do so. Just look at what they did with the new <wait #> command. Essentially they just re-taught the system how to process/read the syntax. In other words(based on the analogy I used above), the system understands both the English (/wait #) and the Spanish (<wait #>) languages of the same command.

Try not to think only of our current macros in regards to the possibilities of if our system could handle the proposed concept. FFXI houses this very same complex nestled functionality in just about every other menu option we use in-game. A good example would be navigating to the equipment menu to change your gear. In essence one could reach the equipment menu by using the menu to navigate to our weapons and then select the weapon we want to swap in:

Menu > Equipment > Main Weapon > Widowmaker = Finished

But, we have the functionality to bypass those steps with one string of syntax:

/equip Main "Widowmaker" = Finished

Picture this process for a moment the same as the Macro issue at hand:

line 1. do something > line 2. do something > line 3. do something > Finish

Where the Macro String would be the equivalent solution as the equipment syntax:

/macrostring <"Title 1"> = Finished

So, my point would be to just mirror some of the other functionality elsewhere to that of the Macro systems.

[Selzak]

Yeah there's nothing too complex about it on paper, but you have to consider other things like, "Can a command execute multiple, separate commands?"

Obviously it's possible, but depending on how the game is written who knows how hard it would be to actually implement it at this point. The syntax isn't much of an issue, it's the actual process that might be difficult to handle. The difference is more like teaching it to say "wait" in Spanish vs. teaching it how to draw.

I don't know that it would be difficult, I don't even think that it would be lol...just trying to help answer your question. What I'd assume is that a macro could be "taught" to execute another by reference very easily, but that begs the question: Why can't we call macros from within a macro already?

Whatever the reason; technical, balance, etc. is what your Strings would want to address. I can't imagine that it's anything other than a balance concern.

[kingfury]

Yep, All I can do is speculate as well ^^;
Just gonna have to wait for one of the cool Community Reps like Camate or another to bless us with a bump to the Devs to see what the low down would be lol. /waves to Camate :) Thanks in advance ^.~

[kingfury]

I don't know that it would be difficult, I don't even think that it would be lol...just trying to help answer your question. What I'd assume is that a macro could be "taught" to execute another by reference very easily, but that begs the question: Why can't we call macros from within a macro already?
----------
A valid question. I would assume the answer would be the same for the question of: Why couldn't we have the <wait #> command that sits on the same line with other stuff from the begining? I would just think it's that some things take time to focus on and re-think the possibilities of how best to accomplish it.
Not to say that it's not possible, but rather, perhaps they haven't considered the possibilities of doing so yet. The same can be said for every enhancement made to the game thus far as well. Job adjustments, Trial of the Magains, the Exp leveling curve, etc. and the list goes on.

The unfortunate thing is, with MMORPG's, there's thousands of systems going on all over the place. Development teams have to put out the most pressing fires one by one before addressing the small ones.

[Flarez]

You should interview to work on the FFXI Dev Team!

[kingfury]

Actually it could be programed to read:

/macrostring group <"Group String Title">

Which would get rid of the possible syntax strangeness of the "(1-3)" lol. It would still be calling up to 3 macros to play one after the next, but this may be a cleaner approach.

[kingfury]

You should interview to work on the FFXI Dev Team!
-------
>< How does one go about doing this?! Camate!! Get me adopted please!! lol

[kingfury]

**EDITED ORIGINAL POST**

Macro String Groups:
A Macro String Group would allow up to 3 Macro Strings to be called on one Macro data line. The line data would appear as this:

/Macro String <"Macro String Title (1-3)">
Or this:
/macrostring <"Macro String Title (1-3)">
Or this:
/macrostring group <"Macro String Title">

[kingfury]

This is overly complex for the PS2 and almost certainly couldn't be implemented due to memory constraints on that platform.
And while we would all like for them to just drop PS2 support realistically that's not going to happen.
A solution that could be implemented on the PS2 would be to just add a command that jumps to the next macro pallet down and continues running lines similar to how /set jumps to a different macro pallet. The /set command would be used to return to the original macro pallet.
---------
Well I'm hoping to hear from an actual programmer to actually explain WHY this would be "overly complex" ^^; And in reference to the memory constraints, again, this would be essentially adding just a new level of macro management and control. Nothing more than list data and titles(a set amount of titles, not infinite amounts). That can't be that memory taxing... can it? o.o

in regards to a command that jumps to a different macro pallet and runs the next macro, there would definitely have to be stop gates to such a command to prevent endless looping. But I'd be happy with anything that would allow macro consolidation and efficiency.

[Dallas]

It's definitely within the game's reach (the basic code for something like this would take all of a couple of hours), but I think the first problems that would arise would be:

1) Exploitation
2) Complexity (on the user end)

I like the idea a lot, but from an objective standpoint I just can't see it fitting into the game.

Another way to handle this would be some kind of Moogle service where they took "snapshots" of what you're currently wearing. Instead of adding a whole new series of code for us to manipulate, a Moogle could take "snapshots" of what you have on and let you name them (up to a finite amount) to use in macros.

You could go to the Fashion Moogle wearing nothing but subligar, have him take a snapshot of you, name it "Nakey", and then use /equip snapshot "Nakey" to revert to that equipment set. If any single piece of equipment from the snapshot is not available when the macro is used, it would fail. If you had the subligar in your bag, it would make you "Nakey" wearing only subligar. I think something like this might be a lot easier to implement.

I only support this version if after using the command, a moogle comes out and takes a picture.

[kingfury]

lol, I'm sure that would be fun to see ^^

Honestly, when you think about it, if we could have two ways to accomplish these types of macros, Manual set ups(the player inputs the data manually) and Assisted set ups (using the photo Moogles), that would actually be ideal!

Manual would be for the Macro professionals that already are well verse and proficient in the art of creating and managing Macros.

Assisted would be this option for those not so proficient in the use of Macros and would just want to quickly create their macros.

I'm sure this would help with the learning curve for a myriad of players with different experience levels.

[Eeek]

I'm confused. Did the Dev Team recently remove the /macro set # and /macro book # commands from the game?

This is a solution to a problem that was addressed a long time ago. I'd be disappointed if the Dev Team spent valuable time overhauling the macro system again when the game has more pressing concerns.

[kingfury]

I'm confused. Did the Dev Team recently remove the /macro set # and /macro book # commands from the game?
This is a solution to a problem that was addressed a long time ago. I'd be disappointed if the Dev Team spent valuable time overhauling the macro system again when the game has more pressing concerns.
---------
Nope, those are still working fine ^^ And they did in fact address the separate issue of adding more macros to the system as well as a way to quickly navigate to them.

The issue that I'm proposing needs addressing, however, is a separate one altogether though. I'm not sure about how others play the game, but for me(as a DD), having to spam up to 6+ macros to get the most out of using a weapon skill each time currently is not very efficient. An example:

swap gear + ws(up to 3 macros) > swap gear > TP(up to 4-5 macros depending on weapon of choice), per 100TP(which is like every few seconds with max haste going)

This is getting to be quite the chore ^^ and equates to re-evaluating the possibilities of finding a smoother solution. Now just imagine for a second being able to hit one macro to do everything listed above. I don't really want to use Windower and other things of the sort, so I'm asking the Devs to revisit the macro system based on looking at the possibilities for a smoother, more efficient option. That isn't impossible by the way! It would only take some thinking and tinkering to find the most practical solution.

Granted, it isn't the end of the world, and I've come to terms with making the best out of the current options, but it CAN be fine tuned to run even smoother which would change the gameplay for the better for all. If "Improving Gameplay" isn't a pressing issue, then I'm not sure what is o.o

If you're unaffected by this issue, then I understand why you would feel this way, but I have to deal with it every time I play ^^. So I would be VERY pleased if they took even a moment to consider the overhaul of the current macro system, since their job as Developers is married to creating the BEST player experience possible.

[Camate]

While we can see the plus sides of the suggestion, there are some pitfalls involved as well. Being able to string together multiple macros would put too much of an emphasis on automation and that is a direction that the development team does not want to move toward.

Though I can’t promise a specific date, the development team is looking into UI and macro revamps for the future.

[kingfury]

While we can see the plus sides of the suggestion, there are some pitfalls involved as well. Being able to string together multiple macros would put too much of an emphasis on automation and that is a direction that the development team does not want to move toward.

Though I can’t promise a specific date, the development team is looking into UI and macro revamps for the future.
-----------

/kneel Thank you again Camate for lending an ear and taking the time out to post feedback. /salute Feedback from you all is the most I can ever ask for ^^ /

Stringing multiple macros would be the holy grail, but if it's not the direction the Dev Team wishes to go in, I can understand.

Does this in fact kill the possibility of at least having one String per Macro(Versus multiple)? I'm sure if the Devs are in fact planning on Revamping the UI, it will be a great jump towards the "more efficient macros" direction, so I feel relieved to know this ^^/

Also, Camate, did you get my Adoption request? I'm an orphaned(as in "currently freelancing" ^^) young artist looking for a Development Team home:D /Kingfury readies "Puppy Dog Eyes"!

[Camate]

-----------

/kneel Thank you again Camate for lending an ear and taking the time out to post feedback /salute Feedback from you all is the most I can ever ask for ^^ /

Stringing multiple macros would be the holy grail, but if it's not the direction the Dev Team wishes to go in, I can understand.

Does this in fact kill the possibility of at least having one String per Macro(Versus multiple)? I'm sure if the Devs are in fact planning on Revamping the UI, it will be a great jump towards the "more efficient macros" direction, so I feel relieved to know this ^^/

Also, Camate, did you get my Adoption request? I'm an orphaned young artist looking for a Development Team home:D /cheer

I'm not so sure about adoption, but if it's a job you are looking for, take a look at
Sqaure Enix's career page (http://www.square-enix.com/na/careers/). This was the gateway for many of us that work here and it is always worthwhile to check it out!

Your art work looks fantastic and I have no doubt you will find an art related job somewhere^^

[kingfury]

I'm not so sure about adoption, but if it's a job you are looking for, take a look at
Sqaure Enix's career page (http://www.square-enix.com/na/careers/). This was the gateway for many of us that work here and it is always worthwhile to check it out!
Your art work looks fantastic and I have no doubt you will find an art related job somewhere^^
------------
\(^^)/ */cheer*
/Kingfury uses Puppy Dog Eyes! (http://i19.photobucket.com/albums/b167/soulchld4/PuppyDogEyes-Web.jpg)

Thank you tons Camate! I'll definitely check it out! /kneel

[Alhanelem]

I'm not so sure about adoption, but if it's a job you are looking for, take a look at
Sqaure Enix's career page (http://www.square-enix.com/na/careers/). This was the gateway for many of us that work here and it is always worthwhile to check it out!

Your art work looks fantastic and I have no doubt you will find an art related job somewhere^^
i guess the question is do all of the community team members and forum moderators necessarily have to live in SoCal?

(Does Square Enix publish any titles from north american studios?)

[Fiarlia]

UI revamps? Well this comes as a pleasant surprise. Now I'm quite intrigued. >_>

[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/threads/686-What-Everybody-Wants-Shorter-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/threads/686-What-Everybody-Wants-Shorter-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) (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=63782&viewfull=1#post63782),(Post 2) (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=63795&viewfull=1#post63795)
-Tamarsamar's idea (http://forum.square-enix.com/ffxi/threads/686-What-Everybody-Wants-Shorter-Simpler-Macros)
---------
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 (http://forum.square-enix.com/ffxi/threads/4619-New-quot-Macro-Strings-quot-Macro-s-Reborn!?p=65197&viewfull=1#post65197) /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;

[Keyln]

While we can see the plus sides of the suggestion, there are some pitfalls involved as well. Being able to string together multiple macros would put too much of an emphasis on automation and that is a direction that the development team does not want to move toward.

Though I can’t promise a specific date, the development team is looking into UI and macro revamps for the future.

I would like to point out that it isn't automatic macros necessarily that most people want, but the ability to swap gear in and out with a single button press. The way it is now is a big problem.

For example, when I play Summoner, when I use a Blood Pact, I have to press three buttons. The first button is to activate my Blood Pact, as well as swap in my Blood Pact Delay - gear, then I press a second button to swap in my avatar magic optimization/physical optimization/summoning magic optimization gear, and then I need to press a third button to swap in my avatar perpetuation optimization set (No perpetuation cost kupo!).

In short, I need to press three buttons to do one job. If I can limit to one button, that'd be great.

[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 (http://www.square-enix.com/na/careers/#ged01), 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 (http://www.playonline.com/pcd/topics/ff11us/detail/6366/detail.html) 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]

I would like to point out that it isn't automatic macros necessarily that most people want, but the ability to swap gear in and out with a single button press. The way it is now is a big problem.
For example, when I play Summoner, when I use a Blood Pact, I have to press three buttons. The first button is to activate my Blood Pact, as well as swap in my Blood Pact Delay - gear, then I press a second button to swap in my avatar magic optimization/physical optimization/summoning magic optimization gear, and then I need to press a third button to swap in my avatar perpetuation optimization set (No perpetuation cost kupo!).
In short, I need to press three buttons to do one job. If I can limit to one button, that'd be great.
------------
/Agreed, This is in essence the basis of my proposed concept in a nutshell. Granted, I opted for even more power with group strings which would pull in up to 3 macros at once per macro line ^^; but the request is the same overall. Pressing "One" macro to handle a complete gear swap would be ideal.

I pray that whatever the revamped Macro UI comes out to be, it answers, at the very least, this request.

Thanks for the feedback /

[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.

[Duzell]

When I started I asked a GM why i couldn't have Macro 1 Turn on Macro 2 and the GM told me it prevents automation. The example they gave is Macro 1 having 3 enhancing spells, and 2 having 2 spells and refresh and having #1 start #2 and #2 start #1 so you could go AFK and cap enhancing magic. So long as there is no way for this situation to occur I see no reason why you couldn't allow a gear set as a single macro line in some way.

[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 (http://forum.square-enix.com/ffxi/threads/686-What-Everybody-Wants-Shorter-Simpler-Macros), 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.

[kingfury]

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 (http://forum.square-enix.com/ffxi/threads/686-What-Everybody-Wants-Shorter-Simpler-Macros), 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.
---------
Awesome feedback ^^ / Thanks friend

Again, like I said in the OP ^^,

"I'm not a programer, but I've seen the Dev Team produce some amazing feats over my years of playing FFXI, and this (at least in my mind) would be easy prey to tackle Of course this is just a suggestion for making things better/more efficient, so if my ambitions are too high with this proposal, then maybe it will serve as a bridge to newer thinking and approaches to the subject of improving Macros for all."

I'm very glad that this has in fact happened based on my post and the others like it. ^^ However I believe the weary feedback that I'm getting from my proposed concept vs Selzak's and Tamarsama's is due mostly because it doesn't focus on "gear sets" only. I would like to think that the memory used for macro lines can't be very much, but I can't pull up the files using my Xbox 360 to check the file size like, I would assume, PC users could. I suppose I would just love the ability to swap gear + WS + swap back into TP gear with the use of only one macro line ^^;. With the feedback stated in a few post(yours as well), including the post from Camate, I now understand the pit falls associated with my concept. It would indeed need a hardy dose of policing functionality to prevent abuse towards automation.

If I took out the ability to input the macro lines manually and other commands such as JA, spells, etc. my concept would just about mirror the other concepts, which is pretty much the correct thing to propose anyway ^^. Thanks again for all the great feedback guys. /salute

I'll edit my post accordingly based on all this great feedback.

[kingfury]

Actually, if I could get the permission from both Selzak and Tamarsama to illustrate their concepts since they are so similar, that would be the direction of my edits to my OP.

[kingfury]

**EDITED OUT OF ORIGINAL POST DUE TO POSSIBLE AUTOMATION PITFALLS**
*Note: After all the great feedback posted in response to my OP, I can now understand the issues that would arise from this functionality and thus make this concept easy to abuse. The OP has since been updated to only allow equipment to be inputed within the macro data lines. I felt it was in the spirit of understanding that this idea should at least be noted within the thread. Thanks for all the feedback ^^/

Macro String Groups:
A Macro String Group would allow up to 3 Macro Strings to be called on one Macro data line. The line data would appear as this:

/Macro String <"Macro String Title (1-3)">
Or this:
/macrostring <"Macro String Title (1-3)">
Or this:
/macrostring group <"Macro String Title">

The “-” between the “(1-3)”would be the equivalent function to "and/or until you complete" and would thus run them automatically one after the other. Duplicating Grouped Macro Strings would not be allowed per 1 Macro(to prevent endless looping).
-Entering Macro Strings-2 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-2.jpg)
-----
Selecting a Macro String Group from the String Menu:
-Entering Macro Strings-3 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-15-1.jpg)
-----
The Macro String Group Editing Menu:
-Entering Macro Strings-4 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-16.jpg)
------
The expanded view of the powerful Macro String Group lines:
-Entering Macro Strings-5 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-9.jpg)

[kingfury]

**EDIT TO ORIGINAL POST** (Reason: MOVED to clear OP real estate)
*WAR setting up his/her macros to quickly equip gear to be used for Raging Rush would be able to create 3 separate macros to do so. In this example, however, the WAR will be setting up the macros using the Macro String system.*
-----------------
Selecting Macro from the menu options:
-Macro String Menu-1 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-10.jpg)
-----
Selecting "Strings" from the "Book/Strings" menu:
-Macro String Menu-2 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-11.jpg)
-----
The String List Menu would display "String Categories", and "Strings".Choosing "Strings" from the list would allow players to create, edit, and name a Macro String:
-Macro String Menu-3 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-12.jpg)
-----
Creating a Macro String:
-Macro String Menu-4 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-14.jpg)
-----
Filling in the Macro String line data per each Macro list:
-Macro String Menu-5 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-3.jpg)
---
-Macro String Menu-6 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-4.jpg)
---
-Macro String Menu-7 (http://i19.photobucket.com/albums/b167/soulchld4/MacroStrings-example-5.jpg)

[kingfury]

**ENTIRE ORIGINAL POST REVISED (APR/7/2011)**
----------
Edited:
-Cover Art
-Description
-System Mechanics
-Entering Macro Strings
-Macro Book/Set change request
-Macro String Groups
-Macro Syntax/Internal System to differentiate Same Named gear
-----------
Again, thanks to everyone for the wonderful feedback ^^/
Camate, If you would do the honors of blessing us again with feedback based on the changes to the post, it would be overly appreciated! Even though you've shared with us that the Dev team will in fact be revising the UI of the macros, myself, and I'm sure everyone else would love to hear if the changes made to the OP are more geared towards the direction of where the Dev Team would consider in line with their possible plans. :D

Thanks in advance /kneel + /salute

[kingfury]

I was still a bit disappointed that a professional programmer didn't chime in on this topic. I would still very much appreciate the feedback based on the changes made recently as well if at all possible.

Heck if I knew a programmer at this point in my life, I'd be forcing him to make a small game for me >< lol.

[Tamarsamar]

Actually, if I could get the permission from both Selzak and Tamarsama to illustrate their concepts since they are so similar, that would be the direction of my edits to my OP.

I'm already quite flattered. :D

I think it'd be cool if you would illustrate my idea!

[CrystalWeapon]

I was still a bit disappointed that a professional programmer didn't chime in on this topic. I would still very much appreciate the feedback based on the changes made recently as well if at all possible.

Heck if I knew a programmer at this point in my life, I'd be forcing him to make a small game for me >< lol.

What kind of game did you have in mind? ^_~

Serriously though if you want to learn more about it yourself there are plenty of free guides on the web that could teach you more about programing than you would learn getting an official degree. Try to find a free game engine, get an express version of Visual Studio (free download from MS), and have at it. Fairly sure you could find some 3d modeling software as well, which seems like something you'd be a natural at.