Overview: What QR Is, and Why You Need It
Previous: Home · Next: Installation
One-sentence positioning
QinhRuins (QR) is a procedural engine that turns "structures" into "gameplay that lives in the world": you give it a building (a schematic / NBT), and it makes that building emerge naturally in the right place, blend into the terrain, and get fitted with monsters / mechanisms / chests / objectives. Players walk up and can explore it, and once cleared they can use a keystone to upgrade it into an ever-escalating realm.
QR deliberately does not do dungeons — it doesn't pull players into a separate world, doesn't start a countdown, and doesn't do "enter / exit instance." The ruins grow right inside your main world and are part of the terrain.
Remember the positioning in one line: other dungeon plugins send the player into a structure; QR plants the structure into the world.
🖼️ [Image placeholder] A comparison image: left "traditional dungeon = separate room + countdown," right "QR = a ruin growing in a valley" · suggested assets/overview-vs-dungeon.png
What problem it solves
You have a beautiful building (built yourself / downloaded as a schematic) and you want it to:
- appear randomly and rarely across the world as players explore, instead of placing them one by one manually;
- fit the terrain — not a platform floating out of nowhere on a hillside, but with a foundation, edge feathering, and half-buried into the mountain;
- have monsters that activate, chests each person opens independently, mechanisms you can step on and trigger, and clear objectives;
- be recycled after clearing — fading over time so the world keeps growing new content;
- and let veterans farm it repeatedly — infuse the same ruin with "tiers + affixes," getting harder and richer the more you push.
QR handles all of this, and the server owner doesn't have to write code, while players don't have to memorize a pile of commands (the core experience is "you bump into a ruin while wandering").
The four-step lifecycle — the life of a ruin
Understand these four steps and you understand the whole picture of QR:
| Stage | What happens | Who drives it |
|---|---|---|
| ① Generation | Pick a site somewhere in the world, paste the structure in, blend it with the terrain | The Generation Director runs a lottery by weight / density / filters |
| ② Exploration | Player approaches → monsters activate, mechanisms stand ready, chests can be opened, objectives count | Anchor activation + the blueprint gameplay layer |
| ③ Clearing | Complete the staged kill objectives → unlock rewards, hand out clear loot | The objective tracker + the loot system |
| ④ Fading / Ascension | A cleared ruin is snapshot-restored over time, freeing its slot; or it's infused with affixes by a keystone and ascends into a realm to be farmed repeatedly | Regen / the realm system |
🖼️ [Image placeholder] A four-stage cycle diagram (generation → exploration → clearing → fading/realm, with an arrow looping back to generation) · suggested
assets/overview-lifecycle.png
The whole cycle lets the world renew itself: old ruins fade, new ruins emerge, and players always have something new to explore.
What it can do — typical scenarios
These are all gameplay patterns QR can orchestrate out of the box:
- Random wilderness towers — one tower template, paired with
generation.profile: surface_overworld+ a weight, and players rarely stumble upon it while exploring. - Half-buried desert tombs — use "bedrock marker blocks" to let the dunes show through from inside the structure, creating an entrance genuinely buried under the sand.
- Staged clear-out dungeon-style ruins — write "stage 1 clear the outpost → stage 2 defeat the boss" in the blueprint; only a full clear counts as a completion and unlocks the grand reward chest.
- Step on a mechanism to open a door / summon an ambush — a redstone trigger + a
FILLaction fills the door into air; a region trigger + aSPAWNaction spawns an ambush as you enter. - Chests each person opens independently — container loot with
per-player-once, so each player gets their own share on first open, preserving the sense of mystery. - Tier realm endgame — clearing drops a keystone → right-click the ruin core to activate a T5 realm (no healing + time limit + monster waves) → purge for exclusive loot + a higher-tier keystone.
- Find ruins with a guide compass — a player right-clicks a guide item → a compass HUD points to the nearest ruin of that kind, consumed on arrival.
- Sky islands / underwater shipwrecks / nether fortresses — 17 built-in placement profiles cover surface / underground / sky / sea surface / seabed × Overworld / Nether / End.
Behind every scenario is the same sentence: you provide the structure and the rules, QR makes it come alive in the world.
Its place in the Qinhuai ecosystem
QR is the "world content engine" of the Qinhuai RPG ecosystem. It itself computes no attributes and settles no damage — this red line is consistent with its sibling modules:
| Module | Role | Relationship to QR |
|---|---|---|
| QinhCoreLib (QCL) | Unified base library (item parsing / database / economy / i18n / scripting) | QR hard-depends on it; without it, QR does not enable |
| MythicMobs (MM) | Monster engine | QR's first choice for spawning monsters (mm-mobname); without it, it degrades to vanilla entities |
| QinhItems / NeigeItems / MMOItems… | Item sources | The item: references for loot / keystones / guide items are resolved by QCL to any item source |
| QinhClass / MMOCore | Class / growth source | Entry requirements and loot growth scaling read from it; without it, a built-in fallback is used |
| AttributePlus, etc. | Attributes / damage | QR doesn't touch it; making "monsters stronger" via affixes is delegated to MM by raising the level, not QR changing stats |
🖼️ [Image placeholder] Qinhuai ecosystem module relationship diagram (QCL base · QR world content · MM monsters · QI items · QC classes) · suggested
assets/ecosystem-diagram.png
Note the difference between "hard dependency" and "soft dependency": QCL must be installed first, or QR simply won't enable; the rest (MM / item plugins / class plugins / economy / Citizens / PlaceholderAPI) are soft dependencies — it'll still start without them, the corresponding capabilities just degrade. See the degradation table on the next page, Installation.
Keep reading
- Ready to install the plugin → Installation
- In a hurry to build your first naturally-generating ruin → Quick Start
- Want to fully grasp the architecture first → Core Concepts