fvtt-find-the-culprit VS macros

the module "find the culprit" helps a lot as it automate the module enable/disable and make it faster till you find the module that's misbehaving.

the module "find the culprit" can help you pinpoint exactly which module was misbehaving if you want to check.

Find the culprit: Helps to track down module conflicts

Find the culprit (absolutely necessary when working with so many modules)

GitHub - Moerill/fvtt-find-the-culprit

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