CoreStructuresX
CoreStructuresX 是一款仅适用于 Paper 的模块化结构插件。它允许管理员从经过验证的 WorldEdit 或 FastAsyncWorldEdit 原理图包中构建结构,然后通过标记的连接点以自动或玩家接近模式对其进行扩展。
其目标是使模块化结构可控、可重复且可恢复,而无需将其与世界生成绑定。每个结构均由管理员手动启动,而包设置则定义了其模块如何继续扩展。
有关包制作、标记格式、配置示例、命令和故障排除,请访问 CoreStructuresX 文档。
CoreStructuresX 目前正处于积极开发阶段,应被视为正在进行中的工作。
该插件尚未功能完备,可能包含错误、不完整的功能、意外行为或破坏性更改。未来的更新可能会修改命令、配置文件、包格式、标记行为、持久化数据、扩展逻辑或插件的其他部分,而不保证完全向后兼容。
在生产服务器上使用前:
- 在单独的环境中测试插件和所有结构包;
- 定期备份世界、包文件、配置文件和实例 JSON 数据;
- 在更新前查阅发行说明;
- 不要假设使用早期版本创建的配置或结构将继续原样工作。
目前主要建议在测试、开发和受控环境中使用 CoreStructuresX。
CoreStructuresX 的功能
- 从插件数据文件夹加载模块化结构包。
- 使用 WorldEdit 或 FastAsyncWorldEdit
.schem 文件作为结构模块。
- 在结构启动前验证包文件、原理图引用、标记告示牌、组和放置设置。
- 使用
[CSX] 标记告示牌作为原点、模块连接器和粘贴后的控制台命令。
- 支持加权原理图组、回退组和闭合组。
- 支持
AUTOMATIC(自动)和 PLAYER_PROXIMITY(玩家接近)扩展模式。
- 检查转换后的原理图边界,以防止不需要的模块重叠。
- 支持可选的方块白名单检查和连接器前瞻检查。
- 通过可配置的分块任务粘贴大型原理图。
- 当服务器 TPS 或 MSPT 超过配置的限制时,可以暂停自动扩展。
- 将实例、生成的模块、连接器、触发器和命令状态持久化为 JSON。
- 包括用于验证、包列表、结构启动和实例管理的管理员命令。
统计数据

