Builder's Manual · Chapter 5

Monsters And Encounters

Fights in MEMS are sized before dice fly. The encounter system measures a monster's danger in threat points, measures the party's strength in a live budget computed from their sheets, and compares the two on five bands — with a hard rule that keeps the power fantasy honest. This chapter is the builder's guide to that machine: how to stat a creature so its numbers mean what you intend.

The monster sheet

Monsters are statted on the Monster sheet — a mirror of the player sheet with the human limits removed:

  • Health is a plain editable field — whatever the creature demands. The rule of thumb: the more physically tough a creature seems, the higher its health.
  • Skills have no caps and may go negative — an ancient thing can sling a 25, and a sun sprite's Stealth is −10 because a tiny sun does not sneak.
  • Creature features come built-in — soul features humans cannot acquire without the Soul Shape feature (mist form, vampiric attack, uncontrolled storage). There is no fixed master list; it accumulates as the bestiary fills in. Folklore is the rule of thumb for sourcing, not a boundary.
  • Creature spells break the rules of spell creation — a creature does not build spells with modifiers; its nature simply has them, including natural attacks with no point cost. Take them as written.
  • Pools can start above player maximums (technically capped at 100 like anyone, but a beast may begin at 100), and pools can be gauges: a chupacabra's Blood bar is a hunger meter, and an elemental's thirteen bars are living — whichever is fullest is its primary, shifting its resistances and weaknesses mid-fight.
  • Energy tags ride on the sheet: i immune, R resistant (half), w weak (double), RW resist-or-weak per the creature's primary element.

Because the sheet mirrors the player sheet, the combat pipeline treats creatures and people identically — wards absorb first, then resistance or weakness applies, and a spell strikes as its own energy mix, so a creature weak to either of a two-energy spell's types takes the double on the whole thing.

Threat: the monster's side

Threat is a computed field — fill in the sheet and it calculates. It sums:

ComponentValue
Durabilityhalf the monster's health
Prowessits best combat skill × 2
Reservestotal pool maxima ÷ 10
Arsenal2 per spell, 3 per ritual
Threat Adjustthe GM's written adjustment

Threat Adjust prices what the numbers hide: +2 to +5 for each spell that deals more than 5 damage per hit, hits an area, disables or removes a fighter, or a rule-breaking soul feature or ritual; −2 to −5 for a readily exploitable weakness the party can hit. Use it honestly — it is the only place the GM's judgment enters the number.

The party budget: the players' side

Computed live from the sheets of everyone actually fighting, so it grows as they spend:

  • Practitioner: best attack skill × 2 + max health + wards + total pool maxima ÷ 10 (the caps, not the current fill — the budget must not dip because the party spent itself last fight).
  • Regular human: best attack skill + max health — their baseline bars count for nothing.

Sum the fighters. Recompute whenever the roster changes or after a growth spend. There is no separate action-economy rule: everyone takes two actions per round, so a larger side simply gets more turns, and the raw threat totals already count bodies fairly.

The bands and the hard rule

BandThreat ÷ budgetMeaning
Trivial10% or lessA warm-up; no real resource concern.
Fair11–25%The expected fight; wins on normal resource use.
Hard26–40%Someone may drop; wards, healing, and cover matter.
Push Your Luck41–70%Possible, but someone may die; needs a plan or an exploited weakness.
Don'tabove 70%Not a fight — run, parley, or siege.

The Hard Rule: never begin or steer the story into an encounter above Push Your Luck unless the players deliberately sought that danger — and even then, warn them in one line before dice fly. A fight the story forces must land Trivial to Hard; if the story demands something bigger, it is not a fight yet — it is a chase, a negotiation, a ritual to interrupt, or a siege. State the band in one line when a fight starts; knowing the odds is part of the fantasy.

Stating a new creature

  1. Give it the stats that feel right — there is no point budget for creatures; research and intent are the template.
  2. Set health by toughness, skills by nature (negative is legal and expressive), pools by scale, and spells by what its nature simply has.
  3. Add creature features for whatever its nature demands, and price the invisible ones with Threat Adjust.
  4. Check the computed Threat against your party's budget and land the creature where the story needs it — or write it as the siege, the negotiation, or the thing that hunts rather than fights.

For calibration, the worked example in the Encounters lore note is the shape to copy: a health-8 creature with one best skill of 10 and two spells computes to Threat 51, which ran Fair against a seven-practitioner party of ≈ 250 — exactly as intended.

One more bridge worth carrying: magical items are how casters answer creatures with no caps — a Savant at Spell Slinging 15 with a +5 robe and a +5 hat slings 25. Items stack by kind (one robe, one hat), each kind needs its own blueprint, and a blueprint in hand is a supply line. When your bestiary outgrows the party, this is the intended answer — not a raising of the skill caps.

Manual updated Nov 22, 2026.