Cewl feat: fully auto create macros on token

[wolph42]

At least I think its a cewl feat ...

Thanks to patoace target.campaign I got the idea of creating token macros fully automatic, so no buttons to push, just drag a token on the map, deselect it, then select it again (click on it) and all the macro buttons 'magically' appear.

I've embedded the function in my current DH framework. The trick is in the property: Initiate and in the macro Initiate on the DH:Lib. These two are the only things you need to make this work.

The howto:
Add:
*Initiate:[macro("Initiate@lib:DH"):""]
to your token properties ("lib:DH" needs to be replaced with the name of your lib token)
and add the following macro to your lib token

Initiate

Code: Select all

<!--requires macros to be user defined on lib token-->
[h:createMacro("Use Skill","[r:UseSkill()]", "group=Manage Character; color=default; fontColor=black; sortBy=3; playerEditable=0")]

<!--Alternative: doesnt require them to be user defined:-->
[h:createMacro("Show Char adjustments","[macro("Edit tmpStats@Lib:DH"):""]", "group=Manage Character; color=default; fontColor=black; sortBy=5; playerEditable=0")]

repeat for other macros

[r:setProperty("Initiate", "")]  

It's insanely simple and possibly done before but I haven't encountered it yet...hence this post!

[Rumble]

Very cool. I was just going to ask how you kept it from repeating the process, when I noticed the last line.

That's an ideal addition to a framework. I'm going to adopt it for my D&D framework, too. A little tedious to get coded, but once it's done, it's in 'ere.

[wolph42]

obviously I found something for the tedious part as well

added xls file. Put the xml part of the macros of a 'macroed' token in the excel file (Sheet1) and start copy pasting, first into word where you can use search and replace ^p^p with ^p to remove all excess linebreaks and then paste it into Sheet2.

Make sure the lines correspond or things get fu.

It takes a bit of figuring out, but it saves the tedious hassle of coding every macro...

[Rumble]

Interestingly...it won't stop doing it for me, even with the code at the end there to overwrite the property.

Ah, nevermind - an error in the code was preventing it from getting that far.

[koralas]

Very cool, only, for me, it doesn't work if you have the "playerEditable=0" parameter enabled. With this, I get an error "setMacroProps(): You do not have permission to change player editable status". Is there something else I need to set somewhere for this to work properly?

[wolph42]

Very cool, only, for me, it doesn't work if you have the "playerEditable=0" parameter enabled. With this, I get an error "setMacroProps(): You do not have permission to change player editable status". Is there something else I need to set somewhere for this to work properly?

i have absolutely no clue. One thing you could try though is download my Framework drag a token to map to see if it works. If it does then you're indeed doing something wrong. If not its due to a setting. Mind that it took me quite some trouble to get it to work. It does need some tinkering.

hope this helps

[koralas]

Very cool, only, for me, it doesn't work if you have the "playerEditable=0" parameter enabled. With this, I get an error "setMacroProps(): You do not have permission to change player editable status". Is there something else I need to set somewhere for this to work properly?

i have absolutely no clue. One thing you could try though is download my Framework drag a token to map to see if it works. If it does then you're indeed doing something wrong. If not its due to a setting. Mind that it took me quite some trouble to get it to work. It does need some tinkering.

hope this helps

I'll do some more testing, see if I can find anything. Thanks.

[Irrlicht]

This is no doubt a very good idea, but I have a little issue (maybe this is a noob thing, and I hope it is, so that it may be easily overcome): how can I differentiate PCs and NPCs macros?
I mean: at present, I have two different sets of macros, one for PCs and one for NPCs, that I load as needed when adding a new PC or NPC token. The two sets have mostly the same macros, for example "Fortitude Save" or "Acrobatics Skill"; the difference is that all the macros in the NPC set begin with "/self", so that only the GM can see their results.
So, how could I differentiate the PC and NPC macros with the method presented here? (Don't tell me that NPC macros' results are automatically hidden to players, that would be hilarious...)

[wolph42]

They're not. Use an if statement in The code if(isNpc):...;...

[Irrlicht]

Seems that using [if(isNpc()): "/self"; ""] at the beginning screws the code up.

I could use:

Code: Select all

[if(isNpc()), code:
{
[g: A]
[g: B]
};
{
[r: A]
[r: B]
};]

But that would only result in a single heavy macro with a double code in it, rather than two lighter macros (as is now). Is there an easier solution?

[jfrazierjr]

Seems that using [if(isNpc()): "/self"; ""] at the beginning screws the code up.

slash commands CAN ONLY be at the beginning of the first called macro. Embedding a slash command somewhere else is a fruitless trial. However, there are several roll options that might do what you need....

[wolph42]

I should have read better what you posted. What you want is indeed easily solved with roll options:

Code: Select all

[s:A...]
[s:B...] 

This will show result only to self (and gm, if not to gm, make it [s,g:A..])
If you actually want to run different code for pc and npc, you'll need my former post

[Irrlicht]

Nope, the code is the same, but I need PC things to be visible to all (not just self and GM), and NPC things only to GM. I take it there is no solution other than having a single heavy macros or two lighter macros, until counterproof.

[Azhrei]

Nope, the code is the same, but I need PC things to be visible to all (not just self and GM), and NPC things only to GM. I take it there is no solution other than having a single heavy macros or two lighter macros, until counterproof.

Did you read the list of roll options on the wiki? In particular, [gm:]?

[Irrlicht]

Yep, but how can I make it so that if the token is a PC things are displayed with r: and if it is a NPC those same things are instead displayed with g:/gm: without writing the same code two times, once for r: and once for g:/gm:?