Thanks Gauss, for the links! Here is a Fetch + ZeroFrame example, using your macros. The thing to remember with these is whether or not the command line of each sub-macro is sending a standard chat message or a mod-script message. If it is sending a standard message, we are going to have to use a ZeroFrame {&simple} construction to output the message to chat. Quick Explainer In order to engage the metascripts (like Fetch & ZeroFrame), we need to start our message with an exclamation point. That creates a message that is sent to the Script Moderator instead of the chat panel. Once the metascripts are done, if what is left in the command line is intended for a script, we can just let it go (the message passes from the metascripts into the normal scripts). On the other hand, if what is left in the command line would have been intended to hit the chat (for instance, the result of the query leaves a Fetch construction that retrieves a macro, and that macro is intended to be a simple chat ouput message), then we need to include the {&simple} tag to make that happen. Placement of the SIMPLE We can put the {&simple} tag in a few places... we can put it in each sub-macro, or we can put it in the top-level macro that bundles the others up in a query. If we put it in the top-level macro, we can put it outside the query (to make it apply to any/all query options), or we can put it in individual query options if we want it to apply to some but not all potential choices. Typically, for a number of reasons I won't get into right now, I suggest putting the {&simple} in the top-level macro wherever it is needed. I am going to assume that every macro in your set is a standard message, so we can get away with putting it outside the query. That would look like this: !?{Which macro?|Attack Fist,#(Atack-Fist)|Atack Sword,#(Attack-Sword)|Atack Magic,#(Attack-Magic)} {&simple} Just for the sake of example, if we assume that the first 2 options in that query (Attack Fist and Attack Sword) were supposed to be simple chat messages but the last (Attack Magic) was a call to a mod script), then we would have to include the {&simple} inside the query for the first 2 options. Since that tag has a character that would break a query (the closing brace), we'll have to do an HTML replacement on it. The final version of the macro where the first two query options were intended to be simple chat output while the third would be a mod script call would look like this: !?{Which macro?|Attack Fist,#(Atack-Fist) {&simple} |Atack Sword,#(Attack-Sword) {&simple} |Atack Magic,#(Attack-Magic)} REQUIRED SCRIPTS: ZeroFrame , Fetch