使用方法
在 Paper 服务器上安装 CoreStructuresX 以及 WorldEdit 或 FastAsyncWorldEdit,然后启动服务器一次以生成插件文件夹和默认的 config.yml。
在 plugins/CoreStructuresX/packs/<pack-id>/ 下创建一个包,其中包含其 YAML 定义、原理图文件和 [CSX] 标记告示牌。运行 /csx validate 并在通过 /csx start <pack-id> 启动结构之前纠正所有报告的错误。
结构不会添加到生物群系、区块、种子或地形生成中。管理员始终选择何时以及何地放置第一个模块。
由于 CoreStructuresX 仍处于积极开发阶段,请在现有生产世界中使用新的包和插件更新之前,在单独的服务器上测试它们。
模块化结构包
每个包定义一种结构类型,并将职责分离到专注的文件中:
pack.yml 标识包及其引用的文件。
structure.yml 控制启动组、生成模式、放置规则、限制和性能设置。
groups.yml 定义加权原理图候选项、回退组和闭合组。
commands.yml 定义由命令标记使用的可选加权控制台命令。
schematics/ 包含 WorldEdit 或 FAWE .schem 模块。
严格的验证可防止无效包启动。这在将方块粘贴到世界之前,会捕获缺失的文件、未解析的组、无效的标记、不支持的设置以及其他制作问题。
验证降低了无效放置的风险,但不能保证包没有逻辑、视觉或运行时问题。包作者应在公开或生产使用前始终测试完整的扩展路径。
基于标记的扩展
CoreStructuresX 从保存在原理图中的告示牌读取三种标记类型:
ORIGIN 定义模块放置原点。如果省略,则默认使用保存的原理图剪贴板原点。
CONNECTOR 创建一个与原理图组链接的一次性扩展点。
COMMAND 在放置后或当接近触发器激活时,从服务器控制台运行一个加权命令组条目。
标记告示牌在粘贴过程中会被替换,而运行结构所需的连接器和触发器数据会保存到其实例 JSON 中。
只有受信任的管理员才应被允许制作包或使用结构启动命令,特别是当包包含控制台命令标记时。
在插件处于开发阶段期间,标记语法和行为可能会发生变化。包作者在每次更新后应查阅文档和发行说明。
扩展和放置安全
AUTOMATIC(自动)模式在尊重包的作业延迟、生成限制、放置检查和服务器稳定性阈值的情况下,通过开放的连接器继续扩展。
PLAYER_PROXIMITY(玩家接近)模式会在玩家进入同一世界中配置的半径时激活特定的连接器或命令。
在放置候选模组之前,CoreStructuresX 可以将其转换后的结构图边界与已生成和待处理的模组进行比对。整合包还可以启用方块白名单检查、前瞻检查、回退候选项以及闭合组,以控制结构的完成方式或在放置被拒绝时的恢复机制。
这些安全措施旨在减少无效或不需要的放置,但它们不应被视为备份和受控测试的替代品。Bug、错误的整合包设置或意外的结构图几何形状仍可能导致不理想的世界修改。
持久化与管理
每个正在运行的结构都以 JSON 格式存储在 plugins/CoreStructuresX/data/instances/ 下。持久化状态包括生成的模组、开放的连接器、邻近触发器、命令记录、限制条件以及当前实例状态,这使得插件能够在正常重启后恢复其运行时状态。
管理员可以:
- 使用
/csx reload 重新加载配置和整合包
- 使用
/csx validate 验证所有整合包或选定的某个整合包
- 使用
/csx packs list 列出已加载的整合包
- 使用
/csx start <pack-id> 启动一个实例
- 使用
/csx instances list 和 /csx instance info <instance-id> 检查活动实例
- 使用
/csx instance <pause|resume|stop> <instance-id> 暂停、恢复或停止一个实例
在进行手动恢复或修复之前,请备份实例 JSON。CoreStructuresX 不会自动删除损坏的持久化数据。
持久化格式可能在开发版本之间发生变化。在更新之前,请备份整个 plugins/CoreStructuresX/ 文件夹,并查阅发行说明以了解迁移要求或兼容性警告。
当前状态
CoreStructuresX 目前处于积极开发阶段,尚未被认为是功能完整或生产稳定的。
现有的功能、命令、配置选项、整合包格式、持久化结构和生成行为可能在开发过程中发生变化。Bug 和不完整的功能可能仍然存在,更新可能需要对整合包、配置或实例数据进行调整。
CoreStructuresX 目前:
- 支持 Paper 1.21.11 及以上版本
- 需要 Java 21 或更高版本
- 需要安装并加载 WorldEdit 或 FastAsyncWorldEdit
- 仅支持手动启动结构
- 支持 WorldEdit 或 FAWE
.schem 整合包
- 将运行时实例状态存储在本地 JSON 文件中
- 不与生物群系、区块、种子或地形生成集成
- 在版本 2026.1.0 中不支持 Folia
- 通过服务器范围的 bStats 配置报告匿名使用统计信息
所列功能描述了当前的开发版本,未来的发行版可能会更改、扩展、替换或删除这些功能。
总结
CoreStructuresX 专为希望拥有模块化结构图结构、严格验证、可控扩展、放置安全保障以及重启安全状态的服务器管理员和整合包作者而构建。
它提供了一个专注的 Paper 工作流:在整合包中定义模组和连接器,验证整合包,在选定位置启动实例,然后让 CoreStructuresX 管理其配置的扩展规则。
CoreStructuresX 仍在开发中。目前应在适当的测试、备份和使用意识下使用,并意识到未来的更新可能会引入行为变化,或要求更新现有的整合包和配置文件。
也可以试试
CoreStructuresX
CoreStructuresX is a Paper-only modular structure plugin for Minecraft servers. It lets administrators build structures from validated WorldEdit or FastAsyncWorldEdit schematic packs, then expand them through marked connection points in automatic or player-proximity mode.
The goal is to make modular structures controlled, repeatable, and recoverable without tying them to world generation. Every structure is started manually by an administrator, while pack settings define how its modules can continue to expand.
For pack authoring, marker formats, configuration examples, commands, and troubleshooting, visit the CoreStructuresX documentation.
CoreStructuresX is currently under active development and should be considered a work in progress.
The plugin is not yet feature-complete and may contain bugs, incomplete functionality, unexpected behavior, or breaking issues. Future updates may modify commands, configuration files, pack formats, marker behavior, persistence data, expansion logic, or other parts of the plugin without maintaining full backward compatibility.
Before using CoreStructuresX on a production server:
- test the plugin and all structure packs in a separate environment;
- keep regular backups of worlds, pack files, configuration files, and instance JSON data;
- review release notes before updating;
- do not assume that configurations or structures created with an earlier version will continue to work unchanged.
CoreStructuresX is currently recommended primarily for testing, development, and controlled environments.
What CoreStructuresX Does
- Loads modular structure packs from the plugin data folder.
- Uses WorldEdit or FastAsyncWorldEdit
.schem files as structure modules.
- Validates pack files, schematic references, marker signs, groups, and placement settings before a structure starts.
- Uses
[CSX] marker signs for origins, module connectors, and post-paste console commands.
- Supports weighted schematic groups, fallback groups, and closing groups.
- Supports
AUTOMATIC and PLAYER_PROXIMITY expansion modes.
- Checks transformed schematic bounds to prevent unwanted module overlap.
- Supports optional block whitelist checks and connector lookahead checks.
- Pastes large schematics through configurable chunked jobs.
- Can pause automatic expansion when server TPS or MSPT crosses configured limits.
- Persists instances, generated modules, connectors, triggers, and command state in JSON.
- Includes administration commands for validation, pack listing, structure starts, and instance management.
Stats

