macros VS dae

Yeah, learning how to do other stuff in Javascript is a good way to start. But then maybe look at things like the example scripts in the community macros: https://github.com/foundry-vtt-community/macros

Have a look at the community free macro module. https://github.com/foundry-vtt-community/macros

If you code at all, then Foundry jumps even higher up the recommendation list since it's designed intentionally to allow people to build stuff and add functionality. As someone who used to mess with R20 macros and their proprietary API, this is probably one of my favorite benefits to Foundry. They have some typical documentation though if you prefer examples the community macros repo is great for that.

Read some of the shorter/simpler macros from https://github.com/foundry-vtt-community/macros to get a sense of how they work.

This macro in the FoundryVTT Community Macros GitHub repository "selects all actors of the same name on the scene." I haven't tested it, but these macros have never given me issues in the past, and I recommend checking out that repo if there's ever something you're looking for.

Quick size control (#2) is generally handled by macros. There's a macro for quickly swapping tokens between 1x1 and 2x2 in the community macros. If you want some that will just bump a token up or down 1 grid size, I can get you mine personal ones in a bit when I'm at my main computer/

buttonpushertv

Try this one: https://github.com/foundry-vtt-community/macros/blob/4e25a66ef7990dbcb0c9015b554286de147c5116/actor/5e_lay_on_hands.js

By using the Dynamic Active Effects and Active Token Effects modules, you can achieve this (pictures).

DAE - This module modifies how active effects behave over and above what is supported in core. An active effect allows you to modify values on an actor (e.g. Strength). You can create effects directly on an actor or create them on an item and have them transfer to the actor when the item is added to the actor.

This definitely looks like a bug to me. I'd open an issue for it over on Tim's Gitlab for DAE

Dynamic Active Effects

These modules are almost entirely redundant in a game that uses tposney's Midi QOL and DAE. The top of the line module lineup for automating combat in dnd5e is absolutely dependent on these two. They are extremely powerful, versatile, and complex. I've used them in the past and would recommend them in a heartbeat for GMs who are interested in going down the rabbit hole of high-automation 5e games.

Bless can be added using Dynamic Active Effects and should be auto-configured within Dynamic Effects SRD (I believe there are also macros for this in FVTT Community Macros as well which allow you to toggle bless on/off)

Further to my previous comment, looking at the DAE documentation: