Class Automation Series D&D 5e (2024) / 5.5e

Quote:

---

Originally Posted by bwatford

You can cut off the Rogue Automation from Savage Attacker in the Options for the game, which lets it play nice with this extension.

---

Thanks bwatford, I appreciate the information and I truly feel like a dumb a$$. Thanks!

Hi Dax Doomslayer, I'm happy that you and bwatford managed to solve the issue as fast as that! xD

Quote:

---

Originally Posted by Henix

What should I automate next?
Have your say on the next class or subclass release!

Hello everyone!

With the Fighter, Rogue, Barbarian, and Sorcerer automations now live and running smoothly, it's time to look ahead to the next project.

I initially prioritized those four specific classes simply because they are the ones my own players chose for our current campaign! But now that my table is fully automated, I want to turn it over to the community.

I want to hear directly from you: what are you currently playing at your tables, and what do you need automated the most?

Let me know what you want to see:
You can request either of the following:

• A New Base Class: Tell me which of the remaining core 5.5e (2024) classes you want me to tackle next.
• A Subclass/Subclasses: If you want a subclass for a base class that is already published (Fighter, Rogue, Barbarian, or Sorcerer), let me know which one! If you want a subclass for a base class that hasn't been automated yet, feel free to request it and I will evaluate it on a case-by-case basis!

Just drop a reply in this thread with your vote or request. I will use your feedback to decide what gets priority in my free time development schedule.*

Thank you all for the amazing support so far! ✨

---

Would love to see classes completed before any subclasses, and for these completed next (in this order): Warlock, Cleric, and Wizard

Maybe set-up a poll somewhere so that people can vote and you know more of what ppl think as some may not care which class comes next, just that the class gets completed. And then I would suggest doing the same for sub-classes or even classes from other popular modules (i.e. Illrigger or Valkyrie just as examples -- Grim Hollow's player guide is coming out soon as well)

Thank you all for the fantastic feedback!

I completely agree with the general consensus here: it makes perfect sense to focus on finishing all the base classes first before we dive into specific subclasses or third-party content. Let's get the core foundation fully automated for everyone!

Also, great suggestion, SmackDaddy! Setting up a poll is a fantastic idea and will make it much easier to track what the community wants most.

I will go ahead and create a poll featuring the remaining 2024 base classes so everyone can easily cast their vote. Keep an eye out for it, and let's see which class takes the top priority spot for the next release!

I use Rogue automation and if I use an effect for ADVATK for my Steady Aim I don't get the pop-up window for Sneak Attack. Could you fix that? If I click on the Advantage button it works.

Quote:

---

Originally Posted by Zardoz4

I use Rogue automation and if I use an effect for ADVATK for my Steady Aim I don't get the pop-up window for Sneak Attack. Could you fix that? If I click on the Advantage button it works.

---

Hi Zardoz4!

I have just tried to replicate this issue on my end, but the Sneak Attack pop-up does correctly appear for me when my Rogue has the `ADVATK` effect applied.

Could you check if you are trying to do this multiple times on the exact same turn? The extension is built to respect the core rules, meaning the Sneak Attack pop-up will only appear once per turn. If you have already used Sneak Attack (so the pop-up has already triggered) during that specific turn in the Combat Tracker, it will not prompt again until the turn order changes or advances.

Try advancing the Combat Tracker to a new round/turn and see if the pop-up triggers for you with the effect active. Let me know if that solves the issue!

We just ended the session a couple of minutes ago and I am using it as a player. I'll tell you next Sunday. Thank you for the reply.