Sure, here's the link - <a href="https://pastebin.com/D9mDuDq4" rel="nofollow">https://pastebin.com/D9mDuDq4</a> Instructions are at the top, it'll change the NPC sheets to use a '*' instead of 'd' in the critical rolls. This means it doesn't need to do any further work once you've run it, unless you add more NPCs - you can probably disable it unless you're planning on adding new NPC sheets. Once you've added it as an API script, it can be run (by GM only, let me know if you need that changed) in a few ways - on selected tokens, the page the GM is currently on, or globally (entire campaign). I'd definitely advise running it on selected tokens first, or create a new map page and drag a few monsters onto it to test. Then run it with either target=sel or target=page, depending on which option you went for: !brutalbot target=sel,mode=chat,brutal This should apply changes to the currently selected tokens, and output to chat. Check the character sheets & click some attacks to check that the math is what you're expecting. Hopefully I understood correctly. For testing - edit an NPC action, click in their To Hit field for example '7'. Change it to this: 7 + 1d0cs0 That'll give you 100% crits... just remember to change it back after you're done spamming crits. Also, if you're happy with it and are planning on doing bulk changes, you may want to toggle the response logging back to API console, so your chat log isn't getting spammed, with mode=log. It's a toggle, once you change it, it should (hopefully) stay changed until you change it again. You could even go for mode=silent, as the script is very spammy - apologies for that, but I was learning as I went and needed the constant feedback :) Let me know if I got anything wrong, or it doesn't work. If you're comfortable with the results, you should be fine to do a page at a time. The worst damage this script should be able to do is mess up the NPC action description field or crash the API sandbox. It doesn't edit anything on PC sheets, and it has a revert setting to undo the changes it makes. Having said that, I'm an absolute novice at JS - make sure your game is backed up first! If everything works fine and you add new monsters, you should be fine to run it globally to easily modify the new NPC sheets. !brutalbot target=global,brutalise Basically, the script will ignore any NPC sheets where it finds the text "crit1=" in the description field, as it shouldn't be in there unless the script (or someone else) is already using a similar hack to override the roll template's crit field. If you're in game at the time, I'd recommend changing the logging mode back to API console log only with mode=log, your players probably don't need to be seeing brutalBot's excessive chat spam. :) How it works, if you're interested, and why it doesn't just change the {crit} field: The new math is stored in the @{repeating_action_$0_attack_crit|max} repeating Attribute, which is unused by the sheet and only exists because all Attributes are created with a 'max' key, whether or not they need it. Changing the actual @{crit} Attribute is no good - there's a sheetworker which fires every time an attack is rolled and changes it right back to the default. The math is called with an override hack, appended to the @{repeating_npcaction_$0_description} field. This looks a little ugly on the character sheet, but it doesn't affect the actual roll template description output. You may still get the 3d dice rolling for the crits - there's not much I can do about that, due to the sheetworker mentioned above. The script defaults to 10 loops through the repeating_npcaction section. Change that if you have monsters with more actions, with the argument loop=X. From memory, there are some Compendium sheets with bogus entries in the middle, so if I'd made the loop break when it first finds an empty row, it probably would have missed actions on those sheets. I've tested it on a bunch of mobs that have different attacks, like the dragon with twin damage types, and the Lich who loves breaking npcaction macros. But there might be some odd attacks with weird roll expression where the script gets confused or the attack no longer works. Revert the changes on the sheet and let me know if this is the case. Click for GIF: