foundryvtt-forien-quest-log VS midi-qol

foundryvtt-forien-quest-log - This module provides comprehensive Quest Log system for players and Game Masters to use with Foundry VTT.

I found the scripts here.

The new version is here: https://github.com/League-of-Foundry-Developers/foundryvtt-forien-quest-log

If you have an enhancement idea or found a bug / problem with FQL please post an issue on the issues forum: https://github.com/League-of-Foundry-Developers/foundryvtt-forien-quest-log

I appreciate the feedback. I already implemented one of the suggestions (extra state buttons for completed / failed quests) and looking into a context menu option for the quest tracker!

There is a public API available now. You'll want to take a look at [QuestDBShim](https://github.com/League-of-Foundry-Developers/foundryvtt-forien-quest-log/blob/master/src/control/public/QuestDBShim.js).

Here you go.

I asked them to improve the module: https://github.com/League-of-Foundry-Developers/foundryvtt-forien-quest-log/issues/59

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