goblinscript

To evaluate game math formulas for damage and costs in DMHub, you compute GoblinScript expressions like '2d6 + Might' using built-in dice operators, symbol lookups, and local bindings to resolve creature and ability fields deterministically.

The best way to calculate custom prerequisites and target filtering for creatures is to evaluate GoblinScript expressions, applying string matching, comparisons, and symbol lookups to compute deterministic and non-deterministic filtering results.

You write dice roll expressions and lookup creature attributes by entering a GoblinScript formula such as '2d6 + Might', combining built-in dice operators with local bindings to resolve specific creature and ability fields.

Yes, you can use GoblinScript formulas for custom attribute evaluation alongside Lua integration within DMHub, applying its domain-specific syntax to compute numbers for damage, costs, and filters.

Yes, DMHub supports non-deterministic results when evaluating custom attribute formulas, allowing GoblinScript to compute variable outcomes like dice rolls alongside deterministic calculations for prerequisites and costs.

You should use GoblinScript expressions instead of standard Lua scripts when you need a readable domain-specific language for defining game math, enabling designers to express damage, costs, and target filters with built-in operators and symbol lookups.