warpgate VS midi-qol

warpgate - Warp Gate is a system-agnostic library module for Foundry VTT that provides a growing number of API functions to make programmatically spawning tokens and modifying those tokens easier for players and GMs alike. Usable both directly via client Macros and as a dependency for other modules to build and expand upon.

Yup. Warp gate can do this with some item macro magic. https://github.com/trioderegion/warpgate … this would involve mutations, just FYI.

Warp Gate - This is a set of functions that greatly reduce the amount of code needed to do something.

Sounds like Warpgate could be the module to use for this, see https://github.com/trioderegion/warpgate/wiki/Mutating-Goblin for a possible example of how to do what you're after.

Warp Gate

Here's a link to the warpgate code for Dancing Lights.

midi-qol - Midi-qol is a module designed to help automate various parts of your game, specifically rolling attacks/casting spells and applying damage/effects. It has LOTS of configuration options which can be daunting.

Midi QOL - Unparalleled automation ability. Still useful even without all the automation options; I use it for its merged roll cards, for indicating that enemy tokens are dead, and for expediting rolls to not require a dialog prompt each time. Very complex.

Also, the change log from midi-qol today gives me a little hope something might be coming there: https://gitlab.com/tposney/midi-qol/-/blob/v10/Changelog.md

Probably also report the issue: https://gitlab.com/tposney/midi-qol/-/issues

Module which is causing the problem identified. Midi-QOL is the problem. Make sure you thumbs up the issue on https://gitlab.com/tposney/midi-qol/-/issues/973

MidiQOL - This does most of the automation heavy lifting.

MIDI QOL has hot keys for aspects like advantage/disadvantage and is likely able to be setup in such a way as to reduce the number of button presses required (auto roll attack and damage + a lot of the targeting automation may be something your player finds improves the game's accessibility significantly).

I agree that, as far as I can see, this isn't possible unfortunately. However it seems Midi does offer that under the optional Reactions settings so it seems possible. I would suggest putting in a new Feature request on their Gitlab repo HERE