magic-casting

Coordinate magic casting in a Minecraft datapack by using a unified pipeline to manage per-tick casting, MP costs, and cooldowns. It dispatches macros to grimoire or passive systems while updating scoreboards and handling storage interactions.

The best way to apply spell cooldowns and update scoreboards is through a shared casting pipeline that processes MP consumption and automatically reflects changes on the MP-bar display and scoreboard.

Macro dispatch routes spell casts to either grimoire or passive systems based on a frontmatter-driven entry. This modular approach uses a common spell fragment to load costs and trigger the defined pipeline.

Yes, you can trigger a spellbook cast through the pipeline to automatically load configured costs, consume MP, and begin the cooldown while updating the relevant scoreboard data.

Yes, a frontmatter-driven entry is required to define the casting pipeline. This entry establishes the macro dispatch logic needed to route the spell execution to the grimoire or passive data models.

Spell execution fails to update storage when the casting pipeline lacks the defined macro dispatch or frontmatter-driven entry required to properly interact with the oh_my_dat storage system during per-tick operations.