RogueRustRandoSpawns

RogueRust-powered random respawn system with biome weighting, topology/zone protection, cached spawn generation and compatibility hooks.

Version: 2.1.2
Author: RogueAssassin
Frameworks: Oxide / Carbon
Required extension: Oxide.Ext.RogueRust

Plugin source · Back to plugin catalogue

Recent Changes

Features

Optional integration

ZoneManager — used only when blocked zone IDs are configured.

Permissions

Commands

Configuration

Configuration file: config/RogueRustRandoSpawns.json

Generation Options

Setting Default Validation
Generation attempts 4000 minimum 100
Maximum slope (degrees) 45 0-89
Distance from buildings (metres) 18 >= 0
Map radius used for spawn generation 0.95 0.1-1.0
Vertical spawn offset 0.15 —
Ground probe height 8 minimum 1
Persist generated spawn cache true —
Minimum cached points before regeneration 250 minimum 1
Regenerate when a biome falls below this many points 10 minimum 0
Maximum nearby entities checked per candidate 64 minimum 8

Spawn Options

Default biome thresholds:

Biome Enabled Minimum online players
Arctic true 30
Tundra true 20
Arid true 10
Temperate true 1
Jungle true 1

Other defaults:

Data

Spawn cache key:

RogueRustRandoSpawns/spawn-cache

The cache stores world seed, world size, plugin version and per-biome vectors. A cache is rejected when it belongs to a different map seed/size. Legacy RogueRust/RogueRustRandoSpawns/spawn-cache is migrated.

Localization

lang/<language>/RogueRust/RogueRustRandoSpawns/messages.json

Developer API

Performance notes

Spawn generation occurs at initialization/regeneration rather than every respawn. Respawns select from cached biome lists and revalidate a limited number of candidates. Nearby entity checks are capped, depleted biomes trigger coalesced regeneration, and persistent caches avoid expensive regeneration on every restart.

Installation and updating

Install the latest RogueRust DLL, place RogueRustRandoSpawns.cs in the plugin directory, optionally install ZoneManager, then review biome/topology rules. Existing cache is automatically invalidated when the map seed/size changes.