Iron's Spells: Incantation

Cast errors now name the mod responsible

If another mod hooks Iron's Spells' cast path and throws, you used to get Cast Error: InvocationTargetException — an error from Incantation, naming nothing useful. Every cast goes through reflection, so the real exception arrived wrapped.

Incantation now works out which mod the failure actually came from and says so: Cast blocked by (mod) — mod conflict, with the full detail in the log.

The known case is Iron's Restrictions. Its mixin on AbstractSpell.canBeCastedBy(...) reads a data attachment and your Curios slots; when that chain fails, the cast fails. It is a conflict between that mod and Iron's Spells rather than anything Incantation does, and it affects any cast that reaches the hook. Removing or reconfiguring Iron's Restrictions resolves it.

Also fixed in 0.9.4, if you are coming from 0.9.3 or earlier

Dedicated servers no longer crash on startup. The config-screen registration sat in the mod constructor, where its reference to a client-only class was resolved before the Dist.CLIENT check guarding it could run. 0.9.0 and 0.9.3 both crash dedicated servers, so if your pack ships either, please update.

Spell indexing works on dedicated servers. It read client-only config and silently indexed nothing.

You can cast the same spell twice in a row. The duplicate-suppression window re-armed itself on every blocked repeat, so with an open mic it never lapsed and the only way to recast was to say a different spell first.

The server crash shipped twice because the project had no dedicated-server run configuration, so every release was tested on a client where that code path is fine by definition. That test now exists and every release is checked against it.

Thanks to Shadower007, Tubeess, eli_zeele, bayratbill, xxshadow007, PhsycoPhink and Kogyuu for the reports and diagnosis.