Known Issues Importing Macros?

I'll come back and update this topic later when I get home - my machine has stopped letting me remote into it - but...

Are there any considerations I need to understand with importing macros from one campaign file into another?

I'm stitching together my own framework for OD6, taking pieces I like from the others available out there, and one of the ones I brought over this morning is throwing a syntax error in my framework only. The process was:

1) Try macro in original framework. Works great, and I like it. (It was a 4e-something. Highlighting tokens. I'll add that detail when I have access to it...)

2) Export to file.

3) Import into my framework.

4) Test, get error in chat.

5) Switch back to other framework, still working.

From what I can see, no libs are being used, nor anything else referenced. It 'should' run in either framework, right? Or is there some kind of trust I need to set on the imported macro first? I've seen the notion of 'trusted macro', but I'm not clear on how to interact with that.

Again, more detail later, but if there's anything obvious that I'm missing, I'd love to learn more about this excellent tool.

EDIT1: More detail...

The macro is from 'rfw-dnd-v513.cmpgn' and contains this code:

Code:

[h:assert(isGM(), "Only the GM can use this macro.",0)]

[h:filter = json.set("{}", "pc", 1)]
[h:tokenList = getTokens(",", filter)]

[h,foreach(token,tokenList),CODE:
{
   [switchToken(token)]
   [state.PCHalo = 1 - state.PCHalo]
}]

[h:abort(0)]

'trusted macro' is a macro run from a library token or campaign (afaik), with "players can edit macro" unticked.

mcbobbo wrote:

Are there any considerations I need to understand with importing macros from one campaign file into another?

Based on the code piece below there are some custom States

Code:

state.PCHalo

that are being referred to. So you may need to include any states that the code refers to or change the code. The code may also refer to campaign properties that you may not have in your framework.
It would also help if you posted the error you received then we could be more specific about our responses.

mfrizzell wrote:

It would also help if you posted the error you received then we could be more specific about our responses.

True, true - here is the output:

Code:

Error in body of roll.       Statement options (if any): h,foreach(token,tokenList),CODE       Statement Body : { [switchToken(token)] [state.NPCHalo = 1 - state.NPCHalo] }

Here's what I changed to fix it:

Code:

[h:assert(isGM(), "Only the GM can use this macro.",0)]

[h:filter = json.set("{}", "npc", 1)]
[h:tokenList = getTokens(",", filter)]

[h,foreach(token,tokenList),CODE:
{
   [switchToken(token)]
   [h, if (getHalo()=="None"): setHalo("Red"); setHalo("None")]
}]

[h:abort(0)]

I still need to learn 'why' that happened, but I assume that the other framework used a state to control halos and it isn't in maptool by default?

Right, for the most part, theres only a handful of "universal" states that are in the default campaign properties. Anything else you'd have to add yourself. I'm not sure if importing campaign properties adds, or overwrites, so make sure if you do it that way you test first, you may need to copy things by hand

aku wrote:

Right, for the most part, theres only a handful of "universal" states that are in the default campaign properties. Anything else you'd have to add yourself. I'm not sure if importing campaign properties adds, or overwrites, so make sure if you do it that way you test first, you may need to copy things by hand

overwrites!

A merge option would be nice for campaign properties. It would make packaging more complicated drop-ins easier, mostly for new states, imo.

I suppose you could do it with an xml merge tool and dragging all the assets together, but that wouldn't be intuitive or easy for the casual user.

RPTools.net

Known Issues Importing Macros?

Who is online

Top

Top

Top

Top