Autobuttons with new 2024 sheets

My players want to use the new 2024 sheets, but I cannot get it to work. Has anyone had any success with this?

AutoButtons relies on RollTemplates, which Beacon sheets don't use.  AutoButtons could be updated to parse the output from Beacon sheets, but that's something the original author (Oosh) or the community would likely need to pursue.

Autobuttons was written specifically for the D&D 5e (2014) Sheet. Since its input is keywords drawn from Chat, and its output changes values on token bars, it should be able to be re-written to work with the 2024 sheet even now. How much work that would be and how difficult it might be to implement in a dual sheet game, I don't know. I'll see if I can ping the author so he is aware of the request, at least.

Glad to see it is possible though, hopefully the author or someone will take it up. Does anyone even have a way of parsing the output from Beacon sheets yet? 

Consider me both pinged and poked. I'll try to make time for this on the weekend and see if I can get anywhere with it, though I haven't touched anything R20 related in a long time. Hopefully there's a way to update the script to be configurable by the user for any Beacon sheet... I'll update here once I've had a looksie.

https://gitlab.com/ooshp/autoButtons/-/blob/development/autoButtons.js?ref_type=heads

There's an experimental version here you can try, if you'd like.
You'll need to enable beacon support with

!autobuttons --beacon

Or just through the --settings menu

I've barely tested anything, so it could have issues - I'll have more time later in the weekend to look at it further, but thought you might want to try it out if you have a game this weekend.

The 2024 template only has a single damage total for each roll as far as I can tell, so 2024 roll buttons won't show anything crit related - if the roll was a crit, the normal damage button will apply that crit damage total.

I've never used the sheet, and only did some basic testing so let me know if it fails to work for anything.

The beacon support is additive with normal sheets - so if you're using dual sheets they should theoretically both trigger buttons.

I just played around with it and everything looks like it is working great! It is working for both 2014 and 2024 sheet rolls. You are the best, thank you! I run my games on Thursdays so I will see how it works through several sessions and different campaigns then, but again thank you again this is huge.

Haven't tried it yet, but based on this, thanks Oosh, for coming around to provide support on this excellent script!

Okies, I've merged an updated version:
https://gitlab.com/ooshp/autoButtons/-/blob/development/autoButtons.js

Squashed a few bugs, but mostly just updated styles which got embiggened at some point when R20 changed the site REM. The buttons and menus should be a more appropriate size.

In case anyone actually liked the inflated version, there's a new setting: --size (or --basesize). This defaults to 1.0 but can be set anywhere between 0.5 and 3.0. So you can have itty bitty buttons, or gigantic buttons. e.g:

!autobuttons --size 1.5

If you happen to have any custom buttons, they'll still have hard-coded font sizes saved in their config. You can set them to the new default styles with:

!autobut --editbutton {{name=myButton}} {{style=color: blue;}}

replacing "blue" with whatever color the button should be. Or just {{style=}} if the button should be the standard dark red.

Let me know if there's any issues remaining. I don't use R20 (or any VTT) any more, and I've only got passing knowledge of the 2024 changes - both core rules and Roll20's implementation. I also couldn't get spells to upcast their damage properly, but I'm running on the assumption that they'll still have the same total damage in the top right corner, so they should work fine.

@Keith - I remember you finding issues with the display on Mac due to OS-level font handling... I'd be interested to see if the new styles are any better, but won't be near a Mac for a few days.

Also, side note: there's nothing structural or semantic in the sheet's roll output that indicates what the roll is supposed to be. I've had to rely on a regex scan for damage type (e.g. Bludgeoning, Fire) appearing in the right place to determine if something is a damage roll. It's possible this might cause some false positives somewhere, since I haven't used the sheet extensively.

The only thing I could find in my testing was that anything with multiple damage rolls, like Eldritch Blast, will overlap the hearts in chat. Still usable though.

Hmmm, I can't reproduce this on either FF or Chrome. I did update some styles, are you using Stylus or something else to modify any Roll20 CSS by any chance? In your screenshot it does look like the timestamp at the top might be overlapping the avatar, which isn't how it's supposed to look.

Which browser/OS are you using? Try an incognito window and see if it makes a difference, and maybe also switching off timestamps/avatars in the R20 chat settings to see if that does anything. You can also try playing with the --bump setting (called 'slim buttons' in the settings menu)

FWIW it should look like this with timestamps off (and slightly spread out with timestamps on):

Also.... every time I cast EB with the 2024 sheet it's adding more beams. Cumulatively. By the end of a session this Warlock would probably be throwing 100 beams per attack. Is this normal??? Dropped straight from the compendium.

I am using Chrome and I haven't touched any styles. The --bump setting fixed everything. Timestamps and Avatars didn't seem to affect it at all. Everything seems to be working flawlessly now! Not sure why your Warlock is gaining beams though, definitely not normal. My player thankfully does not have that issue.

Once again, thank you so much for everything!

I used the script here https://gitlab.com/ooshp/autoButtons/-/blob/development/autoButtons.js and it was working great on a game with both 2014 and 2024 sheet. However a couple of days ago the output looks strange like so:

My friend is the GM so I can't actually check the settings but I'm pretty sure it hasn't been changed. We don't use image icon and we use the slim version. I'm guessing Roll20 pushed some kind of CSS change that broke this. Any quick ideas how to fix this? It's still usable but a bit annoying.

I hacked a fix for the problem above, maybe it's useful for others. I think the problem is the in the damage type regex / finder for Beacon, or how it interacts with the output styling. My coding skills is not enough to fix the actual issue, so I just removed damage type from the output entirely.

                if (damageType)
                // Hack to fix output error
                // name = `${name} ${damageType}`;
                name = `${name}`; 

'Fixed' output: