RealmControl

Realm Control provides visual administration for world blocks, structure and biome generation, beacon areas, and teleport authorization. Use it to shape a modpack's future terrain, configure beacon infrastructure, and give players controlled access to teleport commands.

Installation and access Current build target: Minecraft 1.20.1, Forge 47.4.2+, and KineticCore 26.9.20+. Install Realm Control and KineticCore on the client and server for multiplayer use. Optional: Jade 11.0.0+ for beacon information. Enter a world, press F6, and choose Realm Control in KineticCore. The key is configurable in Controls. Global server settings and world-generation editors require permission level 2. Individual beacon controls also enforce ownership where applicable. World block generation and replacement The World Blocks module has dedicated editors for generation bans, fixed replacement, and weighted replacement.

Generation bans: select exact blocks or create block-tag/mod rules to exclude matching blocks during generation. Fixed replacement: select one or more source blocks, click Done, and choose the final target block. Weighted replacement: select a source and several targets, then assign each target a positive weight. A target's share is its weight divided by the total. Replacement chance and target weight serve different purposes: chance decides whether replacement occurs, while weights select a target after a successful replacement roll. Use source/target groups and searches to manage duplicate ores or other generated blocks in a large modpack. For example, a weighted rule can replace a source with stone and deepslate at weights 3 and 1. Among successful replacements, their shares are 75% and 25%; these shares do not replace the rule's own replacement-chance setting.

Saved block rules affect subsequent generation. Existing terrain is handled only by the separate loaded-chunk replacement feature described below.

Optional one-time replacement in existing chunks Fixed and weighted replacement each have their own Loaded Chunks switch. Both default to off.

Enabling either switch takes effect only after a full game/server process restart. Saving or /kt reload cannot register or unregister this feature live. When enabled at startup, old chunks are queued when they load and processed at most one chunk per tick. Each chunk is marked after processing, separately for fixed and weighted replacement. Changing rules does not automatically rescan chunks already completed for that rule type. The operation uses block contents, not a record of whether a block was placed by a player. Matching blocks in existing builds can therefore also change. This feature does not regenerate structures or replace stored biomes in existing terrain. Use this switch when existing terrain should be migrated, and review source rules against the world before enabling it. With both switches off at startup, the chunk-scanning handlers and processing queue are not installed.

Structures The structure editor reads the active server registry and shows the generation parameters available for each structure.

Disable an individual structure or change its weight within a structure set. Change generation frequency and salt. For random-spread placement, adjust spacing, separation, and linear/triangular spread type. For concentric-ring placement, adjust distance, spread, and count. Restore startup defaults captured from the server registry. Use the editor's locate/teleport tools to inspect enabled structures; cross-dimension structures may require changing dimension first. Placement settings belong to a shared StructureSet. Editing or restoring them can affect sibling structures in the same set. Disabling one candidate does not automatically disable its siblings.

Save All, then reopen the world or restart the server to apply generation changes. They affect future chunks; they do not move, remove, or regenerate structures already present. Refreshing the registry list preserves unsaved local edits.

Biomes The biome editor supports replacing a biome, replacing biomes matched by a tag, removing matching climate entries, and restricting a rule to one dimension or all dimensions.

A source can be a biome ID or #biome_tag; a replacement uses a target biome ID. Rules can target a specific dimension, or * for all dimensions. Removal excludes the matching entries from biome selection rather than turning existing terrain into empty space. Implementation applies to MultiNoiseBiomeSource dimensions. It does not apply to every custom biome source or vanilla's distinct End biome source. If removal would eliminate every climate entry in a dimension, that result is rejected instead of leaving an empty biome source. Save biome rules and reload the world/restart the server. New generation uses the updated selection; already stored chunk biomes remain as generated.

For manual file editing, entries use dimension|source|target, for example minecraft:overworld|minecraft:desert|minecraft:plains. The target null means removal; the visual editor handles this format for you.

Beacon areas Open an active beacon's interface to configure its chunk-loading and spawn-prevention controls, then click Apply Settings.

Enable chunk loading and choose a radius within the beacon-level limit. Radius 0 covers 1×1 chunks; radius 1 covers 3×3. The local value -1 selects the current level's maximum. Set a separate spawn-prevention radius and target all entities, hostile entities, or passive entities. Leave interception codes empty to use global rules, or supply codes for specific spawn sources. Global lists allow or block selected entity IDs. Within an applicable protected area/target category, the allowlist is checked before the blocklist. Global and optional per-owner quotas count unique force-loaded chunks across dimensions. Offline settings control when an absent owner's beacon loses effects, chunk loading, or spawn prevention. Range rendering, quota information, and optional Jade details help inspect beacon coverage. Interception codes: A natural, B conversion, C command, D egg/bucket/dispenser, E spawner, F summoned, G event/reinforcement, H breeding. Without local codes or an entity-specific global rule, the default interception is natural spawning.

Generated defaults use level radii [0, 1, 2, 3], a global limit of 500 chunks, and an offline timeout of 4320 minutes. Per-player quotas are initially disabled. Timeout 0 is immediate; -1 disables the timeout. Saved interception rules update immediately; loaded beacon radius, quota, and offline state may need a beacon update or world reload.

Teleport authorization and commands The teleport module changes vanilla /tp and /teleport. FREE mode permits unrestricted player use; AUTHORIZED mode requires remaining uses or an unexpired timed grant. A master switch disables the modification. Authorized players subject to these limits can teleport themselves, not other entities.

Admin bypass normally exempts permission level 2+. If disabled, level 2 also needs authorization; levels 3 and 4 still bypass. A custom denial message supports & colors and {player}.

Command Purpose / access /kt world help Structure-command help /kt world structure Inspect structures at the player's position /kt world list-structures List registered structures; level 2 /kt tpd Check your own teleport authorization /kt tpd help Teleport-authorization help /kt tpd allow count <players> <amount> Add teleport uses; level 2 /kt tpd allow time <players> <seconds> Add timed authorization; level 2 /kt tpd check <player> Inspect another player's authorization; level 2 /kt tpd clear <players> Clear both uses and timed authorization; level 2 /kt reload Reload registered module configuration; level 2 For example, /kt tpd allow count Alex 3 adds three uses, and /kt tpd allow time Alex 300 grants five minutes. Counts are added to existing uses; time extends the current expiry if it has not expired. Timed grants use elapsed real time.

Files and application scope File under config/kineticcore/ Contents / application worldblock.json Block bans, fixed/weighted targets, chances, startup-only loaded-chunk switches worldblock.old.json Companion backup for world-block rules worldgen.toml Structure and biome rules; apply on world/server start beacon.toml Global beacon behavior, quotas, and offline rules teleport.toml Teleport mode, bypass, master switch, and denial message World data stores beacon chunk-loading state and one-time chunk rewrite markers. Teleport grants are player data. /kt reload reloads registered block, worldgen, and teleport configuration; it does not re-create an already running world's generation setup or replace a full restart for loaded-chunk mode.

Project Mod ID: realmcontrol. Author: XYAT. License: LGPLv3. Implementation: source. Declared dependencies: mods.toml.