foundryvtt-drag-ruler VS midi-qol

foundryvtt-drag-ruler - his module shows a ruler when you drag a token or measurement template to inform you how far you've dragged it from its start point. Additionally, if you're using a grid, the spaces the token will travel though will be colored depending on your tokens speed. By default, three colors are being used: green for spaces that your token can reach by walking normally are colored green, spaces that can only be reached by dashing will be colored yellow and spaces that cannot be reached with the token's speed will be colored red. If you're using a gridless map the ruler color will change to convey this information.

Drag Ruler v1.13.2 Bugs URL

Drag Ruler: https://github.com/manuelVo/foundryvtt-drag-ruler (requires socketlib)

Drag Ruler - Allows tokens to display a ruler indicating how much they are about to move. Can create waypoints to make a token move between multiple destination points.

I've just released Drag Ruler v1.13.0, which is the first official Drag Ruler version to support Foundry v10. A lot of code had to be changed for this release, so it's quite possible that some bugs have crept in that weren't present in Drag Ruler v1.12. If you find anything, please report it in the Drag Ruler bug tracker.

The module uses Drag Ruler iirc as it's source of measurement. Drag Ruler does not work with V10. There is an interim update (not released by the Drag Ruler author) but not sure if it works with ETL

Drag Ruler: Ruler display on movement

Drag Ruler

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