R.E.P.O.R.E.P.O.wiki
Community reference picture of the Rugrat: a small wide-eyed monster with a nappy.
Illustrative community picture showing One of the monsters a run may or may not contain from R.E.P.O. Fandom Wiki (repo-2025horror), CC-BY-SA-4.0 (license), by CritHaxXoG. It has been re-encoded for this page. It is not a screenshot taken by this site.

How the game behaves · R.E.P.O. v0.4.0 · read from a local copy

What decides whether a monster appears

An enemy set-up holds a list of things to spawn.

Which monsters a run can meet in R.E.P.O. is set up rather than left to chance: an enemy set-up holds a list of things to spawn, a condition on how many levels have been completed with a lowest and a highest, a rarity preset, and how many runs have been played.

What the game establishes

In play

Not every monster is waiting behind every door. The game has a set-up of its own that decides what a run may contain, which is why the deeper levels are not simply the same level with more enemies in it.

It holds a list of things to spawn. That list is what the level draws from, so what can appear is a set rather than whatever the level happens to contain.

It can be gated by progress. There is a condition on how many levels have been completed, with a lowest and a highest value, so one set-up can be held back until a crew has got far enough and another can stop appearing once they are past it.

It carries a rarity preset. That preset sits alongside the spawn list, which is how the same set of monsters can be made more or less common without the list being rewritten.

It also counts runs played. That is a separate measure from levels completed, which is why a set-up can be arranged around how much a crew has played rather than only how far they have got.

What this entry does not tell you: which monsters are in any set-up, what the level bounds are, or what a rarity preset changes. We have not verified those numbers, so we do not print them.

Related

Version and sources

A local copy of the game, read only. The grounding for each fact is listed on the technical reference pages; nothing here is estimated. Documented build: 0.4.0.