How To Use
Install CoreStructuresX together with WorldEdit or FastAsyncWorldEdit on a Paper server, then start the server once to generate the plugin folders and default config.yml.
Create a pack under plugins/CoreStructuresX/packs/<pack-id>/ with its YAML definitions, schematic files, and [CSX] marker signs. Run /csx validate and correct every reported error before starting the structure with /csx start <pack-id>.
Structures are not added to biome, chunk, seed, or terrain generation. An administrator always chooses when and where the first module is placed.
Because CoreStructuresX is still under active development, test new packs and plugin updates on a separate server before using them in an existing production world.
Modular Structure Packs
Each pack defines one structure type and separates its responsibilities across focused files:
pack.yml identifies the pack and its referenced files.
structure.yml controls the start group, generation mode, placement rules, limits, and performance settings.
groups.yml defines weighted schematic candidates, fallback groups, and closing groups.
commands.yml defines optional weighted console commands used by command markers.
schematics/ contains the WorldEdit or FAWE .schem modules.
Strict validation prevents invalid packs from starting. This catches missing files, unresolved groups, invalid markers, unsupported settings, and other authoring problems before blocks are pasted into the world.
Validation reduces the risk of invalid placements but does not guarantee that a pack is free from logical, visual, or runtime problems. Pack authors should always test complete expansion paths before public or production use.
Marker-Driven Expansion
CoreStructuresX reads three marker types from signs saved inside schematics:
ORIGIN defines the module placement origin. If it is omitted, the saved schematic clipboard origin is used by default.
CONNECTOR creates a one-use expansion point linked to a schematic group.
COMMAND runs one weighted command-group entry from the server console after placement or when its proximity trigger activates.
Marker signs are replaced during paste, while the connector and trigger data needed by the running structure is saved to its instance JSON.
Only trusted administrators should be allowed to author packs or use structure-start commands, especially when a pack contains console command markers.
Marker syntax and behavior may change while the plugin remains under development. Pack authors should review the documentation and release notes after every update.
Expansion And Placement Safety
AUTOMATIC mode continues through open connectors while respecting the pack's job delay, generation limits, placement checks, and server-stability thresholds.
PLAYER_PROXIMITY mode activates a specific connector or command when a player enters its configured radius in the same world.
Before placing a candidate module, CoreStructuresX can check its transformed schematic bounds against generated and pending modules. Packs can also enable block whitelist checks, lookahead checks, fallback candidates, and closing groups to control how structures finish or recover from rejected placements.
These safeguards are intended to reduce invalid or unwanted placements, but they should not be treated as a substitute for backups and controlled testing. Bugs, incorrect pack settings, or unexpected schematic geometry may still cause undesirable world modifications.
Persistence And Administration
Each running structure is stored as JSON under plugins/CoreStructuresX/data/instances/. Persisted state includes generated modules, open connectors, proximity triggers, command records, limits, and current instance status, allowing the plugin to restore its runtime state after a normal restart.
Administrators can:
- reload configuration and packs with
/csx reload
- validate all packs or one selected pack with
/csx validate
- list loaded packs with
/csx packs list
- start an instance with
/csx start <pack-id>
- inspect active instances with
/csx instances list and /csx instance info <instance-id>
- pause, resume, or stop an instance with
/csx instance <pause|resume|stop> <instance-id>
Back up instance JSON before manual recovery or repair. CoreStructuresX does not automatically delete corrupted persistence data.
Persistence formats may change between development versions. Before updating, back up the entire plugins/CoreStructuresX/ folder and review the release notes for migration requirements or compatibility warnings.
Current State
CoreStructuresX is currently under active development and is not yet considered feature-complete or production-stable.
Existing features, commands, configuration options, pack formats, persistence structures, and generation behavior may change during development. Bugs and incomplete functionality may still be present, and updates may require pack, configuration, or instance-data adjustments.
CoreStructuresX currently:
- supports Paper 1.21.11 and above
- requires Java 21 or newer
- requires WorldEdit or FastAsyncWorldEdit to be installed and loaded
- supports manual structure starts only
- supports WorldEdit or FAWE
.schem packs
- stores runtime instance state in local JSON files
- does not integrate with biome, chunk, seed, or terrain generation
- does not support Folia in version 2026.1.0
- reports anonymous usage statistics through the server-wide bStats configuration
The listed functionality describes the current development version and may be changed, expanded, replaced, or removed in future releases.
Summary
CoreStructuresX is built for server administrators and pack authors who want modular schematic structures with strict validation, controlled expansion, placement safeguards, and restart-safe state.
It provides a focused Paper workflow: define modules and connections in a pack, validate the pack, start an instance at a chosen location, and let CoreStructuresX manage its configured expansion rules.
CoreStructuresX remains a work in progress. It should currently be used with appropriate testing, backups, and awareness that future updates may introduce behavioral changes or require existing packs and configuration files to be updated.
Also try
评论 0
登录后参与评分
还没有评论,来抢沙发吧