5E - AoE Spells Auto-Targeting & Upcast (FREE BETA)

[nephranka]

That's one of those things I don't think needs "automating": it doesn't happen in combat, so you just need the DM to tell you "after 10 minutes of ritual, you cast the spell. Click alt and the spell you need". Done, wham bam thank you ma'am.

I was thinking more of just a note like the free casting

[Henix]

In addition to using "alt" to cast for free, maybe have an option for ritual casting. It is free as well but increases the casting time by 10mins.

I was actually just about to reply and ask what exactly you meant by ritual automation. If it is just a visual note (like the FREE tag) or a simple reminder string, I could technically add a small checkbox like "R" for Ritual in the popup window.

However, I do need to evaluate this carefully. As LoZeno mentioned, since rituals don't typically happen under the pressure of active combat, I want to make sure I don't clutter the popup interface with extra buttons for no major mechanical reason.

I'll write this down and keep it in mind as I refine the UI! Thanks for the discussion, everyone.

[bwatford]

One thing I noticed with AoE targeting.

The 50% Rule: According to the official 5e Dungeon Master's Guide, if an AoE (like a Fireball or Spirit Guardians) covers at least half of a creatures square, the creature inside it is hit.

The targeting for this extension is triggering if it touches any of the square/token from what I can see.

[Lo Zeno]

I'm really loving this extension so far, but the time it takes to launch a campaign when it's enabled is really way too long.
Is there a chance that whatever initialization you do for the extension can be split, maybe having the bare minimum done at load time and the remaining parts during the game? e.g. the first time a character sheet is opened, or the first time an Actions tab is selected, or the first time a spell is used, something like that?

[bwatford]

From looking at it in the vault, this one is loading a literal ton of graphics files that is causing the slow initialize.

[Henix]

Thank you all for the feedback and observations, here are some updates on those points:

One thing I noticed with AoE targeting.

The 50% Rule: According to the official 5e Dungeon Master's Guide, if an AoE (like a Fireball or Spirit Guardians) covers at least half of a creatures square, the creature inside it is hit.

The targeting for this extension is triggering if it touches any of the square/token from what I can see.

Regarding the 50% Rule for AoE Targeting:
From my understanding of the grid rules, the 50% coverage applies to the individual grid squares themselves rather than the total size of the creature's token.
The 50% coverage rule applies to an individual grid square, not the creature's entire token area. If a spell’s AoE covers at least half of a 5x5 grid square, that specific square is considered fully within the effect.

Right now, the most reliable technical method the extension uses to determine this is checking if the AoE template covers the exact center of a grid square (which represents that 50% threshold). If it touches the center point of any square that a creature occupies, it counts as a hit.

I'm really loving this extension so far, but the time it takes to launch a campaign when it's enabled is really way too long.
Is there a chance that whatever initialization you do for the extension can be split, maybe having the bare minimum done at load time and the remaining parts during the game? e.g. the first time a character sheet is opened, or the first time an Actions tab is selected, or the first time a spell is used, something like that?

From looking at it in the vault, this one is loading a literal ton of graphics files that is causing the slow initialize.

Regarding the Campaign Load Times & Graphics:
It is completely true that the extension loads a literal ton of graphics files, which is exactly what is causing that heavy initialization lag.

I am still brainstorming the best architectural way to completely optimize this initialization process so it doesn't slow down the initial boot sequence. However, I have just pushed an optimization update to the Forge that should drastically improve things for now, it should reduce the current loading time by about 2/3.

Please grab the latest update and let me know if the campaign startup feels significantly faster on your end!

[nephranka]

Thank you for the excellent feedback! You are completely right, I hadn't fully accounted for the multiclassing dynamics with Pact Magic yet.

To solve this, I just thought (right now xD) of implementing an option for multiclass characters, likely a checkbox or a toggle button in the interface that lets you switch the active "Pool" (Regular vs. Pact). This way, you can easily choose exactly which type of spell slot you want to consume before triggering the cast. What do you think?




Thank you so much for the kind words! I am incredibly happy to hear that you liked the showcase video and the extension.

Please let me know how it goes at your table! I’d love to hear your feedback after your group tries it out in a live game.




Thank you so much, I'm really happy to hear that! And yes, your assumption is exactly correct.

Because of the unique rolling conditions required for the Chromatic Orb bounce mechanic, there is no built-in automation for it. The best workflow right now is to simply leave the automation popup open, check your damage roll to see if you got matching numbers, and then manually roll the attack and damage again for the new target within 30 feet if it bounces.

I see the note about pact slots but I don't see a way to indicate which to use? Is the intent to just have a note or is there a setting somewhere?

Also, loads are much better now.

[Henix]

I see the note about pact slots but I don't see a way to indicate which to use? Is the intent to just have a note or is there a setting somewhere?

Also, loads are much better now.

Glad to hear that the load times are feeling much better on your end! Thank you for the update on that.

Regarding the Pact Magic slot selection, that feature is actually not present in the current build yet (that is a bug that occur when a PC have both Pact slot and normal one). I am still actively working on it and other features.

[nephranka]

Glad to hear that the load times are feeling much better on your end! Thank you for the update on that.

Regarding the Pact Magic slot selection, that feature is actually not present in the current build yet (that is a bug that occur when a PC have both Pact slot and normal one). I am still actively working on it and other features.

Thanks for the clarification.

[Lo Zeno]

Can confirm, load times are an order of magnitude shorter now
I'm testing it with one of my players together with the new Sorcerer automation, everything looks great so far