每个玩家都从属于自己的起点开始。 与将所有玩家丢入同一个拥挤的世界出生点不同,SpiralGenesis 会为每位新玩家分配一块属于自己的领地——默认大小为 500x500 方块——这些领地位于你指定的中心点周围,呈螺旋状向外扩展。
插件会为玩家寻找一个合适的站立位置:既不在海洋中,也不在岩浆池里,更不在深坑底部或悬崖边缘。这一过程发生在玩家首次加入时,且在主线程之外进行。一旦获得领地,该位置将成为玩家永久的重生点。
在已有玩家游玩的服务器上安装此插件,不会移动任何现有玩家的位置:在插件安装前就已在服务器上的玩家会保留其原有的位置、床和重生锚;只有当管理员使用 /sgen reassign 命令为其分配时,他们才会获得新的领地。
快速上手
- 要求: Paper 1.20 或更高版本,Paper 分支(如 Purpur),或 Folia(详见“兼容性”部分列出的版本)。
Minecraft 1.20 和 1.21 需要 Java 21;Minecraft 26.1 及更高版本要求服务器运行在 Java 25 上,这是 Mojang 的要求,而非本插件的要求。
- 将
SpiralGenesis-x.y.z.jar 放入服务器的 plugins/ 文件夹中。
- 启动服务器。首次运行时会自动生成
plugins/SpiralGenesis/config.yml 配置文件。
- 站在你希望螺旋起始的位置,并运行
/sgen setcenter。
- 完成。下一位加入的玩家将获得编号为 #0,0 的领地,以该位置为中心。
如果你是在已有玩家游玩的服务器上安装?请在首次启动前阅读 在现有服务器上安装:如果在第 4 步之前有新玩家加入,他们将被放置在 (0, 0) 附近,因此原点应选择远离现有建筑和领地声明的地方。
可选:如果你开启了 Bedrock 跨平台游戏,请安装 Floodgate。如果你的 Java 版玩家通过密码登录,任何登录插件(AuthMe、nLogin、LibreLogin 等)均可直接使用,无需额外配置:SpiralGenesis 会在玩家从“limbo”状态释放后才将其放置。对于在线模式服务器,或在代理层进行身份验证的网络,请将 allocation.trigger: ON_JOIN 设置为在玩家连接的瞬间立即放置他们。
请先生成世界区块。 分配过程会在搜索时动态生成区块。对于全新世界来说这没问题,但预先生成的区域可以让新玩家的首次加入几乎瞬间完成。请参阅 大小指导 了解应生成多大范围。
功能说明
- 每位玩家独占一块领地,永不复用。 领地沿方形螺旋路径发放,使玩家均匀向外扩散,而不是堆积在同一山谷中。
- 避开劣质地形。 海洋、岩浆、冰面、深水、深坑、天坑、悬崖边缘和崎岖山峰都会被拒绝。插件会在放弃当前候选地块之前,在其内部搜索一个合适的着陆点。
- 在家重生。 死亡后你会回到自己的领地,而不是世界出生点——除非有床、重生锚、在其他地方设置的
/spawnpoint 或其他插件的重生地点另有规定。
- 支持跨平台。 Bedrock 玩家(Geyser/Floodgate)在加入时即被放置。Java 玩家若受任何登录插件保护,则会被等待至完成身份验证后再放置,确保无人能在证明身份前占用领地。此功能无需指定具体登录插件名称,因此兼容 AuthMe、nLogin、LibreLogin 及其他类似插件。
- 不阻塞服务器。 区块通过 Paper 的异步 API 加载,每个候选位置的检查都在独立的 tick 中进行。存档操作也在主线程之外批量处理。
- 支持 Folia。 同一 jar 包在整个过程中统一使用区域调度器、实体调度器和异步调度器。
- 可保护出生点。 这是一个可选功能,默认关闭,适用于运行 GriefPrevention 的服务器;插件其余部分不需要它。启用后,每位玩家都会在其出生点周围获得一个小范围的领地声明,只有他们自己能在此建造,从而在他们到达的瞬间覆盖他们的床和第一个箱子。如果无法创建声明,绝不会导致玩家失去领地。设置详情及建议优先检查的两个 GriefPrevention 参数见 管理员指南。
- 可为每块领地标记小型结构。 同样是可选功能,默认关闭:包括小屋、塔楼、用于小范围领地的 3x3 标记,或通过结构方块在游戏中保存的自定义模板。每个新领地仅放置一次,方便玩家日后寻找。它只会替换结构地板下方的地面以及房间内的地形,如果领地空间不足无法容纳,则该领地将保持无结构状态。
参见 出生点领地结构。
不包含的功能
SpiralGenesis 专注于分布:它决定每位玩家的起始位置并将他们分散开来,确保没有两人共享同一块领地。除下方提到的可选出生点正方形外,它不提供土地保护功能,也无需依赖领地插件即可正常工作。它与领地系统的交互方式取决于服务器运行的环境:
- 未安装 GriefPrevention,或在 Folia 上(GriefPrevention 无法在 Folia 上运行),系统不会进行任何领地声明,分配逻辑仅考虑地形。这是一种完整且独立的工作模式,并非简化版。
- 安装了 GriefPrevention,分配逻辑还会避开现有的领地声明,无论所有者是谁。除非开启
protection: 选项,否则 SpiralGenesis 本身不会声明任何领地,而该选项默认是关闭的。
- 同时开启
protection:,它会在每位玩家出生点周围声明一个小正方形区域,这就是它的全部领地相关行为——剩余的 500x500 领地范围仍保持未声明状态。
除此之外,SpiralGenesis 本身不会阻止其他玩家进入他人的领地并进行建造或破坏。如果你的服务器使用土地声明系统,那么像 GriefPrevention 或 Lands 这样的插件可以负责这部分保护工作,而螺旋布局则为它们提供了清晰、无重叠的区域供其运作。
配置
plugins/SpiralGenesis/config.yml,其中最重要的默认配置如下:
origin:
world: "world"
x: 0
z: 0
cell-size: 500 # 每个玩家领地的尺寸(方块数)(500 = 500x500)
placement:
strategy: FIRST_SAFE
stride: 16 # 候选位置之间的间距(方块数)(16 = 一个区块)
max-candidates: 12 # 在一个地块内尝试的候选位置数量,达到此数量后移动到下一个地块
height-ceiling: 110 # 【仅 HIGHEST】忽略高于此 Y 值的位置
safety:
min-surface-y: 63 # 拒绝低于此高度的位置
max-scan-attempts: 8 # 在决定采用目前看到的最佳位置之前,尝试的地块数量
max-pit-depth: 8 # 拒绝比周围地面低于此深度的位置(如峡谷)
max-roughness: 12 # 拒绝周围地形起伏超过此数值的位置(如悬崖)
placement.strategy 决定了玩家在某个地块内落在哪个位置:
| 值 |
作用 |
FIRST_SAFE (默认) |
如果中心位置可行则使用中心,否则向外螺旋搜索找到的第一个合适位置。速度最快。 |
FLATTEST |
检查所有候选位置,选择最平坦的地面。 |
HIGHEST |
检查所有候选位置,选择在 height-ceiling 以下的最高位置。 |
所有值在加载时都会进行范围检查,因此拼写错误会导致回退到合理的默认值,而不会导致加入服务器失败。完整的带注释配置文件包含在 jar 包内;请参阅 管理员指南 了解每条规则具体拒绝什么以及如何调整。
玩家分配情况和当前螺旋位置保存在 data.yml 中——除非你有意重置网格,否则不要修改该文件。
命令
/sgen me 需要权限 spiralgenesis.me(默认:所有人)。所有管理命令需要权限 spiralgenesis.admin(默认:操作员)。
/spiralgenesis 是 /sgen 的别名。
| 命令 |
作用 |
/sgen setcenter |
将你站立位置的 X 和 Z 设为中心坐标。世界始终为 origin.world。 |
/sgen setcenter <x> <z> |
将中心设置为指定的坐标。 |
/sgen setspawn <player> |
将玩家的重生点移动到你所在的位置。 |
/sgen setspawn <player> <x> <y> <z> |
将玩家的重生点移动到精确坐标。 |
/sgen reassign <player> |
为玩家重新分配一个沿螺旋更靠后的新地块。 |
/sgen reassign <player> release |
同上,并释放其旧重生点周围的重生保护区域。仅限重生保护:若无此功能,release 无效。 |
/sgen protect |
仅限重生保护。为在开启保护之前已分配的玩家认领重生格。可安全重复执行。 |
/sgen release-all confirm |
仅限重生保护。从启用了保护的服务器卸载时,释放所有玩家当前地块周围的重生认领区域。受 PLAYER_CLAIM 限制。参见 卸载。 |
/sgen tp <player> |
传送至某玩家的地块。如果地块不再安全会先发出警告,然后依然传送。 |
/sgen info <player> |
显示玩家的地块编号、网格单元、坐标以及实际的认领访问权限。 |
/sgen structure <player> |
报告玩家地块上的结构,或检查配置的模板是否能放入该地块(不实际放置)。添加 place 参数可立即放置。参见 重生地块结构。 |
/sgen me |
显示你的地块、距离、重生点状态及实际的认领访问权限。 |
/sgen simulate <count> |
对你的真实地形进行 1-500 次分配的试运行,并报告结果。会生成区块;但不会移动实时的螺旋进度。 |
/sgen reload |
重载 config.yml。 |
setspawn 和 reassign 作用于在线玩家,因此目标必须在线。tp、info 和 structure 从存储中读取数据,对离线玩家也有效。
三个标记为 仅限重生保护 的命令适用于运行 GriefPrevention 且开启了 protection.enabled 的服务器,并且仅在该选项开启时生效。从未开启过该选项的服务器没有重生认领区域,也不需要这些命令。
/sgen simulate 50 是在玩家到来之前检查你的设置与世界的匹配程度的最快方法——它会报告跳过了多少个地块、搜索回退了多少次,以及具体是哪条安全规则导致了拒绝。
查找你的重生地块
玩家可以使用 /sgen me 查看他们的重生坐标、水平距离、当前重生点状态以及实际的 GriefPrevention 认领边界和命名访问权限。该命令使用权限 spiralgenesis.me(默认:true)。管理命令仍需 spiralgenesis.admin。
分配和变更认领会产生聊天通知。服务器可以自定义 config.yml 中的 messages 部分,包括传统的 & 颜色代码,或者独立关闭自动地块和认领通知。/sgen me 仍然可用。在 Folia 或未安装 GriefPrevention 的情况下,无法获取保护信息。
到达地块时(首次分配、断开连接后重新放置、重新分配,或被传送到该地块重生),操作栏会在几秒钟内显示其坐标。当玩家的认领区域覆盖重生点时,提示会补充其大小、边界,并提及 GriefPrevention 的调查工具,且认领区域的边缘会被绘制一次。messages.arrival 可关闭此功能或更改其计时。
螺旋机制的工作原理
第一个地块 #0,0 落在中心。随后的每个地块沿不断扩大的顺时针方形螺旋移动一格,因此地块 n 始终与其相邻地块相距 cell-size 个方块:
(-1,-1) ───> (0,-1) ───> (1,-1) ───> (2,-1)
▲ │
│ (0,0) [P1] ───> (1,0) [P2] │
│ │ ▼
(-1,0) ▼ (2,0)
▲ (1,1) [P3] │
│ │ ▼
(-1,1) <──── (0,1) <──────┘ (2,1)
[P5] [P4] │
▼
方块的世界坐标即为 x = origin.x + u * cell-size 和
z = origin.z + v * cell-size。完整的推导过程、地形规则及生命周期钩子详见 管理员指南。
兼容性
|
支持情况 |
| Paper, Purpur 及其他 Paper 分支 |
是 1.20.x, 1.21.x, 26.1 至 26.3 |
| Folia |
是 1.20.x, 1.21.x, 26.1 至 26.3 |
| Spigot / CraftBukkit |
否 - 分配功能需要 Paper 的异步区块和传送 API |
| Fabric / NeoForge |
否 - 模组加载器,非插件平台 |
| Velocity / BungeeCord |
否 - 代理服务器无用于分配的“世界”;请安装在后端服务器上 |
本插件基于 1.20.4 API 构建,较新的服务器仍接受该版本。CI 在 Paper 和 Folia 上以 1.20.4、1.21.11、26.2 和 26.3 启动插件,并在每种版本上使用真实生成的地形进行分配测试,因此适用范围是在每次变更时经过验证而非假设得出的。Paper 26.3 也在 CI 和隔离运行中通过真实客户端进行了验证。Folia 的支持范围与 Paper 相同。PaperMC 目前仅将 Folia 26.3 作为实验性(alpha)构建发布,CI 使用其中最新版本对 Folia 26.3 进行了验证,包括让真实客户端通过分配检查点。关于 Paper 26.3 和 Folia 更长时间的实时压力测试,已在 #191 中追踪,目标为 1.0.0 版本。
Minecraft 26.1 及更高版本拒绝在 Java 25 以下环境启动。这是 Mojang 的服务器要求,而非本插件的要求:该 jar 包使用的是 Java 21 字节码,可在 Java 25 运行时环境中无需更改地运行。
故障排除
玩家仍然在世界出生点生成。 他们可能并非新玩家。只有没有记录地块的玩家才会被分配一个;其他玩家会保留其现有的出生点,直到你执行 /sgen reassign 命令为他们重新分配(执行此操作时玩家必须在线)。
没有人获得地块且日志显示名称为 origin.world。 插件仅绑定到名为 origin.world 的世界,绝不会替换为其他名称。如果该世界未加载,日志会以 SEVERE 级别记录 Configured world '...' (origin.world) is not loaded,列出已加载的世界,且不进行任何分配。新玩家将在加入时滞留,并在地块绑定完成后立即分配:请修正 origin.world 配置并运行 /sgen reload。如果某个世界管理器在 SpiralGenesis 启动后加载了世界,则无需重载;当下一个没有地块的玩家经过检查点或滞留玩家行动时,该世界会被自动拾取。Multiverse-Core 总是最先启用,因此当 SpiralGenesis 启动时,其管理的世界均已加载完毕。
首次加入需要几秒钟。 插件正在生成区块以寻找安全的地面。预生成该区域(参见管理员指南中的尺寸表)即可消除此延迟。
玩家在登录前就被放置。 请检查 allocation.trigger 是否为 FIRST_ACTION,而非 ON_JOIN。启动日志会声明当前激活的触发器类型以及检测到的登录插件。
玩家从未被放置。 某种机制抑制了他们的所有行为,导致检查点无法打开。当 action-timeout-seconds 超时保护触发时,控制台会发出警告;如果你反复看到此警告,通常是由反作弊或领地插件引起的。如果是你的登录插件导致的,请将其登录命令钩子指向 sgen allocate %p,这样即可完全绕过检查点。参见 管理员指南。
有人落在了极其糟糕的位置。 运行 /sgen simulate 50 —— 按规则拒绝的详细统计通常能显示出需要放宽的规则,最常见的是山地或海洋密集型世界的 min-surface-y 或 max-roughness。
文档、源码与贡献
自行构建:
./gradlew build
jar 包将生成在 build/libs/ 目录下。
许可证与致谢
GNU General Public License v3.0.
灵感来源于 Block4Block / DynamicSpawnPlugin,该插件首创了面向 Paper 服务器的螺旋模式出生点分布方案。SpiralGenesis 是一个独立实现的版本。
Every player starts somewhere of their own. Instead of dropping everyone at one crowded
world spawn, SpiralGenesis gives each new player their own plot of land - 500x500 blocks by
default - laid out in an expanding spiral around a centre point you choose.
The plugin finds them somewhere sensible to stand: not in an ocean, not in a lava pool, not
at the bottom of a ravine or on the edge of a cliff. It happens on first join, off the main
thread, and the player keeps that spot as their respawn point for good.
Installing it on a server people already play on moves none of them: a player who was there
before the plugin keeps their position, bed and respawn anchor, and gets a plot only when an
operator gives them one with /sgen reassign.
Quick start
- Requirements: Paper 1.20 or newer, a Paper fork such as Purpur, or Folia (on the
versions listed under Compatibility).
Java 21 for Minecraft 1.20 and 1.21; Minecraft 26.1 and newer require the server
to run on Java 25, which is Mojang's requirement rather than this plugin's.
- Drop
SpiralGenesis-x.y.z.jar into your server's plugins/ folder.
- Start the server.
plugins/SpiralGenesis/config.yml is generated on first run.
- Stand where you want the spiral to begin and run
/sgen setcenter.
- That's it. The next player to join gets plot #0,0, centred on that spot.
Installing on a server people already play on? Read
Installing on an existing server
before the first start: a new player who joins before step 4 is placed around (0, 0),
and the origin should be chosen away from existing builds and claims.
Optional: install Floodgate if you run Bedrock cross-play. If your Java players log in
with a password, any login plugin works (AuthMe, nLogin, LibreLogin and the rest) with no
configuration: SpiralGenesis waits for the player to be released from limbo before placing
them. On an online-mode server, or a network authenticating at the proxy, set
allocation.trigger: ON_JOIN to place players the moment they connect.
Pregenerate your world first. Allocation generates chunks as it searches. On a fresh
world that is fine, but a pregenerated area makes first joins near-instant. See
sizing guidance for how big
to make it.
What it does
- One plot per player, never reused. Plots are handed out along a square spiral, so
players spread outward evenly instead of piling into the same valley.
- Skips bad ground. Oceans, lava, ice, deep water, ravines, sinkholes, cliff edges and
jagged peaks are all rejected. The plugin searches inside a plot for a good landing
spot before giving up on it.
- Respawns at home. Die and you return to your own plot, not to world spawn - unless
a bed, a respawn anchor, a
/spawnpoint set elsewhere or another plugin's respawn
location says otherwise.
- Cross-play aware. Bedrock players (Geyser/Floodgate) are placed the moment they join.
Java players behind any login plugin are held until they authenticate, so nobody burns a
plot before proving who they are. This works without naming a login plugin, so it covers
AuthMe, nLogin, LibreLogin and anything else.
- Doesn't stall the server. Chunks load through Paper's async API and each candidate
spot is checked on its own tick. Saves are batched off the main thread.
- Runs on Folia. The same jar uses region, entity and async schedulers throughout.
- Can protect the spawn point. An optional extra, off by default, for servers running
GriefPrevention; nothing else in the plugin needs it. Switch it on and every player gets
a small claim around their spawn that only they can build in, so their bed and first
chest are covered the moment they arrive. It never costs anyone their plot when it
cannot be created. See the admin guide for
the settings and the two GriefPrevention numbers worth checking first.
- Can mark each plot with a small structure. Also optional and off by default: a hut,
a tower, a 3x3 marker for small claims, or a template you save in game with a structure
block, placed once on each new plot so players can find it again. It only replaces the
ground under its floor and the terrain inside its rooms, and a plot where it does not
fit is simply left without one.
See Spawn plot structures.
What it does not do
SpiralGenesis is about distribution: it decides where each player starts and spaces
them out so that no two share a plot. Apart from the optional spawn square below, it does
not protect land, and it needs no claim plugin to do its job. How it deals with claims
depends on what the server runs:
- Without GriefPrevention, or on Folia (where GriefPrevention cannot run), nothing is
claimed and allocation looks at terrain only. This is a complete setup, not a reduced
one.
- With GriefPrevention installed, allocation also keeps new spawns off existing
claims, whoever owns them. Nothing is claimed by SpiralGenesis unless
protection: is
switched on, and it is off by default.
- With
protection: switched on as well, it claims a small square around each
player's spawn point, and that is the whole of it - the rest of the 500x500 plot stays
unclaimed.
Beyond that square, nothing in SpiralGenesis stops another player walking onto someone
else's plot and building or breaking things there. If your server uses land claiming, a
plugin such as GriefPrevention or Lands covers that, and the spiral layout gives it
clean, non-overlapping regions to work with.
Configuration
plugins/SpiralGenesis/config.yml, with the defaults that matter most:
origin:
world: "world"
x: 0
z: 0
cell-size: 500 # size of each player's territory in blocks (500 = 500x500)
placement:
strategy: FIRST_SAFE
stride: 16 # blocks between candidate spots (16 = one chunk)
max-candidates: 12 # spots tried inside a plot before moving to the next one
height-ceiling: 110 # HIGHEST only: ignore anything above this Y
safety:
min-surface-y: 63 # reject spots below this height
max-scan-attempts: 8 # plots to try before settling for the best seen so far
max-pit-depth: 8 # reject spots this far below the surrounding land (ravines)
max-roughness: 12 # reject spots whose surroundings are this uneven (cliffs)
placement.strategy decides which spot inside a plot a player lands on:
| Value |
What it does |
FIRST_SAFE (default) |
Centre of the plot if it works, otherwise the first good spot found spiralling outward. Fastest. |
FLATTEST |
Check every candidate, pick the most level ground. |
HIGHEST |
Check every candidate, pick the highest one below height-ceiling. |
Every value is range-checked on load, so a typo degrades to a sane value instead of
breaking joins. The full annotated file ships inside the jar; see the
admin guide for what each rule actually rejects and how to tune it.
Player assignments and the current spiral position live in data.yml - leave that one
alone unless you are deliberately resetting the grid.
Commands
/sgen me requires spiralgenesis.me (default: everyone). All administrative
commands require spiralgenesis.admin (default: operators).
/spiralgenesis works as an alias for /sgen.
| Command |
What it does |
/sgen setcenter |
Set the centre's X and Z to where you're standing. The world is always origin.world. |
/sgen setcenter <x> <z> |
Set the centre to explicit coordinates. |
/sgen setspawn <player> |
Move a player's spawn to your position. |
/sgen setspawn <player> <x> <y> <z> |
Move a player's spawn to exact coordinates. |
/sgen reassign <player> |
Give a player a fresh plot further along the spiral. |
/sgen reassign <player> release |
The same, and release the spawn claim around their old spawn. Spawn protection only: without it, release does nothing. |
/sgen protect |
Spawn protection only. Claim the spawn square for players allocated before protection was switched on. Safe to run twice. |
/sgen release-all confirm |
Spawn protection only. Release the spawn claim around every player's current plot, when uninstalling from a server that has had protection on. Refused under PLAYER_CLAIM. See Uninstalling. |
/sgen tp <player> |
Teleport yourself to a player's plot. Warns first if the plot is no longer safe, then goes anyway. |
/sgen info <player> |
Show a player's plot number, grid cell, coordinates and actual claim access. |
/sgen structure <player> |
Report the structure on a player's plot, or check whether the configured template would fit there, changing nothing. Add place to place it now. See Spawn plot structures. |
/sgen me |
Show your plot, distance, respawn-point status and actual claim access. |
/sgen simulate <count> |
Dry-run 1-500 allocations against your real terrain and report what it found. Generates chunks; does not move the live spiral forward. |
/sgen reload |
Reload config.yml. |
setspawn and reassign act on the live player, so the target has to be online. tp,
info and structure read from storage and work for offline players too.
The three marked spawn protection only are for servers running GriefPrevention with
protection.enabled switched on, and act only while it is. A server that never switches
it on has no spawn claims and needs none of them.
/sgen simulate 50 is the fastest way to check your settings against your world before
players arrive - it reports how many plots were skipped, how often the search fell back,
and exactly which safety rule did the rejecting.
Finding your spawn plot
Players can use /sgen me to see their spawn coordinates, horizontal distance,
current respawn-point status and actual GriefPrevention claim bounds and named
access. The command uses spiralgenesis.me (default: true). Administrative commands
still require spiralgenesis.admin.
Allocation and changed claims produce chat notices. Servers can customise the
messages section of config.yml, including legacy & colours, or independently
turn off automatic plot and claim notices. /sgen me remains available. Protection
information is unavailable on Folia or without GriefPrevention.
On arrival at the plot (first allocation, placement after a disconnect, reassignment,
or a respawn sent to the plot) the action bar shows its coordinates for a few seconds.
When a claim of the player's covers the spawn, the hint adds its size and bounds and
names GriefPrevention's investigation tool, and the claim's edges are drawn once.
messages.arrival switches it off or changes its timings.
How the spiral works
The first plot, #0,0, lands on the centre. Each following plot moves one cell along an
expanding clockwise square spiral, so plot n is always cell-size blocks from its
neighbours:
(-1,-1) ───> (0,-1) ───> (1,-1) ───> (2,-1)
▲ │
│ (0,0) [P1] ───> (1,0) [P2] │
│ │ ▼
(-1,0) ▼ (2,0)
▲ (1,1) [P3] │
│ │ ▼
(-1,1) <──── (0,1) <──────┘ (2,1)
[P5] [P4] │
▼
A cell's world position is simply x = origin.x + u * cell-size and
z = origin.z + v * cell-size. The full derivation, terrain rules and lifecycle hooks are
in the admin guide.
Compatibility
|
Supported |
| Paper, Purpur and other Paper forks |
Yes 1.20.x, 1.21.x, 26.1 to 26.3 |
| Folia |
Yes 1.20.x, 1.21.x, 26.1 to 26.3 |
| Spigot / CraftBukkit |
No - allocation needs Paper's async chunk and teleport APIs |
| Fabric / NeoForge |
No - mod loaders, not plugin platforms |
| Velocity / BungeeCord |
No - proxies have no world to allocate in; install on the backend servers |
Built against the 1.20.4 API, which newer servers still accept. CI boots the plugin on
Paper and Folia at 1.20.4, 1.21.11, 26.2 and 26.3, and runs allocation against real
generated terrain on each, so the range is checked on every change rather than assumed.
Paper 26.3 is also verified with real clients in CI and in isolated runs. Folia is
supported across the same range as Paper. PaperMC has published Folia 26.3 only as
experimental (alpha) builds so far, and CI verifies Folia 26.3 against the latest of
those, including a real client passing through the allocation gate. Longer Paper 26.3
and Folia live soaks are tracked for 1.0.0 in
#191.
Minecraft 26.1 and newer refuse to start on anything below Java 25. That is a server
requirement from Mojang, not this plugin: the jar is Java 21 bytecode, which a Java 25
runtime runs unchanged.
Troubleshooting
Players still spawn at world spawn. They are probably not new. Only players without a
recorded plot are allocated one; everyone else keeps the spawn they already have until you
/sgen reassign them (they must be online for that).
Nobody gets a plot and the log names origin.world. The plugin binds only to the
world origin.world names and never substitutes another. If that world is not loaded it
logs Configured world '...' (origin.world) is not loaded at SEVERE, lists the worlds
that are, and allocates nothing. New players are held where they joined and allocated as
soon as the world is bound: correct origin.world and run /sgen reload. A world that a
world manager loads after SpiralGenesis starts needs no reload; it is picked up the next
time a player without a plot passes the gate or a held player acts. Multiverse-Core is
always enabled first, so its worlds are already loaded when SpiralGenesis starts.
First join takes a few seconds. The plugin is generating chunks to look for safe
ground. Pregenerate the area (see the sizing table in the admin guide) and it disappears.
Players get placed before logging in. Check allocation.trigger is FIRST_ACTION, not
ON_JOIN. The startup log states which trigger is active and which login plugins it saw.
Players never get placed. Something is suppressing every action they take, so the gate
never opens. The console warns when the action-timeout-seconds backstop fires; if you see
that repeatedly, an anti-cheat or region plugin is the usual cause. If it is your login
plugin, point its on-login command hook at sgen allocate %p and the gate is bypassed
entirely. See the admin guide.
Someone landed somewhere terrible. Run /sgen simulate 50 - the per-rule rejection
breakdown usually shows the rule that needs loosening, most often min-surface-y or
max-roughness on mountainous or ocean-heavy worlds.
Docs, source and contributing
Building it yourself:
./gradlew build
The jar lands in build/libs/.
License & credits
GNU General Public License v3.0.
Inspired by Block4Block / DynamicSpawnPlugin,
which pioneered spiral-pattern spawn distribution for Paper servers. SpiralGenesis is an
independent implementation.
评论 0
登录后参与评分
还没有评论,来抢沙发吧