Ok, second issue first: This is a Typo. It looks like Sam simply left out the word "with" here, and should be an easy fix once he decides to do it. Regarding the first issue, this is because of the fundamentally screwed-up workaround required to make the attack buttons in the first place. Let me explain. No, is too long. Let me sum up: There are two different buttons for any given attack. One is internal, and cannot be made into a Token Action, but it's the one that uses the contents of the "Macro Text" field, and can therefore be easily modified by the user. The other is external, being the corresponding button in the big row-of-26-buttons. These CAN be used as Token Actions, but due to the nature of the beast, cannot be easily modified. People wanted both, and Sam was able to accommodate them only by doing this. If you want to change the macro, by changing the 'macro text' section, you have to use the internal button. Or use the information shown to make your own macro, which is a pain in the ass. For the curious.. TL/DR Version: Because it's impossible to access the contents of repeating fields (which the attack fields are) in the normal fashion, a work-around was needed. This consists of making an entirely separate macro for each field, copying the functionality of the one in the 'macro text' box but being entirely separate from it. Within the repeating field for each weapon, one can simply say 'use this field's attack bonus, add this field's damage rolls, and print out this field's note section' and the computer knows what you mean, since it's part of the repeating section. This is reflected in the 'macro text' box's macro. More on this later. However, outside of the repeating field, this isn't possible. If you say 'use the attack bonus for this weapon' the computer doesn't know which weapon 'this weapon' is... the contents of a repeating field don't actually exist, from a certain viewpoint, unless you're already 'inside' that section. So, what Sam ended up doing is re-creating the entire macro text section for each of 26 possible repeating fields! In each of these copies, instead of 'use this weapon's attack bonus etc', it says 'use weapon four's attack bonus etc'. This is how you have to write a macro that exists outside of a repeating field, to access the information within a repeating field: you have to include WHICH FIELD YOU WANT in every part of the macro! Now, as to why this was done, it's so it's possible to use these buttons as Token Actions. Since one cannot just simply copy and paste the 'macro text' (due to its length and complexity and the need to change it to indicate which field you're looking at), but people still wanted to use token actions, this work-around was designed. The up side is that you can now put as many weapons as you want into a character sheet, and (relatively) easily turn them into Token Actions by simply putting the corresponding button into the "Ability" section of your sheet. For example, if the first attack in my sheet is "Shortsword", I can make an Ability called "Shortsword", have its text be simply "%{selected|repeating_weapon_0_attack}" (which is the name of the 0 button, shown when you hover your mouse over it), and make that a Token Action. This is MUCH easier than re-writing an entire paragraph of macro for each desired weapon. The downside is that you're kind of stuck with what Sam designed... which isn't to say there's anything wrong with it, it's quite a good macro. However, since each of these 26 buttons has to specifically and individually contain the information for which repeating field it's looking for, they're kind of hard-wired to be what they are and nothing else. So what's the "Macro Text" box for, you ask? Well, I said I'd get to that... you'll notice that each repeating section has its own button, internally. THAT button calls up the contents of the "Macro Text" field. The upside to this is that, if you want to change the way the attack appears, you can modify the contents of that attack's 'Macro Text" field to your heart's content. The downside to this is that it's impossible to turn an internal button like this into a Token Action: the computer simply doesn't understand that the information it wants exists! The good news is that, if you take the time to figure out how it works (made easier by having the "Macro Text" information visible like this) you can then go on to alter the various calls and make a Token Action type macro of your own. Basically where the macro text says "@{name}" you change it to "@{selected|repeating_weapon_#_name}", and you have to do this with EVERY SINGLE CALL within that macro. So, yeah, you can make your own macros as Token Actions, but... it's a lot of work. Work you don't have to do, since Sam kindly did it all for you, in the form of that row of 26 buttons. Hope that helps (or at least helps you sleep, if you read it all!) -Phnord
