Yeah - putting that on the core tab should be optional like all the other settings. Getting back to my response, keithcurtis said: Brian C. said: I feel like I'm missing something here. You can put the roll template components in any order you want. Can you show me an example of incorporating the additional macro? Although you can manually construct them any way you want, the description does not come last as sent by the sheet. There was a trick a lot of people used to use to insert macro code into the description field of an attack by beginning it with "}}" that has been unavailable for several years, due to a re-order, You can still do it, but its a lot more coding than before. Essentially, it means letting it go through once, copying everything after "{{desc=<content...>" and inserting it in the description with the "}}..." from desc on. Then after, hitting a new line, inserting macro code, hitting another new line with "!." on it. By then, your attack, spell, trait, whatever looks more like programming than D&D until its clicked into chat. Onto new business though: When was the last time this Mod Info was updated?:
5th Edition OGL by Roll20 Companion
Version: [Latest]
Authors:
Steve K., Chris M., Christopher D.
Enhances the Official 5th Edition OGL by Roll20 Character Sheet. The
Companion currently supports Ammo Tracking, Automatic NPC Tokens,
Automatic Death Save Tracking, and Automatic Spell Slot Tracking. API Commands:
!5ehelp - Gives a list of the script's API commands in the chat tab.
!5estatus - Lists the current status of the script's features in the chat tab.
!ammotracking on/off/player/quiet - Automatically expends linked resource when attack is made.
!autonpctoken on/off - Automatically generates a NPC
token on the GM's screen based on the default token when an NPC's health
calculation is rolled
!deathsavetracking on/off/player/quiet - Automatically
ticks off successes and failures when death saves are rolled, clearing
on death, stabilization, or hp recovery
!spelltracking on/off/player/quiet - Automatically expends spell charges as cast, factoring in higher level casting
!longrest character name - If spelltracking is on, this command will reset all of the character's spell slots to unspent.
!npchp character name - Rolls NPC hit point totals
using their formula and updates the token bar. If no character name is
provided it will roll the selected tokens. Options:
on - Toggles the functionality on (default)
off - Disables the functionality
player - Maintains functionality but only sends data to the GM and the player involved.
quiet - Maintains functionality while preventing results from being output to the chat. Ammo Tracking:
Directions for ammo tracking can be found in the wiki .
You can spend more than one piece of ammunition per shot by adding a
number after the name of the ammunition resource and a comma. (ex.
Arrows,2 )
There's no new info as it pertains to the sheet functions, such as !shortrest ? And !npchp Character Name doesn't seem to work anymore. Instead of putting pretty red charactermancer buttons where they don't need to be, can the dev team get back to some basics? Maybe update old news, provide working functions, etc? I don't know why development teams tend to work on "New Features" without making sure they haven't broken or depricated the old - I saw this in DDO, big time! Now Roll20 seems to be going that route. This past weekend, my game became unplayable, requiring me to restart my instance every time I moved my tokens or deducted HP. I'm pulling my game (and Sub) from here to another VTT because of that. But I still play with another group here, where I help them with their macro coding. It'd be nice if I could get her tokens to drop on the board with the HP rolled, but it doesn't. So I tried " !npchp @{selected|character_name} " and absolutely nothing happens! This is what I learned from going to the API Scripts page ... why doesn't it work? Why are we worried about putting charactermancer buttons on the character sheets when the API is malfunctioning/ uninformative? I'm a little miffed, and more than baffled.