Tune Waystones config + ship via defaultconfigs #11

2026-05-23T12:55:18Z

Matt commented

2026-05-23 12:55:18 +00:00

Disables village-waystone worldgen. Leaves the rest at mod default (already provides ACTIVATION+restricted+no-global-UI protections). Bumps pack to 0.16.1.

Matt added 1 commit 2026-05-23 12:55:18 +00:00

pack: tune Waystones config + bump to 0.16.1 3dc0767a24

Ships an override of waystones-common.toml under pack/overrides/
defaultconfigs/ so first-run installs (clients + fresh servers) get the
intended defaults. NeoForge auto-copies defaultconfigs/<file> into
config/<file> on first run only -- player-tweaked configs after that
are preserved across pack updates.

The only override vs mod-default in this commit:
- spawnInVillages: REGULAR -> DISABLED

Everything else stays at mod default, which already gives the security
posture we want:
- defaultVisibility = ACTIVATION  -> each player must physically visit
  a waystone before they can teleport TO it. Solves the "player B
  teleports into player A's base" concern without a hard per-player
  placement cap (which v21.x dropped).
- restrictedWaystones = [PLAYER]  -> only owners can edit their own
  waystones.
- allowedVisibilities = []        -> no player UI can create global
  waystones; OPs use the /waystone command for server-public ones.

Wild waystones (in the open world, not villages) stay on -- they're
public-good fast travel, not tied to bases.

Matt merged commit d4dfcb1e11 into main

2026-05-23 12:55:19 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: minecraft/brass-and-sigil#11