I'm setting up my framework so the DM can hide save/ability/skill checks from the players. Also if the players want to hide their attack/initiative rolls/etc. I've got most of it working (tooltips are a bane here) but I've still one problem.
Some of the macros still generate a blank line/cr it seems. Say a player uses the ability check macro it will send the normal output to the DM but the players still get the "ding" noise from someone typing CR and their name but no text in it.
I seem to recall there being some odd behavior with <!-- --> tho I thought that was frame/dialogs. Either way I went through the process for one macro and found none.
Any theories?
Private/hidden macro output, still generating CRs?
Moderators: dorpond, trevor, Azhrei
Forum rules
PLEASE don't post images of your entire desktop, attach entire campaign files when only a single file is needed, or generally act in some other anti-social behavior.
PLEASE don't post images of your entire desktop, attach entire campaign files when only a single file is needed, or generally act in some other anti-social behavior.
Re: Private/hidden macro output, still generating CRs?
You can save the chat log and it will show you the "blank" line. It probably is a <!-- comment --> somewhere. Text is not displayed but it is treated as content.
Downloads:
- Notepad++ MapTool addon
- RPEdit details (v1.3)
- Coding Tips: Modularity and Design
- Videos: Macro Writing Tools
Re: Private/hidden macro output, still generating CRs?
Hum, I tried that and while it did show the one macro that did have <!-- comments --> all I get is this on another.
I do not use /div anywhere in my macros so not sure where that's coming from. Infact I think it's part of the chat system because the <!-- comment --> versions had the same thing only showed the "<!-- comment -->" bit also followed by the above. Once I removed the comments I got no more.
My only guess is that last CR below /html is coming from something? I use the same macro, one in a macroLink the other is just a button macro. The button macro works fine but the macroLink produces the above output when it's suppose to be DM only. This probably has something to do with the "all", "self" "gm-self" "none" settings? I can't use none, nor gm-self... I want the macro to determine where the output goes not macroLink.
Code: Select all
Bruni:
</td>
</tr>
</table>
</div>
</body>
</html>
My only guess is that last CR below /html is coming from something? I use the same macro, one in a macroLink the other is just a button macro. The button macro works fine but the macroLink produces the above output when it's suppose to be DM only. This probably has something to do with the "all", "self" "gm-self" "none" settings? I can't use none, nor gm-self... I want the macro to determine where the output goes not macroLink.
Re: Private/hidden macro output, still generating CRs?
I've had another "hide" not working tonight and for the life of me it makes no sense.
Everytime that macro is run you'll see in the chat window:
I've added an option to that to make sure that's where it's coming from and it is.
Will show both test= and totalWeight= when the user runs the macro attached to that.
Code: Select all
[h: macro.return=strformat("totalWeight=%{totalWeight};")]
Code: Select all
Briar:totalWeight=42;
Code: Select all
[h: macro.return=strformat("test=%{class}; totalWeight=%{totalWeight};")]
Code: Select all
Bruni:test=oddRow; totalWeight=43;
Re: Private/hidden macro output, still generating CRs?
that is correct output!
The statement IN the macro is hidden, however if you use [macro.return=] then IF there is NO ouput of the macro THEN the macro returns whatever is in assigned to macro.return... !
To hide that you need to hide the macro output of that macro e.g.
the macro
"Hello"
contains:
then you need to call it as
if you set 'ignore output' in the UDF... for 'Hello' then i don't know what will happen.
to put it differently
will return 2 and
will return 500.
The statement IN the macro is hidden, however if you use [macro.return=] then IF there is NO ouput of the macro THEN the macro returns whatever is in assigned to macro.return... !
To hide that you need to hide the macro output of that macro e.g.
the macro
"Hello"
contains:
Code: Select all
[h:x=1+1]
[h:macro.return=x]
Code: Select all
[h:Hello]
to put it differently
Code: Select all
[r:x=1+1]
[h:macro.return=500]
Code: Select all
[h:x=1+1]
[h:macro.return=500]
GETTING STARTED WITH MAPTOOLS - TUTORIALS, DOCS, VIDEOS, TOOLS, ETC
DISCORD (the new MT forum!)
My stuff
Excel Tools: Table and Light editors
MT Tools: Bag of Tricks: Tools for Maptool, Dungeon Builder I, Dungeon Builder II,onMouseOverEvent.
Frameworks: Dark Heresy, Rogue Trader, Deathwatch, Black Crusade, Only War, SET Card Game, RoboRally
Wiki: Debugging Tutorial, Speed Up Your Macros, Working With Two CODE Levels, Shortcut Keys, Avoiding Stack Overflow, READ THIS
DISCORD (the new MT forum!)
My stuff
Excel Tools: Table and Light editors
MT Tools: Bag of Tricks: Tools for Maptool, Dungeon Builder I, Dungeon Builder II,onMouseOverEvent.
Frameworks: Dark Heresy, Rogue Trader, Deathwatch, Black Crusade, Only War, SET Card Game, RoboRally
Wiki: Debugging Tutorial, Speed Up Your Macros, Working With Two CODE Levels, Shortcut Keys, Avoiding Stack Overflow, READ THIS
Re: Private/hidden macro output, still generating CRs?
If I could I would display the weight in the macro above but the way I display I want the weight in another table that is manipulated in the previous macro().
I guess I could put the value in a property and just pull it in that way but if there is a way to get around this it would be useful.
The way I call the macro is UDF(First)->[macro(Second)]->UDF(thisISTheReturnMacro). I did find that if I used [h:UDF(First)] on the initial call it would display the frame correctly AND hide the weight return. If I use [h: macro(Second)] it would hide all the output from UDF(thisISTheReturnMacro) as expected and defeat the purpose.
I guess I could put the value in a property and just pull it in that way but if there is a way to get around this it would be useful.
The way I call the macro is UDF(First)->[macro(Second)]->UDF(thisISTheReturnMacro). I did find that if I used [h:UDF(First)] on the initial call it would display the frame correctly AND hide the weight return. If I use [h: macro(Second)] it would hide all the output from UDF(thisISTheReturnMacro) as expected and defeat the purpose.