面向 机械动力(Create)服务器的优化与网络管理附属。
An optimization and network management add-on built for Create-based servers.
Language: English (US) /简体中文(中国大陆)/繁體中文(台灣)
未安装机械动力模组时无法使用本模组 Cannot work without CREATE mod
中文 | English
Create CIR Addition 是一个针对机械动力综合服务器的服务端附属,主要解决三件事:
- 性能 —— 减少 Create 方块实体和方块实体的网络同步与 tick 开销
- 规则 —— (可选)限制 AE2 量子环的过度堆叠,迫使玩家用物流网络而不是无脑并联;限制AE2本身的发电,迫使玩家使用CC&A的发电机基于应力发电
- 运维 —— MSPT 预警、应急扫地、垃圾桶找回等
该模组每一项优化都对应一处具体的 Create 内部实现,每一个改动均为了方便服务器的构建和管理。绝大多数功能可以通过修改配置文件调节。
- 修复 RollingGate
1.1.0+build.66加载配置时从后台线程修改 GLFW 窗口属性造成的启动卡死;更新被非阻塞地调度到游戏主线程。此补丁只对对应版本的客户端启用,不加载到专用服务器。 - 修复 ThroughputQuest 1.0.0 对 AdvancedAE 私有 Mixin 访问器的调用:改用 AE2 的公开 getter,覆盖服务端检测与客户端渲染。仅检测到
throughput_quest和ae2时启用;不需要修改第三方 JAR。 - 工作盆被拆除时的动力冲压机空粒子修复仅对 Create 6.0.10 启用。其他版本自动跳过此补丁,其他工作盆优化保持原有行为。
- CIR 网络协议升级为 3.4.8。新版服务器接受协议 3.4.7、3.4.8,拒绝更早或未知协议;其他模组的协商不变。新版客户端连接旧版服务器时仍受旧服务器的严格检查限制。
3.4.7fix使用协议3.4.7,属于兼容范围。 - 补齐 AE2 发电控制、强制清扫和开关状态的三语翻译。
兼容补丁在启动时由 CirMixinPlugin 自动检测;不需要手动开启,也不会把可选模组变成必装依赖。
工作盆空粒子补丁是临时兼容措施;Create 上游修复后可移除该项。这个说明不涉及 ThroughputQuest、RollingGate 等其他兼容修复。
| 修复 | 自动启用条件 | 范围 |
|---|---|---|
| 动力冲压机空物品粒子 / 拆除工作盆时掉线 | Create 版本号严格等于 6.0.10 |
其他 Create 版本跳过这一补丁;不影响原有工作盆及其他 Create 优化 |
| ThroughputQuest 旧访问器兼容 | 同时安装 throughput_quest 和 ae2 |
修复服务端检测及客户端渲染;针对 1.0.0 实测通过,仅替换明确匹配的旧调用,新版本没有这些调用时不作替换 |
| RollingGate 窗口设置导致启动卡死 | 客户端安装 rolling_gate,版本号严格等于 1.1.0+build.66 |
将窗口属性修改交给游戏主线程;专用服务器不加载该补丁 |
缺少对应模组或不满足版本条件时,相关补丁自动跳过。ThroughputQuest 使用的是“安装检测+旧调用匹配”,不是把所有版本的模组逻辑整体覆盖。日志会记录各项条件补丁是否启用。
动力冲压机在工作盆上运行的瞬间,如果下方工作盆被拆除,服务端会把一个数量为 0 的物品写进方块实体的粒子同步包。客户端解析出来是空物品栈,创建粒子时抛出:
java.lang.IllegalArgumentException: Empty stacks are not allowed
表现是客户端直接弹出「网络协议错误」并掉线。该问题在 3.4.7fix 中修复:创建粒子前先把空物品栈从粒子列表里剔除,避免将其用于粒子构造。
历史版本 3.4.7fix 的网络通道协商版本为
3.4.7,旧客户端可正常连接,模组列表显示版本为3.4.7fix。
| 目标 | 优化内容 |
|---|---|
SmartBlockEntity |
同步包节流(1/3)、按玩家距离动态调整 lazyTick 频率 |
MountedStorageManager |
提高同步冷却,减少挂载库存的重复发包 |
PackageEntity |
减少包裹实体的追踪更新 |
BeltBlockEntity |
传送带 tick 优化 |
ChainConveyorBlockEntity |
锁链运输 tick 间隔调整 |
BasinBlockEntity |
工作盆溢出检查间隔 |
FunnelBlockEntity |
漏斗 tick 优化 |
以上间隔全部可配置,默认值经过实测。
缓存 LinkBehaviour.isAlive() 的查询结果(按游戏 tick 粒度)。
Create 的 RedstoneLinkNetworkHandler.updateNetworkOf 每次被调用都要遍历整个同频率网络,对每个节点做 4 次状态查询。终端一多、或者区块反复加载,就是 O(n²) 的开销。
这个优化不会影响信号实时性 —— 信号值 getTransmittedStrength() 依然是实时读取,缓存的只是「这个节点是否存活」。最坏情况是同一 tick 内被拆掉的终端晚 1 tick 才被移出网络。
可用 /cir redstoneLinkOptimization true|false 热切换。
客户端与服务端之间的 Create 同步包会按大小自动选择 LZ4 或 Zstd 压缩,小包直接放行避免因压缩反而变大。
需要 AE2。没装的话整个功能跳过,其他功能不受影响。
限制 ME 量子环(ae2:quantum_ring + ae2:quantum_link)的密集程度以迫使玩家更多使用机械动力的物理系统:
- 主世界:半径 1024 格内最多 2 座、4096 格内最多 4 座(两级同时满足)
- 其他维度:每个维度最多 4 座,不看距离
- 基地豁免:主基地半径 256 格内不限制
首次安装量子环,当多方块结构成型时会立刻收到提示,并提示附近剩余可建造数量
超出限制的新环会在成型瞬间被拆除,原地留一块黑曜石,并召唤一道纯视觉效果的闪电。
计数基于一张持久化的「已登记环坐标表」,不依赖区块加载 —— 半径 4096 格等于 512×512 个区块,实时扫描根本不现实。
基地位置可以通过指令 设置 (op level=4) 或 查询 (op level >=0) ,扫描指令 /cir quantum scan可用于扫描添加已加载的所有量子环。
扫描获得的量子环坐标将被保存在文件中而非缓存,因此游戏重启后仍会被调用。
数量上限、基地豁免半径、以及是否启用本功能,都可以在 config/create_cir_addition.toml 里调整。
P.S. 为防止玩家使用活塞,实体方块化等方式绕开方块放置检测创建量子环,本mod采用的方案为检测到量子环成型(未被加载的量子环被加载时也会被判定为多方块成型)后对照已被扫描的量子环清单决定该量子环是否触发提示或拆除。
需要 AE2。没装的话指令会提示「未检测到 AE2」,其他功能不受影响。
AE2 自带两个能给 ME 网络发电的方块。本模组提供运行时调节,不用改 ae2-common.toml,也不用重启:
| 方块 | 中文名 | 调节方式 |
|---|---|---|
ae2:crystal_resonance_generator |
水晶谐振发电机 | 开 / 关 |
ae2:vibration_chamber |
谐振仓 | 三档:low / normal / boost |
谐振仓三档以「切档前的值」为基准整体缩放:
| 档位 | 燃料系数 | 下限 AE/t | 上限 AE/t |
|---|---|---|---|
low |
×1/4 | ×1/4 | ×1/4 |
normal |
×1 | ×1 | ×1 |
boost |
×4 | ×4 | ×4 |
以 AE2 默认的 5 / 4 / 40 为例,三档分别是 1.25 / 1 / 10、5 / 4 / 40、20 / 16 / 160。
基准会在第一次切档时快照进 create_cir_addition.toml(ae2Vibration*Snapshot 相关项)。所以如果手动把 ae2-common.toml 调成 10 / 8 / 80,normal 恢复的是对应文件的值,不会被恢复为 AE2 默认设置。
切完立即生效,包括已放置的机器。 AE2 把这三项缓存在方块实体的 final 字段里,构造之后再也不看配置;本mod会逐个顶掉该缓存,聊天栏会提示当前同步数量。
谐振仓参数无法设置为零。 AE2 自身下限是 baseEnergyPerFuelTick ≥ 0.1、maxEnergyPerGameTick ≥ 1,low 只是压到 1/4,不是关闭。需要完全禁用只能靠删配方或拦截交互。
数值写于 AE2 的
ae2-common.toml,所以这条调节是全局的 —— 一台机器切档,全服所有谐振仓都会更新配置。
首次进入新地图时,世界出生点被自动设为基地。可用 /cir setHome 更改(需要管理员权限)。
全世界只有一个基地,只在主世界生效,同维度才有豁免。
每 30 秒采样一次服务器 MSPT,四档:40 / 45 / 50 / 70(颜色:白 → 黄 → 金 → 红)。
读到超线不会立刻报,要等 3 秒复检一次。
- 第二次仍在同一档位或更高 → 根据第二次的读数和档位触发全局播报
- 第二次数值下降 → 保持完全静默
重复确认为避免自动保存或偶然的卡顿误触报警的操作,只有持续性负载才会报出来。
≥ 70 时每次确认都会触发广播,直到mspt不再高于该值。
前三档处于「每 tick 有余量」的范围内(50 MSPT刚好占满 20 TPS),其作用为提前告知趋势。70MSPT已经可以导致明显可见的卡顿。
没有定时扫地。 触发方式只有两种:
- MSPT ≥ 70(红色档位确认后)自动触发清理
- 管理员执行扫地命令
/cir cleanup,或使用MCDR,KubeJS等外部包装方法间接执行该指令
被清理的物品不会消失,而是进垃圾桶,有效期 1 小时。玩家用 /cir trashBin 或点击聊天栏的垃圾桶文字提示打开界面取回。
手动执行 /cir cleanup 时,这条提示会全服广播,附带可点击的「打开垃圾桶」按钮。
带自定义名称的物品默认受保护(可在配置里关闭)。
为了避免垃圾桶在编码物品时造成客户端被踢下线,下列物品不会被清理,留在地面等玩家自行拾取:
| 跳过 | 原因 |
|---|---|
| 所有旗帜 | 图案是静态注册表条目,两端未必一致 |
| 17 种原版潜影盒 | 内部物品表随物品走 |
| 任何带附魔的物品 | 数据包重载后旧附魔引用会失效,编码时找不到 id |
可堆叠的物品(石头、圆木这类)不做上述检查,直接清理。
因此,常规清扫只放过带数据的物品,其余全部清走。
常规清扫指令无法缓解服务器压力时的最终解决办法:
- 全服播报 20 / 10 / 5 / 3 / 2 / 1 秒倒计时
- 倒计时结束后清空所有掉落物
通过本方法清空的掉落物无法收入垃圾桶
清空完成后,全服广播「强制清扫执行完毕」(红色加粗)。
面向公益服务器的非商业兑换码功能。所有兑换码对全体玩家开放,每人每个码限兑一次,不支持按人发放或一次性码。
/cir giftCode—— 打开兑换界面(无权限要求)/cir manageGiftCode—— 打开管理界面,权限 4
兑换码可配置物品、经验值和状态效果。管理界面支持新建、作废、删除;作废后视同过期,删除会连同兑换记录一起清掉。
配置保存在 config/create_cir_addition/gift_codes.json,首次运行自动生成。兑换记录存在世界存档里。
两个界面打开前都会先弹出免责声明,说明本系统不支持任何商业性质的兑换码。
依据 Mojang 商业使用指南,服务器不得销售影响游戏平衡的内容。CIR 团队不支持一切商业性质的兑换码行为。
| 依赖 | 必需性 | 版本 |
|---|---|---|
| Minecraft | 必需 | 1.21.1 |
| NeoForge | 必需 | 21.1+ |
| Create | 必需 | 6.0.0 – 6.x |
| AE2 | 可选 | 19+(不装则量子环限制和发电机调节都跳过) |
- 下载
create_cir_addition-3.x.x.jar - 放进
mods/目录(若为服务器,客户端和服务端都要放!) - 启动一次,生成
config/create_cir_addition.toml - 按需调整配置,改完
/reload或重启
所有命令在 /cir 下。
3.4.6 起所有命令改为驼峰命名,旧名(
forcecleanup、trashbin、redstonelinkoptimization等)不再可用。
| 命令 | 权限 | 说明 |
|---|---|---|
/cir setHome <x> <y> <z> |
4 | 设置主基地(固定落在主世界) |
/cir home |
0 | 查看当前基地坐标(所有玩家可用) |
/cir quantum scan |
4 | 扫描当前维度已加载区域,把现有量子环补登记进表 |
/cir cleanup |
4 | 立即清理地面掉落物(旗帜、潜影盒、附魔物品会跳过) |
/cir forceCleanup |
4 | 强制清扫:倒计时后清空所有掉落物,不进垃圾桶 |
/cir trashBin |
0 | 打开垃圾桶(所有玩家可用) |
/cir giftCode |
0 | 打开兑换码界面(所有玩家可用) |
/cir manageGiftCode |
4 | 打开兑换码管理界面 |
/cir redstoneLinkOptimization <true|false> |
4 | 热切换红石终端优化 |
/cir ae2Generator |
4 | 查看两个 AE2 发电方块的当前状态 |
/cir ae2Generator crystalResonance <true|false> |
4 | 开关水晶谐振发电机 |
/cir ae2Generator vibrationChamber <low|normal|boost> |
4 | 切换谐振仓档位(Tab 补全) |
配置文件:config/create_cir_addition.toml
network = true # 网络压缩
create = true # Create 优化 mixin 总开关smartBlockInterval = 3
chainConveyorInterval = 2
basinCheckInterval = 5
mountedStorageSyncCooldown = 20quantumLimitNear = 2
quantumRadiusNear = 1024
quantumLimitFar = 4
quantumRadiusFar = 4096
otherDimensionLimit = 4
homeRadius = 256
quantumLimiterEnabled = true # 总开关,改这个必须重启
quantumLimiterEnabled只在服务器启动时读取一次。
/reload和配置热重载都会刻意忽略它。因为限制依赖一张持久化登记表,运行中途切换会让表内内容和游戏对不上:关掉时表还在(重新打开会把老记录当有效量子环),打开时现有量子环全部未登记(下次区块加载会被当新桥判一遍)。要改必须重启游戏。
redstoneLinkOptimization = true # 支持 /cir 指令热切换cleanupIgnoreNamed = true # 保护带自定义名称的物品
cleanupOnHighMspt = true # MSPT 到红色档(≥ 70)时自动清理msptWarnEnabled = true从旧版本升级时:
- 老的量子环不会自动登记。升级后进游戏跑一次
/cir quantum scan,把现有环补进表里,否则它们会被当成新桥重新判定一遍 - 如果你的存档里有大量量子环且已超出当前限制,建议先跑 scan 再改限制值
该项目由 CIR 服务器成员于 2025 年立项进行,后续因成员变动本项目被搁置,2026 年 11 月通过 DeepSeek v4.1 Flash 1017 模型结合此前开发计划和已完成代码补全,因此部分 JAVA 代码由 AI 生成。
本项目采用 CC BY-SA 4.0(署名—相同方式共享 4.0 国际)。
你可以自由地:
- 共享 —— 以任何媒介或格式复制、发行本作品
- 演绎 —— 修改、转换或以本作品为基础进行创作
但必须遵守以下条款:
- 署名 —— 必须给出适当的署名,提供指向本许可协议的链接,并说明是否作了修改。可以以任何合理的方式署名,但不得暗示作者为你或你的使用背书
- 相同方式共享 —— 如果你再混合、转换或以本作品为基础进行创作,必须基于与原作品相同的许可协议分发你的作品
完整法律条款见 LICENSE。
Create CIR Addition is a server-side add-on for Create-focused modpacks. It covers three areas:
- Performance — reduces the network sync and tick overhead of Create's block entities
- Rules — (optional) caps how densely AE2 quantum rings can be stacked, pushing players toward a proper logistics network instead of brute-force parallel bridges; and throttles AE2's own power generation so players fall back on CC&A stress-based generation
- Operations — MSPT warnings, emergency item cleanup, trash bin recovery
Each optimization maps to a specific piece of Create's internals, and every change exists to make a server easier to build and run. Nearly all of it is tunable through the config file.
- Fix a startup hang in RollingGate
1.1.0+build.66by dispatching GLFW window updates from the configuration-loading worker to the game thread without blocking loading. This patch is client-only and version-gated; dedicated servers do not load it. - Replace ThroughputQuest 1.0.0's calls to AdvancedAE's removed private mixin accessor with AE2 public getters, covering server watchers and client rendering. Enabled only when both
throughput_questandae2are installed; no third-party JAR changes are needed. - Enable the empty press-particle fix only for Create 6.0.10. Other Create versions skip this fix; existing basin optimizations retain their behavior.
- Upgrade the CIR payload protocol to 3.4.8. Updated servers accept 3.4.7 and 3.4.8 only. Older and unknown protocols are rejected, and other mods retain their original negotiation rules. Updated clients still cannot bypass strict negotiation on an older server.
3.4.7fixuses protocol3.4.7and is accepted. - Complete the English, Simplified Chinese and Traditional Chinese translations for AE2 generation controls, forced cleanup and toggle states.
CirMixinPlugin checks these compatibility patches at startup. No manual switch is needed, and optional integrations do not become required dependencies.
The empty basin/press-particle patch is a temporary workaround and can be removed after Create fixes the upstream bug. This does not apply to the separate ThroughputQuest or RollingGate compatibility fixes.
| Fix | Activation condition | Scope |
|---|---|---|
| Empty mechanical-press particles / disconnect when a basin is removed | The installed Create version is exactly 6.0.10 |
Other Create versions skip this patch; existing basin and other Create optimizations remain unchanged |
| ThroughputQuest legacy accessor compatibility | Both throughput_quest and ae2 are installed |
Covers server detection and client rendering; tested with 1.0.0. Only explicitly matched legacy calls are rewritten, so newer versions without those calls are left untouched |
| RollingGate window-setting startup hang | A client has rolling_gate version exactly 1.1.0+build.66 |
Dispatches window attribute updates to the game thread; dedicated servers do not load this patch |
Missing mods or unmatched versions cause the corresponding patch to be skipped automatically. ThroughputQuest uses mod-presence checks plus exact legacy-call matching rather than replacing the behavior of every version. Startup logs report whether each conditional patch is enabled.
If the basin under a mechanical press is destroyed at the exact moment the press runs, the server writes an item stack with count 0 into the block entity's particle sync packet. The client parses it as an empty stack and throws:
java.lang.IllegalArgumentException: Empty stacks are not allowed
which shows up as a "network protocol error" disconnect. Fixed in 3.4.7fix: empty stacks are stripped from the particle list before constructing particles.
Historical release 3.4.7fix uses payload channel version
3.4.7, so older clients can still connect; the mod list shows3.4.7fix.
| Target | What it does |
|---|---|
SmartBlockEntity |
Sync packet throttling (1/3), lazyTick rate scaled by player distance |
MountedStorageManager |
Longer sync cooldown, fewer repeated packets for mounted storage |
PackageEntity |
Fewer tracking updates for package entities |
BeltBlockEntity |
Belt tick optimization |
ChainConveyorBlockEntity |
Chain conveyor tick interval |
BasinBlockEntity |
Basin overflow check interval |
FunnelBlockEntity |
Funnel tick optimization |
All intervals are configurable; the defaults are values measured in practice.
Caches LinkBehaviour.isAlive() results per game tick.
Create's RedstoneLinkNetworkHandler.updateNetworkOf walks the entire same-frequency network on every call, performing four state lookups per node. With many links, or with chunks loading and unloading repeatedly, this becomes O(n²) work.
Signal timing is unaffected — getTransmittedStrength() is still read live; only the "is this node still alive" check is cached. Worst case, a link destroyed mid-tick leaves the network one tick later.
Toggle at runtime with /cir redstoneLinkOptimization true|false.
Create sync packets between client and server pick LZ4 or Zstd by size. Small packets pass through untouched, so compression cannot make them larger.
Requires AE2. Without it the feature is skipped entirely; nothing else is affected.
Caps how densely ME quantum rings (ae2:quantum_ring + ae2:quantum_link) can be placed, so players lean on Create's physical systems instead:
- Overworld: at most 2 within 1024 blocks and at most 4 within 4096 blocks (both conditions must hold)
- Other dimensions: at most 4 per dimension, distance-independent
- Base exemption: unlimited within 256 blocks of the main base
The first time a ring multiblock completes, the player is notified on the spot, along with how many placements remain nearby.
A ring that breaks the limit is dismantled the instant it completes, leaving a single obsidian block and a visual-only lightning strike.
Counting runs off a persistent registry of ring positions rather than chunk scanning — a 4096-block radius covers 512×512 chunks, so live scanning is simply not viable.
The base can be set with a command (op level 4) and queried by anyone (op level ≥ 0). /cir quantum scan can be used to register every loaded ring into the table.
Scanned positions are written to disk rather than kept in memory, so they survive a restart.
Limits, the base exemption radius, and whether the feature is enabled at all are configurable in config/create_cir_addition.toml.
P.S. To keep players from sidestepping placement detection with pistons, block-entity conversion or similar tricks, the mod does not hook block placement at all. It hooks the moment a ring multiblock completes — which also covers a ring that was loaded from an unloaded chunk — and then compares it against the scanned registry to decide whether it gets the notification or the axe.
Requires AE2. Without it the command reports "AE2 not found"; nothing else is affected.
AE2 ships two blocks that generate power for an ME network. This mod exposes both at runtime, with no need to edit ae2-common.toml and no restart:
| Block | Name | Mode |
|---|---|---|
ae2:crystal_resonance_generator |
Crystal Resonance Generator | on / off |
ae2:vibration_chamber |
Vibration Chamber | three tiers: low / normal / boost |
Vibration chamber tiers scale the three underlying values against whatever was in effect before the first switch:
| Tier | Fuel factor | Min AE/t | Max AE/t |
|---|---|---|---|
low |
×1/4 | ×1/4 | ×1/4 |
normal |
×1 | ×1 | ×1 |
boost |
×4 | ×4 | ×4 |
With AE2's defaults of 5 / 4 / 40, the tiers come out as 1.25 / 1 / 10, 5 / 4 / 40 and 20 / 16 / 160.
The baseline is snapshotted into create_cir_addition.toml (the ae2Vibration*Snapshot entries) the first time a tier is applied. If you have hand-tuned ae2-common.toml to 10 / 8 / 80, normal restores those values rather than AE2's factory defaults.
Changes take effect immediately, including on machines already placed. AE2 caches these three values in final fields on the block entity and never re-reads the config after construction; this mod overwrites that cache and reports in chat how many chambers it refreshed.
The vibration chamber cannot be driven to zero. AE2's own floors are baseEnergyPerFuelTick ≥ 0.1 and maxEnergyPerGameTick ≥ 1, so low is a 1/4 throttle, not a disable. Shutting it down entirely still requires removing the recipe or blocking interaction.
These values live in AE2's
ae2-common.toml, so the adjustment is global — switching one tier updates every vibration chamber on the server.
On first world load the spawn point becomes the base. Change it with /cir setHome (admin permission required).
There is exactly one base in the world. It lives in the Overworld, and only rings in the same dimension benefit from the exemption.
Samples server MSPT every 30 seconds, four tiers: 40 / 45 / 50 / 70 (white → yellow → gold → red).
A reading above the line does not broadcast immediately — it waits 3 seconds and samples again:
- Second reading still in the same tier or higher → broadcast using the second reading's value and tier
- Second reading fell back → complete silence
The repeat sample exists so that an autosave or an incidental hitch does not trip the alarm; only sustained load gets reported.
At ≥ 70 every confirmed reading broadcasts until MSPT drops back below it.
The first three tiers all sit inside "still has headroom per tick" territory (50 MSPT is exactly 20 TPS); their role is to surface a trend early. At 70 MSPT stutter is already plainly visible.
No timer-based cleanup. Two triggers only:
- Automatic, once MSPT reaches the red tier (≥ 70) and is confirmed
- Manual, via
/cir cleanup, or invoked indirectly through external wrappers such as MCDR or KubeJS
Swept items are not destroyed — they go into a trash bin valid for 1 hour. Players reclaim them with /cir trashBin, or by clicking the trash-bin link in chat.
When /cir cleanup is run manually, this message is broadcast to the whole server with a clickable trash bin button.
Items carrying a custom name are protected by default (configurable).
To avoid the trash bin getting a client kicked while encoding items, the following are not cleaned up at all — they stay on the ground for players to pick up themselves:
| Skipped | Reason |
|---|---|
| All banners | Patterns are static registry entries that may differ between client and server |
| The 17 vanilla shulker boxes | Their contents travel with the item |
| Anything enchanted | After a datapack reload the old enchantment reference goes stale and cannot be encoded |
Stackable items (stone, logs and the like) skip all these checks and are cleared directly.
As a result, the regular cleanup only spares items that carry data; everything else is taken.
The final recourse when the regular cleanup command can no longer relieve server load:
- Broadcasts a countdown at 20 / 10 / 5 / 3 / 2 / 1 seconds
- When it reaches zero, every dropped item is cleared
Dropped items cleared this way cannot be retrieved from the trash bin.
Once the clear is done, "Force cleanup complete." is broadcast to the whole server in bold red.
A non-commercial gift code feature for community servers. Every code is open to all players and can be redeemed once per player; per-player or single-use codes are not supported.
/cir giftCode— open the redeem screen (no permission needed)/cir manageGiftCode— open the management screen (permission 4)
A code can grant items, experience and status effects. The management screen supports creating, disabling and deleting codes; a disabled code counts as expired, and deleting removes its redemption records too.
Codes live in config/create_cir_addition/gift_codes.json, generated on first launch. Redemption records are stored in the world save.
Both screens show a disclaimer first, stating that this system does not support gift codes of any commercial nature.
Per Mojang's Commercial Usage Guidelines, servers may not sell content that affects game balance. The CIR team does not support gift code activity of any commercial nature.
| Dependency | Required | Version |
|---|---|---|
| Minecraft | Yes | 1.21.1 |
| NeoForge | Yes | 21.1+ |
| Create | Yes | 6.0.0 – 6.x |
| AE2 | Optional | 19+ (quantum limiter and generator control are skipped without it) |
- Download
create_cir_addition-3.4.2.jar - Drop it into
mods/— on a server, both the client and the server need it - Launch once to generate
config/create_cir_addition.toml - Adjust the config as needed, then
/reloador restart
All commands live under /cir.
Since 3.4.6 all commands use camelCase. The old names (
forcecleanup,trashbin,redstonelinkoptimization, etc.) no longer work.
| Command | Permission | Description |
|---|---|---|
/cir setHome <x> <y> <z> |
4 | Set the main base (always lands in the Overworld) |
/cir home |
0 | Show current base coordinates |
/cir quantum scan |
4 | Scan loaded chunks of this dimension and register existing rings |
/cir cleanup |
4 | Sweep dropped items immediately (banners, shulker boxes and enchanted items are skipped) |
/cir forceCleanup |
4 | Force sweep: countdown, then clear every dropped item without binning it |
/cir trashBin |
0 | Open the trash bin (available to everyone) |
/cir redstoneLinkOptimization <true|false> |
4 | Toggle the redstone link cache at runtime |
/cir ae2Generator |
4 | Show the current state of both AE2 generators |
/cir ae2Generator crystalResonance <true|false> |
4 | Enable or disable the crystal resonance generator |
/cir ae2Generator vibrationChamber <low|normal|boost> |
4 | Switch the vibration chamber tier (tab-completed) |
File: config/create_cir_addition.toml
network = true # network compression
create = true # master switch for the Create optimization mixinssmartBlockInterval = 3
chainConveyorInterval = 2
basinCheckInterval = 5
mountedStorageSyncCooldown = 20quantumLimitNear = 2
quantumRadiusNear = 1024
quantumLimitFar = 4
quantumRadiusFar = 4096
otherDimensionLimit = 4
homeRadius = 256
quantumLimiterEnabled = true # master switch, restart required
quantumLimiterEnabledis read once at startup.
/reloadand config hot-reload deliberately ignore it. The limiter depends on a persistent registry, and flipping the switch mid-run leaves the table out of sync with the world: turn it off and the table stays behind (switching back on would treat stale entries as live rings); turn it on and every existing ring is unregistered (the next chunk load judges them as new).Changing it requires a restart.
redstoneLinkOptimization = true # the /cir command can toggle this at runtimecleanupIgnoreNamed = true # protect items with a custom name
cleanupOnHighMspt = true # auto-clean once MSPT hits the red tier (≥ 70)msptWarnEnabled = trueUpgrading from an older version:
- Existing rings are not registered automatically. After upgrading, run
/cir quantum scanonce in-game to pull them into the table; otherwise they are judged as new rings - If the save already contains more rings than the current limits allow, run scan before tightening the limits
This project was started by CIR server members in 2025 and later shelved due to membership changes. In November 2026, the previously planned design and the existing code were completed with the DeepSeek v4.1 Flash 1017 model, so part of the Java code is AI-generated.
This project is licensed under CC BY-SA 4.0 (Attribution-ShareAlike 4.0 International).
You are free to:
- Share — copy and redistribute the material in any medium or format
- Adapt — remix, transform, and build upon the material
Under the following terms:
- Attribution — you must give appropriate credit, link to the license, and indicate whether changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use
- ShareAlike — if you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original
Full legal text in LICENSE.