[BUG] Compatibility with Automated Evocations

[Nysterian]

Description
I'm not sure if the incompatibility is with Automated Evocations or one of it's dependencies like Warp Gate, but since Automated Evocations isn't trying to modify DnD5e rolls, I thought I'd try to ask if it's possible to try to make these modules compatible.

The incompatibility happens when trying to use Automated Evocations' feature of creating a token after casting a spell, which runs a macro that detects the level of the spell, and alters the created token's attack to scale appropriately with the spell level.

Currently, with no modules installed other than Automated Evocations and it's dependencies, it works perfectly fine, as soon as RSR is added, it stops working, the console logs the spell level as 0. I'm assuming that the way that RSR changes the rolls is stopping the other module from detecting the spell level.

Steps to Reproduce

1. Activate both RSR and Automated Evocations
2. Go to the Compendiums and import all the actors and macros from Automated Evocations
3. Find the imported actor for Flaming Sphere, edit the Prototype Token and make sure that the image used for the appearance exists (currently, those links are broken)
4. Create a new test actor and give it the "Flaming Sphere" spell, upcast it to 7th level.
5. Log into a player account and cast the spell, a new window should appear.
6. Click on the image of the only choice there, then place the Template somewhere.
7. Double-click the token that appears, and check it's only attack.
8. The description should say that it deals 7d6 damage, and the damage fields should change themselves to 7d6 as well, but they currently stay as 2d6

Versions

• Module: [2.1.2]
• dnd5e: [2.2.2]
• Foundry: [11.306]

Other Modules
Automated Evocations
Sequencer
socketlib
Warp Gate

[MangoFVTT]

@Nysterian As of versions 3.0.0+, RSR no longer changes the spell level itself and instead depends on base system function. Can you confirm if this incompatibility still exists on these latest versions?

[Nysterian]

Indeed, the latest update seems to have fixed this issue. Thanks!

Edit: Celebrated a bit too soon, I updated the module, tried it out and it seemed to work, but I didn't realize that RSR was simply not on, since my D&D version is not currently 3.0

I sadly cannot test this for a while, since I have some modules that aren't working with 3.0 yet, so my D&D version will have to stay at 2.4.1 for a while