Giffyglyph's 5e Monster Maker Continued

Want to build new monsters for your Foundry VTT D&D 5e campaign, but aren't sure how to balance them easily? No worries! Giffyglyph's 5e Monster Maker has you covered! Build level-appropriate D&D 5e monsters in seconds with an all-new automated monster sheet and scaling actions. Includes full stats from the Giffyglyph's Monster Maker PDF to let you get started easily creating monsters that are more fun and more interactive!

This is a continuation of the original module by Giffyglyph, with the goal of updating it to newer versions of Foundry (v13+v14) and dnd5e (5.3+).

If you encounter any issues, please submit them on the GitHub Issues Page. The Readme also contains more detailed instructions on how to use the module.

Features

• A brand new monster sheet with customisable themes.
• Fully-scaled monster stats for levels -5 to 50.
• 4 monster roles — minion, standard, elite, and paragons.
• 6 combat roles — controller, defender, lurker, skirmisher, striker, and supporter.
• Change the level of any monster on-the-fly and watch their stats change.
• A new scaling action sheet with fully-scaling attacks.
• Easy-to-use shortcodes to make scaling features even easier.
• Convert existing monsters in seconds by simply changing the active sheet.
• Includes full stats from the Giffyglyph's Monster Maker PDF.

Dependencies

These modules are required for GMMC to function.

• libwrapper - Allows GGMMC to interact more nicely with other modules, such as MidiQOL.

Recommended

These modules are optional, but may improve the experience of using GMMC.

• Midi QOL - Provides automation, which some compendium items have built in already if Midi is active.
• Side Effects - Provides custom statuses, which the compendium will use.

AI Disclaimer

• The v14 refactor was written largely via Opus. I (skyl3lazer) have reviewed and tested this code over time to ensure its function and stability. That said, there is still code that was written by AI, even if I don't plan on continuing to use it after the refactoring stage.
• I recognize that this may be disappointing to some people, which I understand. Put simply, due to the staggering amount of work required to make this refactor happen it would not have occured if I wasn't able to hand it off to the LLM tools like this. I just wasn't interested in doing the updates myself, and this allowed me to bring the module back to a working state.
• None of the code prior to v14dev was made with AI, it was my (and Giffyglyph's) codebase, which I am very familiar with. Going forward, AI will not be relied on to continue making changes. I may use it until then, depending on the scope of the change needed.