⚠️ 已整合至 Drakes-Suites(Chagui68 的多宇宙套件):
所有针对 Paper/Purpur 1.21.11+ 的活跃开发与官方支持均在 Drakes-Suites monorepo 内的 drakes-multiverse 模块中进行,保留了 Chagui68 的所有权与设计主权。
? MultiverseNets
面向 Paper 的独立数字物流网络与大规模存储——无需 Slimefun。
Wiki: English · Español · 合成表: EN · ES
? MultiverseNets 是什么?
MultiverseNets 实现了一个 100% 独立的网络式物流系统:不依赖 Slimefun,也无其他任何依赖项。每个设备均为自定义物品(通过 PDC 标识),放置后的设备状态保存在世界文件夹内的区域文件中(无每区块数量限制),且网络的存储空间是虚拟且持久的。
一个网络由 一个网络控制器(Network Controller)加上与其面面相接的所有 MultiverseNets 方块 组成。线缆是最经济的连接方式,但每个设备本身均可导电:抓取器接触存储单元、再接触控制器的情况下,它们即构成一个网络。
? 快速上手
- 放置一个 网络控制器(Network Controller)。放置者将成为该网络的所有者。
- 将其与 线缆 和设备连接。至少添加一个 量子存储单元(Quantum Cell)(或无限桶)——没有存储,网络便无处存放物品。
- 右键点击 网络终端(Network Terminal)(或控制器的菜单)以查看和使用存储空间。
- 将 抓取器(Grabber) 放置在箱子旁以导入物品,将 推送器(Pusher) 放置在箱子旁以导出物品。通过右键点击配置它们的过滤规则。
- 如果某些设备无法连接,请检查
/mvnets doctor 命令或使用 网络探针(Network Probe)。
上述所有设备的 ID 均可通过 /mvnets give <id> 指令获取(按 Tab 键可自动补全 ID)。
所有设备的合成配方请参阅 Recipes (EN) /
Recetas (ES)。
? 机器参考
各项速率均为 config.yml 中的默认值;每项均可配置(详见下方 Configuration)。“周期”指一次传输循环(network.op-interval-ticks.transfer,默认为 5 tick)。
?️ 核心与访问
| 设备 |
ID · 材质 |
功能 |
使用方法 |
| 网络控制器 |
mvn_controller · Lodestone |
网络的根节点。所有扫描均从此处开始(通过连接的方块进行广度优先搜索,最多可达 network.max-nodes 个节点)。记录其所有者(放置者),并显示带有状态、节点数和存储总量的浮动全息图。内存模块不再放入控制器:它们应放入 DRAM 扩展坞。 |
右键点击:查看状态和路由器状态。它不接受模块。旧控制器内的模块会被自动取出连同其中的物品一起,并作为临时物品等待在终端中:在那里点击它并将其安装到 DRAM 扩展坞中。破坏控制器会掉落任何未被收集的模块。每个网络只能有一个控制器:连接到相同线路的第二个控制器会被报告为 foreign controller(参见 共享总线)。 |
| 网络线缆 |
mvn_cable · Glass |
连接设备。自身无逻辑功能。它可以伪装成任意固体方块,从而使一排线缆隐藏在墙内。它还提供16种颜色(染色玻璃)以区分建筑的不同区域:4 根任意颜色的线缆 + 染料 = 4 根该颜色的线缆。每种颜色的连接方式与普通线缆相同;断开的线缆会掉落其颜色。 |
空手右键点击可查看其是否连接到控制器并打开其菜单。将方块放入伪装槽,线缆外观将与该方块完全一致:方块被保留在线缆内部,不会被消耗。取回后线缆恢复为玻璃状态;破坏线缆会同时掉落线缆和方块。仅限不掉落、不自变或具有库存的实心完整方块。手持方块时右键点击会放置该方块。 |
| 网络终端 |
mvn_terminal · Beacon |
存储网格:网络中的每项物品(缓存、量子细胞、桶、贪婪细胞、Slimefun 桶)。顶行包含视图:网络存储、清除模式(被清除器锁定的物品)、流体和5 个自定义页面(你的收藏),以及输入槽。底行包含工具:页面、排序、搜索、网络概览、固定模式、存入库存和帮助书。 |
左键点击获取 1 个,右键点击获取一组,Shift+点击发送到你自己的背包;将光标上的物品点击到网格中以存储它。Shift+左键点击你的物品(或在输入槽中丢弃它们)以存储它们。将物品固定到自定义页面只需悬停并按下 1-5,或在固定模式下操作;在自定义页面上的物品上按 Q 取消固定。自定义页面仅显示其固定的物品(即使缺货时也是如此),因此任务只会显示其所需内容。右键点击页面标签可重命名,Shift+右键点击可清空。页面按玩家保存,并在任何终端上生效。桶/蜂蜜瓶进入流体存储。每项物品显示其在网络中的总量及其存储位置的细分(DRAM、量子细胞、无限桶、贪婪缓冲器、Slimefun 桶);各部分之和等于总量,不会重复计数。从旧控制器恢复的模块首先作为临时物品出现。 |
| 无线终端 |
mvn_wireless_terminal · 物品(下界之星) |
远程打开网络终端。 |
Shift+右键点击控制器或终端以绑定它,然后在空气中右键点击。没有网络路由器时,它仅在同一世界且距离 wireless.local-range-without-router(64)格范围内工作。战斗开始后 10 秒内不可用,且仅在你可以访问网络土地时使用。 |
| 网络路由器 |
mvn_router · Lightning Rod |
解除其所在网络的无线终端限制:任意距离和任意世界。 |
将其连接到网络中的任意位置。 |
| 网络监视器 |
mvn_monitor · Respawn Anchor |
实时诊断面板:按类型统计的节点数、存储使用情况、错误信息。 |
右键点击;打开时会持续刷新。 |
| 网络探针 |
mvn_probe · 物品(望远镜) |
回答“是否已连接?”:网络大小、控制器位置、扫描错误和你点击方块的保护切断情况。 |
右键点击任意方块。 |
| 网络状态灯 |
mvn_status_light · Lime/Red Stained Glass |
放置在网络方块的任意一侧,可从远处显示该方块是否连接到控制器:绿色表示已连接,红色表示未连接。它不属于网络的一部分,也永远不会连接两个网络。 |
将其放置在任意网络方块上;每秒检查一次。 |
? 内存:DRAM 扩展坞与模块
| 设备 |
ID · 方块 |
功能 |
使用方法 |
| DRAM 存储柜 |
mvn_dram_bay · 上蜡的铜灯 |
网络方块,可容纳最多 18 个内存模块,每个模块拥有独立的库存。这些模块即为存储空间:安装后,其库存即成为网络的一部分。你可以放置任意数量的存储柜。 |
手持一个模块右键点击存储柜,即可将其安装到下一个空闲槽位;或右键点击以打开其菜单:菜单顶部显示存储柜摘要,下方有 18 个模块槽(每个均带有填充进度条),以及两个仪表盘分别显示物品和流体存储的占用情况。可通过鼠标拖拽或 Shift+左键进行安装;点击已安装的模块可将其取出,并保留其全部库存。破坏该方块(或 Rake)会掉落存储柜及所有模块,且保留完整库存。 |
| 物品内存模块 |
mvn_cache_l1 · _l2 · _l3 · _dram · _quantum · items |
多物品存储:总计可存储 2,048 / 8,192 / 32,768 / 131,072 / 524,288 个物品(对应 virtual-cache.tier-1 … tier-5),支持任意类型的混合存储。 |
将其安装在 DRAM 存储柜中。取出时会带走其中的所有物品:这些物品会从原网络中消失,并出现在你将其安装的 DRAM 存储柜所属的网络中。在合成表中升级已加载的模块会保留其内的物品。 |
| 流体 DRAM 模块 |
mvn_fluid_dram · item (Heart of the Sea) |
仅流体模块:可同时容纳多种流体,总计上限为 fluids.dram-capacity-mb(512,000 mB = 512 桶)。 |
与物品模块类似:它需安装在 DRAM 存储柜中,为其所在网络的流体存储增加容量;取出时会将其中的流体带至另一个网络。 |
| DRAM 卸载器 |
mvn_module_unloader · 上蜡的风化铜灯 |
清空卡片(内存模块)中的内容到网络中:每次循环可处理最多 9 张卡片,每张卡片转移 transfer.module-items-per-op 个物品(4,096)和 transfer.module-fluid-per-op mB(64,000)。与 DRAM 存储柜不同,内部的卡片不作为网络存储空间。网络无法存储的部分将留在卡片上,并尝试处理下一项物品,从而使卡片尽可能被清空。需要网络中有可用空间。 |
手持一张卡片右键点击它,或打开其菜单:包含 9 个带有进度显示的卡片槽,以及**“取空卡片”**按钮用于收集所有已完成的卡片。 |
| DRAM 装载器 |
mvn_module_loader · 上蜡的氧化铜灯 |
向一张卡片填充单一物品(或流体,针对流体 DRAM 模块),从网络中提取,直到达到你选择的数量后停止。仅插入卡片不会触发任何操作。 |
打开界面,放入一张卡片,用目标物品(流体 DRAM 模块使用流体桶)点击目标槽位,设置数量(使用 ±64/±1k/±10k 按钮,Shift 乘以 100,或直接点击并输入 1m、500k、max),然后按下开始。示例:一张空的量子卡片 + 圆石 + 500k + 开始 = 一张准备好出售的卡片。其目标和数量会在方块被破坏时随方块一起移动。 |
? 物品存储
| 设备 |
ID · 方块 |
功能 |
使用方法 |
| 量子单元格 T1–T6 |
mvn_cell_t1 … mvn_cell_t6 · 陶瓦(普通、橙色、黄色、 lime、青色、紫色) |
每个单元格仅存储一种物品类型:分别为 65,536 / 262,144 / 1,048,576 / 16,777,216 / 268,435,456 / 2,000,000,000 个物品。空单元格会接收第一个无处存放的物品类型。 |
连接至网络。右键点击可查看或管理其内容。破坏方块会使货物保留在物品形式中。使用量子工作台或在合成表中(单元格周围环绕 8 颗钻石)提升一个等级,货物将被保留。 |
| 无限桶 |
mvn_infinity_barrel · 木桶 |
与单元格相同——仅存储一种物品类型,容量为 barrel.capacity(2,000,000,000),但在 emptied 后仍保持注册状态。具有自身 ID 的物品(如 Slimefun 和其他插件中的物品)通过其 ID 和可见文本识别,因此无论名称或描述如何存储,取出的物品总会返回其中。 |
右键点击:手持物品右键点击 Set Item 以注册该物品;手持空光标右键点击 Set Item 清除注册(仅在桶为空时有效)。漏斗不与其交互(见下文)。 |
| 贪婪单元格 |
mvn_greedy_cell · 黏液块 |
带有过滤器时:作为优先级汇点。匹配其过滤器的传入物品优先存入此处,每个循环从网络中拉取多达 512 个额外物品,并向相邻的非网络容器(箱子、Slimefun 机器)推送多达 256 个物品。可容纳多种类型,总计上限为 greedy.capacity(262,144)。无过滤器时:作为通用溢出存储,仅在其他所有存储已满时使用。 |
右键点击以设置过滤器并查看其缓冲区。它作为内部过滤器工作:定义在其过滤器中的物品始终保留1 个单位在内部,无论是什么将其取出(推板、终端、合成、其自身的推送到容器)。如果网络的推板在其白名单中包含该物品,贪婪单元格会将所有物品(包括最后 1 个单位)释放给单元格,并在该推板存在期间停止接收它。无线桥接不会从中提取物品。 |
| 容器连接器 |
mvn_container_connector · 赭色萤石 |
将与其接触的原版容器(箱子、陷阱箱、铜箱、木桶、潜影盒)链接到其网络:终端会显示其物品,存入操作会填满它们,取出操作会清空它们。它们是双向存储的最后一环(见下方的顺序说明)。物品按原样移动;潜影盒永远不会进入另一个潜影盒。双联箱只计一次。 |
将其连接到网络,并在任意侧面放置容器。来自同一网络的抓取器、推板和贪婪单元格会忽略已链接的容器(因为它们已是其存储的一部分)。在有主权的土地上,容器必须位于网络可用的土地内。 |
| 量子工作台 |
mvn_quantum_workbench · 脑珊瑚块 |
将量子单元格 T1–T5 升级到下一级,同时保留其货物。 |
将单元格放在中心,周围环绕 8 颗钻石,点击 Entangle & Upgrade,取出结果。 |
? 流体
流体拥有独立的存储空间,与物品分离:量子流体细胞和安装在 DRAM 存储柜中的流体 DRAM 模块。
| 设备 |
ID · 方块 |
功能 |
使用方法 |
| 量子流体舱 |
mvn_fluid_cell · 海晶砖 |
存储一种流体——水、熔岩、牛奶、细雪或蜂蜜,容量上限为 fluids.cell-capacity-mb(64,000 mB = 64 桶)。网络中所有流体舱共同构成其流体存储。 |
使用装有流体的桶/蜂蜜瓶右键点击以注入该舱;使用空桶右键点击以填充(仅限水、熔岩、牛奶、细雪)。或使用终端的流体页面:存入桶/瓶子,用空桶取出(蜂蜜需用玻璃瓶取出)。 |
| 液体泵 |
mvn_liquid_pump · 蓝色染色玻璃 |
每个周期直接从其正下方抽取一个水源方块的水或熔岩(1,000 mB)。仅当整个 1,000 mB 能容纳在网络中时,该方块才会被移除。 |
将其放置在液体上方。右键点击选择 ANY / WATER / LAVA。 |
? 物品传输
| 设备 |
ID · 方块 |
功能 |
使用方法 |
| 简易抓取器 |
mvn_grabber · 侦测器 |
从相邻容器导入物品到网络:每个周期最多 128 个同类型物品,通过所有六个面进行。如果是熔炉,则只提取结果。如果网络不接受某个物品(无空间或配额已满),该物品会退回其槽位,抓取器继续处理下一个物品,因此一个不需要的物品永远不会阻塞箱子。如果旁边有一个未连接到网络的量子舱或无限桶,它也会清空它们(抓取器不会将该存储拉入网络)。 |
右键点击打开过滤器(白名单/黑名单)。空过滤器 = 所有物品。 |
| 高级抓取器 |
mvn_grabber_ht · 粘性活塞 |
同上,×8倍(transfer.ht-multiplier):每个周期 1,024 个物品,并且可以限制为单一方向。 |
过滤器菜单 + 方向选择器。 |
| 简易推送器 |
mvn_pusher · 标靶 |
将物品从网络导出到相邻容器:每个周期最多 128 个物品,通过所有六个面(它没有方向选择器:如需单侧请使用高级推送器)。它绝不会将任何物品放入其他网络方块中。 |
过滤器决定哪些物品离开,而不是去向哪里。空白名单 = 空闲(因此新的推送器永远不会清空网络);黑名单 = 除列出的物品外的所有物品:被你列入黑名单的物品将保留在网络中。 |
| 高级推送器 |
mvn_pusher_ht · 活塞 |
同上,×8倍,并带有方向选择器,仅向该侧面投递。 |
过滤器菜单 + 方向选择器。对于机器,请选择机器的对应面。 |
| 网络吸尘器 |
mvn_vacuum · 海绵 |
每 10 个游戏刻在 vacuum.radius(4 格)范围内拾取掉落物品并将其吸入网络。 |
可选过滤器。无法容纳的物品将留在地面上。 |
| 网络净化器 |
mvn_purger · 岩浆块 |
每个周期删除最多 128 个符合过滤器的物品。 |
没有过滤器时它什么也不会删除,这是故意设计的。 |
| 网络配额限制器 |
mvn_limiter · 标靶 |
限制网络可持有的某种物品的数量上限。每次存入操作(抓取器、吸尘器、终端、合成结果、无线桥接)都会在达到上限时停止。 |
右键点击:设置目标物品、限额以及开/关。同一物品多个限制器:最低限额生效。 |
| 配额管理器 |
mvn_quota_manager · 翠色荧光蛙灯 |
提供其网络中每个配额限制器的统一界面:显示每种受限物品及其限额、网络库存、使用进度条以及是否已启用,还有剩余多少可用限制器。 |
右键点击它。添加物品:使用“添加”按钮(鼠标指针上的物品)添加到空闲的限制器上,或在背包中 Shift+右键点击:它会占用一个空闲的配额限制器(物品仅为复制);如果没有空闲限制器,则无法添加,因此需放置更多限制器以限制更多物品。对已受限物品操作:左键点击输入限额(500、64k、1m),Shift+右键点击开启/关闭,右键点击移除该物品(限制器恢复空闲),用其他物品点击则会替换它。 |
| 无线发射器 |
mvn_transmitter · 引导装置 |
无线桥接的一端。如果它持有与接收器的链接,它将把通过其过滤器的最多 128 个物品在每个周期内推送至接收器的网络。 |
右键点击:过滤器菜单,以及一个按钮可打开其自身网络的终端。链接:Shift+右键点击持有接收器物品的已放置发射器,或持有发射器物品的已放置接收器。 |
| 无线接收器 |
mvn_receiver · 红石灯 |
另一端。如果它持有与发射器的链接,它将从发射器的网络中拉取通过其过滤器的最多 128 个物品到其自身网络中。只要另一端所在的区块已加载,即可跨距离和维度工作。 |
右键点击:过滤器菜单,以及一个按钮可打开远程网络的终端。空白名单 = 没有任何物品穿过,这是故意设计的。 |
抓取器、推送器和贪婪舱兼容的容器包括:箱子、陷阱箱、 barrels(木桶)、漏斗、发射器、投掷器、熔炉、高炉、烟熏炉、酿造台、雕纹书架、潜影盒,以及——安装 Slimefun 后——Slimefun 机器(仅限机器声明用于输入/输出的槽位)。绝不对其他 MultiverseNets 方块操作。
推送器的工作方式(专为喂养机器如 Slimefun 冶炼炉设计):
- 每个槽位最多一组。如果在单个槽位中使用了包含 128 或 1,024 个物品的周期,导致超过一组的物品丢失,这就是曾经清空整个网络的原因。
- 使用多种物品的白名单(例如合金的三种原料),每种物品将获得目标槽位的份额(9 个槽位 / 3 种原料 = 各 3 个),并在同一周期内轮流服务。这样第一种原料就不会淹没机器并锁定配方。
- 投入熔炉、高炉或烟熏炉:从上方投入时,所有物品进入输入槽;从侧面投入时,燃料进入燃料槽,其余物品进入输入槽。绝不会进入结果槽。
- 无法容纳的物品会返回网络;不会有任何物品丢失。
针对在同一方块内接收和输出物品的机器的小贴士(例如熔炉在没有输出箱子时会将产物放入发射器):添加一个输出箱,将高级抓取器指向该箱子,并将高级推送器对准发射器。如果有一个面向发射器的抓取器,它也会取回你刚刚推送进去的原料。
漏斗: 漏斗(以及漏斗矿车)不会与任何 MultiverseNets 方块交互,既不能插入也不能提取。曾经,位于无限桶上方的漏斗能够删除其整组物品。
?️ 合成
| 设备 |
ID · 方块 |
功能 |
使用方法 |
| 蓝图 |
mvn_blueprint · 物品 (书) |
一种配方:包含完整的 3×3 网格及其结果数据(PDC)。合成过程不会消耗它。 |
在配方编码器中编码并安装到合成器中。安装会将蓝图移入合成器;移除、替换或点击清除全部则将其返还。 |
| 配方编码器 |
mvn_encoder · 锻造台 |
在 3×3 模板网格中构建配方(点击仅标记槽位,不消耗物品),并将其写入蓝图(空白或已编码的)。 |
填满网格,将蓝图放入蓝色槽位,按下编码。点击已编码的蓝图会将其配方加载到网格中。留在槽位中的蓝图会存储在方块内(同一时间只有一名玩家可见)。 |
| Slimefun 配方编码器 |
mvn_sf_encoder · 附魔台 |
用于 Slimefun 配方的相同功能。留在槽位中的蓝图也会存储在方块内,因此你不必每次都携带空白蓝图。 |
需要 Slimefun;可通过 slimefun-machines.encoder(或通过 slimefun-machines.enabled 禁用所有 Slimefun 机器)禁用。 |
| 自动合成器 |
mvn_crafter · 合成台 |
每 20 个游戏刻尝试一次每个已安装的原版蓝图(最多 crafter.max-recipes,即 18 个)。全有或全无机制:如果缺少任何原料,则不取走任何东西;如果结果无法容纳,则整个合成被撤销。 |
右键点击,放入蓝图。拒绝 Slimefun 蓝图。 |
| Slimefun 自动合成器 |
mvn_sf_crafter · 哭泣的黑曜石 |
同上,并接受Slimefun 和原版蓝图:可以在同一台机器中混合使用两者。 |
完全禁用(包括配方、放置、菜单和合成)通过设置 slimefun-machines.crafters: false 或 slimefun-machines.enabled: false。 |
| 库存合成器 |
mvn_stock_crafter · 织布机 |
与自动合成器相同,但如果网络中已经持有 64 个其产出物,则跳过该蓝图。 |
仅限原版蓝图。 |
| Slimefun 库存合成器 |
mvn_sf_stock_crafter · 紫水晶块 |
与库存合成器相同,但支持Slimefun 和原版蓝图。 |
像 Slimefun 自动合成器一样禁用。 |
| 请求合成器 |
mvn_request_crafter · 箭袋桌 |
持有仅在请求终端上按需合成的蓝图(永远不会自动合成)。 |
像在自动合成器中一样安装蓝图。 |
| Slimefun 请求合成器 |
mvn_sf_request_crafter · 紫珀柱 |
同上,支持 Slimefun 和原版蓝图。 |
— |
| 请求终端 |
mvn_request_terminal · 讲台 |
列出网络中请求合成器可以制作的所有物品,并按需合成,利用网络的库存解决链式反应(原木 → 木板 → 合成台)。 |
左击获取 1 组,Shift+左击获取 10 组,右击获取 64 组,Shift+右击会在聊天栏询问数量。切换交付到你的背包或网络中。 |
| 网络合成网格 |
mvn_crafting_grid · 制图台 |
一种从网络中提取原料的合成台;模板网格存储在方块内。 |
右键点击,设置网格,进行合成。 |
? 工具
| 设备 |
ID · 方块 |
功能 |
使用方法 |
| 配置扳手 |
mvn_configurator · 物品 (比较器) |
将一个设备的过滤器(精确模板、材料和白名单/黑名单模式)复制到另一个设备。 |
Shift+右键点击可过滤的设备以复制,右键点击另一设备以粘贴。 |
| 网络耙子 |
mvn_rake · 物品 (枯死灌木) |
瞬间拆解节点并将其连同其状态(过滤器、蓝图、绑定)返还给你。拥有 250 次使用次数 (rake.uses)。 |
右键点击节点。它会拒绝控制器和仍持有物品或流体的存储设备。 |
? 组件
基础设备合成所需的中间部件,以确保没有设备配方会与原版配方冲突。它们是手持物品:不可放置或使用,且没有任何原版配方接受它们。
使用旧设备配方编码的蓝图不再有效:请重新编码。它们的配方位于 Recipes & functions。
| 组件 |
ID · 物品 |
用于合成 |
| 硅晶圆 (×2) |
mvn_silicon_wafer · 海晶晶体 |
网络电路、存储矩阵、空白蓝图 |
| 网络电路 (×2) |
mvn_network_circuit · 海晶碎片 |
控制器、电缆、终端、简单抓取器、简单推送器、真空机、净化器、配额限制器、监视器、探针、两种配方编码器、配置扳手、容器连接器;逻辑处理器、存储矩阵 |
| 逻辑处理器 |
mvn_logic_processor · 潜影壳 |
控制器、自动合成器和 Slimefun 自动合成器、两种请求合成器、请求终端、合成网格;量子核心 (×2) |
| 存储矩阵 |
mvn_storage_matrix · 唱片碎片 |
量子单元 T1、无限桶、贪婪细胞、量子流体细胞、DRAM 扩展坞、L1 CPU 缓存模块 |
| 传输线圈 (×2) |
mvn_transfer_coil · 绊线钩 |
简单和高级抓取器、简单和高级推送器、真空机、液体泵、容器连接器 |
| 量子核心 |
mvn_quantum_core · 回声碎片 |
无线终端、无线发射器、无线接收器、网络路由器、量子工作台 |
? GeneticChickengineering
| 设备 |
ID · 方块 |
功能 |
使用方法 |
| Genetic Chicken Sorter(基因鸡分拣器) |
mvn_chicken_sorter · Hay Bale(干草捆) |
一台专门用于处理 GeneticChickengineering 附加模组中口袋鸡的机器。它会读取鸡的基因,并仅移动符合所有规则的鸡;其他任何物品都会被忽略。每个周期最多处理 16 只鸡。 |
右键点击。菜单从上到下依次为:控制栏(开始/停止、方向为将网络 → 方块 Push(推送)或方块 → 网络 Pull(拉取)、侧面、一本摘要书,用通俗语言说明当前哪些鸡可以通过,以及帮助信息)、接受的产品(18 个槽位,显示每种产品对应的物品;鼠标悬停有口袋鸡时点击一个槽位,或在背包中按住 Shift+点击一只鸡,再点击一个产品以移除它;空槽 = 接受任何产品)和按层级分组的基因规则(最小值/最大值;隐性基因、特殊物种 7-9)、基因(最小 DNA 强度 0-6,仅限纯合基因)和身份(已测序/未测序 DNA、成年/幼年)。每条规则的名称和堆叠数量都会显示其数值,并在激活时发光:左键 +1,右键 -1,Shift+点击重置。层级范围不能留空。底行包括:清除产品、重置基因规则、关闭。默认处于停止状态:设置完成后需手动开启。 |
安装此附加模组后,每只鸡都是独一无二的物品(携带自己的 DNA)。网络不再将两只不同的鸡合并为一组:以前可能会出现一只鸡带有另一只鸡的 DNA 的情况。
可过滤的设备:Grabbers(抓取器)、Pushers(推送器)、Vacuum(吸尘器)、Purger(清除器)、Greedy Cell(贪婪存储单元)、Wireless Transmitter and Receiver(无线发射器和接收器)。它们均支持白名单和黑名模式,并且在 Grabber/Pusher 的菜单中点击某个面按钮会打开该面上的容器。
? 物品在网络内部及网络之间的移动方式
1. 什么属于一个网络
在每次扫描时,控制器会逐一检查所有相连的 MultiverseNets 方块,从面到面进行遍历。当一个节点被放置或破坏后,其所在网络会立即被扫描;在 network.scan-inticks 时间内,如果网络可能发生变化(例如其部分区块加载了,或者旁边放置/破坏了 Slimefun 电缆或桶),也会触发扫描;否则仅在每隔 network.full-rescan-ticks 时执行一次完整重新扫描。扫描过程如下:
- 不会加载区块——未加载区块中的节点暂时不属于网络,直到它们被加载;
- 从内存中读取每个相邻方块(只需一次查找,无需解码),因此无论区块密集还是稀疏,扫描成本相同;
- 遇到另一个控制器时会停止(
foreign controller at x,y,z);
- 绝不会从 Grabber(抓取器)进入 Quantum Cell(量子存储单元)或 Infinity Barrel(无限桶):如果一个 Grabber 接触其中一个,就像箱子一样将其清空到网络中。如果用电缆连接这些存储设备,则它们成为网络存储的一部分,而 Grabber 不会操作它们;
- 遇到网络所有者无法使用的土地时会停止(参见 Land protection);
- 当安装了 Slimefun 时,还会遍历 ID 包含
CABLE 或 BRIDGE 的 Slimefun 方块,并将与其接触的 Slimefun 桶加入存储系统。
不存在每个节点“我属于哪个网络”的状态:拓扑结构会在每次扫描时从头重建,因此节点永远不会指向一个已经不存在的网络。
2. 内部存储及其顺序
网络的物品存储由五个内部存储组成。每次存入操作——无论是来自抓取器、吸尘器、终端、合成结果还是无线桥接——首先会检查 配额限制器(Quota Limiters),然后按以下顺序填充:
| # |
物品存放位置 |
条件 |
| 1 |
Greedy Cells(贪婪存储单元) |
过滤器匹配,或已持有该物品 |
| 2 |
Memory modules(内存模块,DRAM Bays) |
已持有该物品类型 |
| 3 |
Slimefun barrels(Slimefun 桶) |
已持有该物品类型 |
| 4 |
Quantum Cells / Infinity Barrels(量子存储单元 / 无限桶) |
已持有该物品类型 |
| 5 |
Memory modules(内存模块,DRAM Bays) |
有空闲空间,新物品类型 |
| 6 |
Slimefun barrels(Slimefun 桶) |
为空 |
| 7 |
Quantum Cells / Infinity Barrels(量子存储单元 / 无限桶) |
为空(存储单元会采用该物品类型) |
| 8 |
没有过滤器的 Greedy Cells(贪婪存储单元) |
通用溢出 |
| 9 |
通过 Container Connector(容器连接器)链接的容器 |
先填满同种物品的堆叠,再填充空槽 |
任何无法容纳的物品都会返回给存入者(永远不会被删除)。
取出操作的顺序如下:内存模块 → Quantum Cells / Infinity Barrels → Slimefun 桶 → Greedy Cells → 链接的容器。推送器、终端、合成系统和 API 都可以从 Greedy Cells 中取出物品,但 Greedy Cell 始终保留其过滤器(内部过滤器)中定义的每种物品的 1 单位。如果某个 Pusher 在其 白名单 中包含该物品,则会释放它:此时 Greedy Cell 会将所有该物品转移到其他存储中,并在该 Pusher 存在期间停止摄取该物品。Greedy Cell 自身的吸取功能和无线桥接都不会从 Greedy Cells 中取出物品。
单次取出操作总是返回 一种 物品类型(第一个匹配的)。具有多个物品白名单的推送器会在同一个周期内依次对每种物品执行一次取出操作。
3. 一个周期的逐步流程
每 5 个刻钟,计时器会对每个网络运行以下步骤(每项步骤可在配置文件中独立设置间隔时间):
| 间隔 |
设备 |
每台设备 |
| 传输 (5 t) |
抓取器 / 高级抓取器 |
从第一个有物品的面最多抓取 128 / 1,024 个同类物品。如果网络拒绝接收部分物品,则首先尝试发送给接受该物品的推送器;剩余部分退回原来源槽位(仅限输出槽,绝不进入机器输入口),抓取器将在同一周期内尝试下一个物品。仅当无法退回时,才会将其暂存在抓取器的中转缓冲区中(抓取器暂停工作直到缓冲区清空;区块破坏后缓冲区数据保留)。 |
| 传输 |
DRAM 卸载器 |
从其卡中最多移动 4,096 个物品和 64,000 mB 液体到网络中;无法容纳的部分留在卡上。 |
| 传输 |
DRAM 加载器 |
启动后,将最多 4,096 个目标物品(或 64,000 mB 流体)拉取至其卡中;达到设定数量或卡满时停止。 |
| 传输 |
推送器 / 高级推送器 |
仅在有相邻容器时生效:最多抓取 128 / 1,024 个物品(依次检查多物品白名单),并按上述规则插入相邻容器;无法容纳的部分退回网络,或在网络已满时等待在推送器的中转缓冲区中(下一周期优先重试)。 |
| 传输 |
遗传鸡分类器 |
最多 16 只符合规则的鸡,按选定方向(推/拉)。 |
| 传输 |
贪婪单元格 |
拉取最多 512 个匹配物品,向相邻非网络容器推送最多 256 个。 |
| 传输 |
净化器 |
删除最多 128 个匹配物品(需配备过滤器)。 |
| 传输 |
无线接收器 / 发射器 |
通过桥接最多拉取 / 推送 128 个匹配物品(见下文)。 |
| 传输 |
液体泵 |
抽取一个源方块(1,000 mB),仅当其能完整容纳时才执行。 |
| 真空 (10 t) |
吸尘器 |
拾取半径内的掉落物。 |
| 合成 (20 t) |
自动合成器 / Slimefun 自动合成器 |
尝试每个已安装的蓝图一次。 |
| 合成 (20 t) |
库存合成器 / Slimefun 库存合成器 |
同上,但当网络中持有其输出物 64 个时跳过该蓝图。 |
空闲的抓取器和推送器会退避:在未发现任何物品后,它们仅在每第三个周期进行检查,并在连续 30 个空闲周期后改为每第六个周期检查(默认间隔下为 1.5 秒),直到再次有物品移动,因此上千个空闲设备几乎不消耗资源。若净化器未找到可删除的物品,它将不再查找,直到网络中的某物发生变化(或经过 5 秒),因此新物品仍会在下一个周期被净化。
4. 网络之间:无线桥接
两个网络绝不会通过空气合并。物品跨网络传输的唯一方式是 Transmitter / Receiver 链接,且拥有链接的那一端负责移动物品:
Network A Network B
[Controller]-[Cells]-[Transmitter] ~~~~~~~~~~~ [Receiver]-[Cells]-[Controller]
Receiver linked to the Transmitter: B pulls from A what passes the RECEIVER's filter
Transmitter linked to the Receiver: A pushes into B what passes the TRANSMITTER's filter
- 链接:按住 Shift + 右键点击放置好的、手持 Receiver 物品的 Transmitter(此时接收器处于拉取模式),或手持 Transmitter 物品的 Receiver(此时发射器处于推送模式)。双向链接两端可实现双向交换。
- 移动端的过滤器生效:可为白名单或黑名单,支持精确模板或材料。空的白名单不会移动任何物品;空的黑名单则会移动所有物品。
- 另一端的过滤器同样有效:如果被动端设有过滤器(条目或黑名单模式),物品必须同时通过两端的过滤器才能跨越。两端互不覆盖;若被动端未作设置(空白名单)则不构成限制。
- 每个周期和每个链接的设备最多传输 128 个同类物品。贪婪单元格永远不会被排空。
- 适用于任意距离和跨世界,但前提是另一端所在的区块已加载。
- 两端均需通过保护检查,各自使用其所属网络的拥有者权限。
- 若目的地无法接收物品,则退回源端;若源端也无法接收退回物品,则在移动它们的设备旁掉落——绝不会凭空消失。
- Receiver 的菜单中有一个按钮可打开 A 的终端,从而允许你从 B 基地手动使用 A 的存储(前提是你被允许访问 A 的土地)。
5. 共享总线:同一线缆上的两个控制器
如果两个控制器最终连接在一起(一根线缆同时接触两者),每个控制器都会构建自己的网络,且两者都包含它们之间的线缆和设备。/mvnets doctor、探针和全息图会将其报告为 foreign controller at x,y,z。在此期间:
- 每个共享设备在每个周期仍只工作一次:它会被分配给两个网络中的第一个(顺序由世界和控制器位置稳定决定)。此前,每个共享的抓取器、推送器、净化器、泵和合成器会在每个周期工作两次。
- 共享单元格可从两个终端查看。
- 共享 DRAM 舱可从两个网络查看,如同单元格一样。从旧控制器回收的模块会等待在该网络的终端中。
正确的修复方法是保持每个网络只有一个控制器,如果你确实希望两个网络交换物品,请使用 Transmitter/Receiver 对。
6. 流体
流体存储是独立的:Quantum Fluid Cells 和 Fluid DRAM Modules(位于 DRAM 舱中)用于存储流体,只有液体泵、终端的流体页面、终端的输入槽以及对流体单元格的直接右键操作才能移动它们。存入流体会优先填充已持有该流体的单元格,然后是 Fluid DRAM,最后是空单元格。
存入操作是全有或全无的:桶、瓶子或源方块只有在体积完全容纳时才会被消耗,因此一个接近满的网络绝不会同时保留流体和容器。
7. 无丢失,无重复
- 破坏节点会将其状态存储在掉落物中(单元格货物、过滤器、面朝向、传输缓冲区、蓝图、合成网格、接收器链接、限制器、流体、泵过滤器、鸡排序规则),放置时则会恢复这些状态。耙子也执行相同的操作。DRAM 存储库会将每个模块单独掉落,并保留其内部的全部库存。
- 推杆永远不会在槽位中留下超过一组物品,也不会将任何物品放入其他网络节点。
- 漏斗无法接触任何设备。
- 所有 GUI 都具有防复制保护机制,并在关闭时返回真实槽位中剩余的任何物品。
- 合成是全有或全无的,即使结果只能部分容纳也是如此。
- 节点不受活塞和爆炸的影响。
? 存储与性能
每个放置的设备都将其状态(过滤器、货物、规则、链接等)保存在世界文件夹内的区域文件中:<world>/multiversenets/r.<rx>.<rz>.mvn,每 32×32 个区块一个文件,类似于 Minecraft 自身的区域文件格式。不会向区块本身写入任何数据。
- 无每区块限制。 一个区块可以容纳尽可能多的电缆和设备。区块自身的保存数据不会改变,因此密集的建造永远不会使区块在保存或加载时变得沉重。
- 电缆成本几乎为零。 处于默认状态的节点——即未被配置的每条电缆、每个设备——仅存储其类型和位置(20 字节)。只有经过配置的设备才会存储其完整状态。
- 在主线程之外。 只要其中一个区块加载,其区域就会在后台读取。仅当区域发生更改时才会写入:每隔
storage.autosave-seconds(30 秒)、执行 /save-all、使用 /mvnets save 以及服务器关闭时。自动保存将其主线程工作分散到多个刻中(每刻最多 2 毫秒),因此繁忙的世界永远不会导致单刻过长。每次写入都会先写入临时文件,然后通过单次移动替换旧文件,因此崩溃只会保留旧文件或新文件,绝不会是两者的混合。
- 仅在用时占用内存。 区域在其包含设备的区块加载期间保持加载状态,并在保存后被卸载。
- 损坏的文件不会导致服务器停止运行。 校验和失败的文件会被重命名为
.corrupt-<time>(保留以供检查),并且该区域将从空状态开始。
- 数据随世界一起迁移。 复制或备份世界文件夹即可保留其网络。
- 自动迁移。 由 5.2 或更早版本写入的区块会在更新后首次加载时将其设备数据从区块中移出;无需手动操作。此迁移为单向过程:5.2 版本的 jar 包此后将无法看到这些设备。
?️ 领地保护
支持的保护插件:ProtectionStones、WorldGuard、Lands、Towny、GriefPrevention(包括用于玩家访问的 BentoBox 岛屿)。
- 控制器会记住是谁放置了它;该玩家即为网络的拥有者。在此功能存在之前创建的控制器将采用第一个被允许打开它们的玩家作为所有者。
- 扫描不会将网络扩展到其拥有者无法使用的领地范围内,并且网络读取或写入的每个方块都会进行检查——抓取器、推杆、溢出的推杆、贪婪单元格、真空吸盘、泵以及无线桥的两端,无论方向如何。
- 玩家无法在他们不拥有的受保护领地上的设备上进行操作(
multiversenets.protection.bypass 和 multiversenets.admin 权限可跳过此限制)。这包括通过接收器打开远程网络。
- 逃生出口:
protection.exempt-worlds、protection.exempt-locations 以及 protection.block-network-linking: false。
⌨️ 命令
| 命令 |
描述 |
权限 |
/mvnets help |
命令列表 |
multiversenets.use |
/mvnets guide [en|es] |
打开指南菜单:显示每种设备及其配方、功能及使用方法,以及网络的工作原理。可在英语/西班牙语之间切换 |
multiversenets.use |
/mvnets give <id> [n] |
给予一个设备 |
multiversenets.admin |
/mvnets doctor |
重新扫描并诊断所有网络(还会说明 Slimefun 集成是否激活) |
multiversenets.admin |
/mvnets stats |
全局统计信息,包括节点存储情况(内存中的区域、磁盘上的区域以及等待保存的区域) |
multiversenets.admin |
/mvnets inspect |
检查你正在查看的方块(类型、网络、内容、过滤器) |
multiversenets.admin |
/mvnets repair |
强制重新扫描你正在查看的网络 |
multiversenets.admin |
/mvnets recipes |
重新注册并解锁所有合成配方 |
multiversenets.admin |
/mvnets save |
立即保存节点区域文件,而不是等待自动保存 |
multiversenets.admin |
/mvnets reload |
重新加载配置、保护提供程序和配方 |
multiversenets.admin |
⚙️ 配置
config.yml 中最相关的键(每个键都在文件本身中有文档说明,提供英语和西班牙语版本):
| 键 |
默认值 |
效果 |
network.scan-interval-ticks |
20 |
可能已更改的网络重新扫描之间的最小间隔 |
network.full-rescan-ticks |
600 |
未触动的网络的定期完全重新扫描 |
network.max-nodes |
16384 |
每个网络的最大节点数 |
storage.autosave-seconds |
30 |
节点区域文件的后台保存间隔 |
network.op-interval-ticks.transfer / vacuum / craft |
5 / 10 / 20 |
各类操作的间隔 |
transfer.items-per-op |
128 |
抓取器/推送器/清除器/接收器每次操作处理的物品数量 |
transfer.ht-multiplier |
8 |
高级抓取器/推送器的乘数 |
transfer.module-items-per-op |
4096 |
DRAM 加载器/卸载器每周期移动的物品数量 |
transfer.module-fluid-per-op |
64000 |
DRAM 加载器/卸载器每周期移动的流体(mB)数量 |
cells.capacities |
65,536 … 2,000,000,000 |
各层级格子的容量 |
virtual-cache.tier-1 … tier-5 |
2,048 … 524,288 |
各层级物品存储模块的容量 |
greedy.capacity / barrel.capacity |
262,144 / 2,000,000,000 |
贪婪格/无限桶的容量 |
fluids.cell-capacity-mb |
64,000 |
流体格子容量 |
fluids.dram-capacity-mb |
512,000 |
流体 DRAM 模块的总容量 |
vacuum.radius |
4.0 |
真空拾取半径 |
crafter.max-recipes |
18 |
制造台可用的蓝图数量 |
wireless.local-range-without-router |
64 |
无路由器时无线终端的范围 |
wireless.combat-cooldown-seconds |
10 |
无线终端的战斗锁定冷却时间 |
compat.slimefun |
true |
Slimefun 机器、电缆和桶的集成 |
slimefun-machines.enabled |
true |
Slimefun 机器的总开关(编码器、自动制造台、库存制造台、请求制造台):关闭 = 无配方、无法放置、无菜单、不工作 |
slimefun-machines.encoder / slimefun-machines.crafters |
true |
各个 Slimefun 机器单独控制(旧的 sf-encoder.enabled / sf-crafter.enabled 键仍有效) |
blocked-worlds |
[] |
设备无法放置的世界列表 |
protection.* |
— |
参见 领地保护 |
? Slimefun 集成(可选)
MultiverseNets 不依赖 Slimefun。如果安装了它,将在启动时检测到
(包括 DrakesCraft 分支和原版),并且在 compat.slimefun: true 的情况下:
- 抓取器、推送器、贪婪格和制造台可以与 Slimefun 机器 一起工作,就像与箱子一样,
仅使用机器声明用于输入和输出的槽位。
- 插入遵循机器自身的规则,类似于 Networks:每次插入会填满已持有该物品的槽位,并打开 最多一个新槽位。诸如电动熔炉或加热压力舱之类的机器只接受放入已持有该物品的槽位中的物品,因此每种材料保持在 一个堆叠 中,其他槽位保持空闲以容纳其他材料。普通机器仍会填满每个输入槽位,每周期一个。
- ID 包含
CABLE 或 BRIDGE 的 Slimefun 方块可以传导 MultiverseNets 网络,且与其接触的 Slimefun 桶将成为其存储的一部分。
- Slimefun 编码器和制造台变为可用。
如果没有安装 Slimefun,桥梁将处于非活动状态,其他内容不会发生变化。执行 /mvnets doctor 后,其第一行会显示集成是否处于活动状态。
? 与 Networks 的共存
可以同时安装这两个插件。 它们的标识符永远不会冲突:
|
MultiverseNets |
NetworksV6-Drake |
| 插件名称 |
MultiverseNets |
NetworksV6-Drake |
| 主类 |
com.chagui68.multiversenets.… |
io.github.sefiraat.networks.… |
| 命令 |
/mvnets |
/networks |
| 权限 |
multiversenets.* |
networks.* |
| 物品 |
自有,通过 PDC,带有原版配方 |
Slimefun 的 (NTW_*) |
Networks 不注册任何原版配方(它们的配方通过 Slimefun 合成表进行),因此这里的 66 个配方也不会冲突。NetworksCoexistenceTest 中的五个测试固定了标识符,因为破坏共存的是意外重命名的标识符,而不是代码本身。
在启用 Slimefun 集成时需要记住的交互: MultiverseNets 抓取器可以从 Networks 方块中提取物品(它是一个具有自己菜单的 Slimefun 物品),而 ID 包含 CABLE 或 BRIDGE 的 Networks 方块(例如 NTW_BRIDGE)可以传导 MultiverseNets 网络。如果你希望每个网络坚持使用自己的方块:
compat:
slimefun: false
? 与 Networks 的区别
|
Networks (Slimefun 附加组件) |
MultiverseNets |
| 依赖项 |
Slimefun + 其链式依赖 |
无,仅依赖 Paper API |
| 网络成员资格 |
每个节点存储其根节点 |
由控制器从 BFS 重新计算 |
| 孤立节点 |
可能存在 |
结构上不可能:每次扫描都会重建拓扑结构 |
| 诊断工具 |
稍后添加 (/networks doctor) |
/mvnets doctor、探针、监视器、全息图 |
| 计时器 |
Slimefun 的周期 |
自有,配置中包含每个操作的间隔 |
| 节点数据 |
Slimefun 的 BlockStorage |
世界文件夹中的自有区域文件,在主线程之外保存;电缆和未配置的装置仅存储其类型 |
代价是扫描需要在最多 max-nodes 个方块上进行一次 BFS——这是可预测的、有界的工作量,以换取没有任何可能被损坏的状态。它仅在可能发生更改时运行,此外每隔 full-rescan-ticks 运行一次以捕获未被事件报告的内容(领地主张、被其他插件编辑的方块)。
?️ 构建
mvn clean package
这将构建发布版 jar(1.21.11 API,Java 21 字节码,可在 1.21.11、26.1 和 26.2 上运行)。要针对较新的 API 检查代码(需要 JDK 25):
mvn -P api-26.1 clean compile
mvn -P api-26.2 clean compile
jar 文件生成于 target/MultiverseNets-v<version>.jar。
? 兼容性
| 参数 |
要求 |
| 服务器 |
Paper / Purpur 1.21.11、26.1(26.1 – 26.1.2)和 26.2 —— 这三个版本使用同一个 jar 文件 |
| Java |
你的服务器所需的 Java 版本:1.21.11 需要 Java 21,26.1 和 26.2 需要 Java 25 |
每次发布前如何验证各个版本(.github/workflows/verify.yml):
| 版本 |
检查项 |
| 1.21.11 |
jar 文件基于此 API 构建,并在其上运行完整的测试套件。 |
| 26.1 |
相同源码针对 Paper 26.1.2 API 进行编译(mvn -P api-26.1 clean compile,JDK 25)。 |
| 26.2 |
相同源码针对 Paper 26.2 API 进行编译(mvn -P api-26.2 clean compile,JDK 25)。 |
测试服务器(MockBukkit)仅存在于 1.21 中,因此在 26.x 版本上的检查是:插件调用的每个方法都必须存在于 MockBukkit 中;且这些版本中没有标记为即将移除的功能。 | 依赖项 | 无(Slimefun 和保护类插件为可选) |
不兼容 Folia。 网络时钟、拓扑扫描以及所有 GUI 均运行在 Paper 的全局调度器上,并假设主线程拥有其所操作块的权限。请安装在 Paper 或 Purpur 服务器上。
? 许可证与独立著作权
版权所有 © 2026 Chagui68 · Slimefun: New Horizons。
本项目是由 Chagui68 为 DrakesCraft 网络打造的原创独立作品。所有知识产权及创作署名均归属于 Chagui68。严禁商业转售、打包进付费套装或移除创作者署名。
⚠️ CONSOLIDADO EN DRAKES-SUITES (SUITE MULTIVERSE POR CHAGUI68):
Todo el desarrollo activo y soporte para Paper/Purpur 1.21.11+ se realiza oficialmente en el monorepo Drakes-Suites dentro del módulo oficial drakes-multiverse, preservando la autoría y diseño soberano de Chagui68.
🌌 MultiverseNets
Standalone digital logistics networks and massive storage for Paper — no Slimefun.
Wiki: English · Español · Recipes: EN · ES
📖 What is MultiverseNets?
MultiverseNets implements a Networks-style logistics network 100% standalone: no Slimefun and
no other dependency. Every device is a custom item (identified by PDC), every placed device keeps
its state in region files inside the world folder (no per-chunk limit), and the
network's storage is virtual and persistent.
A network is one Network Controller plus every MultiverseNets block connected to it, face to
face. Cables are the cheap way to connect things, but every device conducts: a grabber touching a
cell touching the controller is already a network.
🎮 Quick start
- Place a Network Controller. Whoever places it becomes the network's owner.
- Connect Cables and devices to it. Add at least one Quantum Cell (or an Infinity Barrel)
— without storage the network has nowhere to put items.
- Right-click a Network Terminal (or the controller's menu) to see and use the storage.
- Put a Grabber next to a chest to import, a Pusher next to a chest to export. Configure
their filters with right-click.
- Check
/mvnets doctor or a Network Probe if something does not connect.
Every device id below can be given with /mvnets give <id> (press Tab to complete the ids).
Crafting recipes for every device are in Recipes (EN) /
Recetas (ES).
🧩 Machine reference
Rates are the defaults from config.yml; every one of them is configurable (see
Configuration below). "Cycle" means one transfer cycle (network.op-interval-ticks.transfer,
5 ticks by default).
🖥️ Core and access
| Device |
id · block |
What it does |
How to use it |
| Network Controller |
mvn_controller · Lodestone |
The network's root. Every scan starts here (breadth-first through connected blocks, up to network.max-nodes). Records its owner (the placer) and shows a floating hologram with status, nodes and stored totals. Memory modules no longer go in the controller: they go in a DRAM Bay. |
Right-click: status and router status. It does not accept modules. A module that was inside an old controller is taken out automatically with its items and waits in the Terminal as a temporary item: click it there and install it in a DRAM Bay. Breaking the controller drops any module nobody collected. Only one controller per network: a second one wired to the same cables is reported as foreign controller (see Shared buses). |
| Network Cable |
mvn_cable · Glass |
Connects devices. No logic of its own. It can be camouflaged as any solid block, so a line of cables disappears inside a wall. It also comes in 16 colours (stained glass) to tell areas of a build apart: 4 cables of any colour + a dye = 4 cables of that colour. Every colour connects like the plain cable; a broken cable drops with its colour. |
Right-click it (empty hand) to see whether it reaches a controller and open its menu. Put a block in the camouflage slot and the cable looks exactly like it: the block is kept inside the cable, not used up. Take it back and the cable is glass again; breaking the cable drops the cable and the block. Only solid, full blocks that do not fall, change by themselves or have an inventory. Holding a block while right-clicking places the block instead. |
| Network Terminal |
mvn_terminal · Beacon |
The storage grid: every item in the network (cache, cells, barrels, greedy cells, Slimefun barrels). The top row holds the views: Network Storage, Purge Mode (items targeted by purgers), Fluids and 5 custom pages (your favourites), plus the input slot. The bottom row holds the tools: pages, sort, search, network overview, Pin Mode, Deposit Inventory and a help book. |
Left-click takes 1, right-click a stack, shift+click sends to your inventory; click the grid with an item on the cursor to store it. Shift+left-click your items (or drop them in the input slot) to store them. Pin an item to a custom page by hovering it and pressing 1-5, or with Pin Mode on; Q over an item on a custom page unpins it. A custom page shows only its pinned items (also when out of stock), so a job only shows what it needs. Right-click a page tab to rename it, shift+right-click to clear it. Pages are saved per player and work on any Terminal. Buckets/honey bottles go to fluid storage. Each item shows its total in the network and a breakdown of where it is kept (DRAM, Quantum Cells, Infinity Barrels, Greedy Buffer, Slimefun barrels); the parts add up to the total, nothing is counted twice. Recovered modules from an old controller appear first as temporary items. |
| Wireless Terminal |
mvn_wireless_terminal · item (Nether Star) |
Opens the Network Terminal remotely. |
Shift+right-click a Controller or a Terminal to bind it, then right-click in the air. Without a Network Router it works only in the same world and within wireless.local-range-without-router (64) blocks. Never within 10 s of combat, and only if you may access the network's land. |
| Network Router |
mvn_router · Lightning Rod |
Lifts the Wireless Terminal limits for its network: any distance and any world. |
Connect it anywhere in the network. |
| Network Monitor |
mvn_monitor · Respawn Anchor |
Live diagnostic panel: node counts by type, storage usage, errors. |
Right-click; it refreshes while open. |
| Network Probe |
mvn_probe · item (Spyglass) |
Answers "is this connected?": network size, controller position, scan errors and protection cuts for the block you click. |
Right-click any block. |
| Network Status Light |
mvn_status_light · Lime/Red Stained Glass |
Placed on any side of a network block, it shows from afar whether that block reaches a Controller: green when connected, red when not. It is not part of the network and never links two networks. |
Place it on any network block; it checks once a second. |
🧠 Memory: DRAM Bay and modules
| Device |
id · block |
What it does |
How to use it |
| DRAM Bay |
mvn_dram_bay · Waxed Copper Bulb |
Network block that holds up to 18 memory modules, each with its own stock. The modules are the storage: while installed, their stock is part of the network. Place as many bays as you like. |
Right-click a bay with a module in hand to install it in the next free slot, or right-click to open its menu: a menu with the bay's summary on top, 18 module slots (each with its fill bar), and two gauges that show how full the item and fluid memory are. Install from the cursor or with shift+click; click an installed module to take it out with its whole stock. Breaking it (or the Rake) drops the bay and every module with its whole stock. |
| Item memory modules |
mvn_cache_l1 · _l2 · _l3 · _dram · _quantum · items |
Multi-item storage: 2,048 / 8,192 / 32,768 / 131,072 / 524,288 items in total (virtual-cache.tier-1 … tier-5), any mix of types. |
Install it in a DRAM Bay. Taking it out takes all its items with it: they disappear from that network and appear in the network of the DRAM Bay you install it in. Upgrading a loaded module in a crafting table keeps its items. |
| Fluid DRAM Module |
mvn_fluid_dram · item (Heart of the Sea) |
Fluid-only module: holds several fluids at once, up to fluids.dram-capacity-mb (512,000 mB = 512 buckets) in total. |
Like the item modules: it goes in a DRAM Bay, adds its capacity to the network's fluid storage, and taking it out carries its fluids to another network. |
| DRAM Unloader |
mvn_module_unloader · Waxed Exposed Copper Bulb |
Empties cards (memory modules) into the network: up to 9 cards, transfer.module-items-per-op items (4,096) and transfer.module-fluid-per-op mB (64,000) per cycle. Unlike a DRAM Bay, the cards inside are not network storage. What the network can not store stays on the card and the next item is tried, so the card ends up as empty as possible. Needs free space in the network. |
Right-click it with a card in hand, or open its menu: 9 card slots with their progress, and Take empty cards to collect every finished one. |
| DRAM Loader |
mvn_module_loader · Waxed Oxidized Copper Bulb |
Fills one card with a single item (or fluid, for a Fluid DRAM) from the network, up to the amount you choose, then stops. Inserting a card does nothing by itself. |
Open it, put a card in, click the target slot with the item (a fluid bucket for a Fluid DRAM), set the amount (±64/±1k/±10k buttons, shift ×100, or click and type 1m, 500k, max) and press Start. Example: an empty Quantum card + cobblestone + 500k + Start = a card ready to sell. Its target and amount travel with the block when broken. |
📦 Item storage
| Device |
id · block |
What it does |
How to use it |
| Quantum Cell T1–T6 |
mvn_cell_t1 … mvn_cell_t6 · Terracotta (plain, orange, yellow, lime, cyan, purple) |
Stores one item type each: 65,536 / 262,144 / 1,048,576 / 16,777,216 / 268,435,456 / 2,000,000,000 items. An empty cell takes the first item type that has nowhere else to go. |
Connect it. Right-click to see or manage its contents. Breaking it keeps the cargo in the item. Upgrade one tier with the Quantum Workbench or in a crafting table (cell surrounded by 8 diamonds); the cargo is kept. |
| Infinity Barrel |
mvn_infinity_barrel · Barrel |
Same as a cell — one item type — with barrel.capacity (2,000,000,000), but it stays registered to its item when it empties. Items with their own id (Slimefun and other plugins) are recognised by that id and their visible text, so an item you take out always goes back in, even if its name or lore was stored differently. |
Right-click: click Set Item with an item on the cursor to register it; right-click Set Item with an empty cursor clears the registration (only when empty). Hoppers do not interact with it (see below). |
| Greedy Cell |
mvn_greedy_cell · Slime Block |
With a filter: a priority sink. Incoming items matching its filter go to it before any other storage, every cycle it pulls up to 512 more of them from the network, and it pushes up to 256 per cycle into adjacent non-network containers (chests, Slimefun machines). Holds several types, up to greedy.capacity (262,144) in total. Without a filter: general overflow storage, used only when everything else is full. |
Right-click to set the filter and see its buffer. It works as an internal filter: an item defined in its filter always keeps 1 unit inside, whatever takes it out (Pushers, terminal, crafting, its own push to containers). If a Pusher of the network has that item in its whitelist, the Greedy Cell releases all of it (the last unit too) to the cells and stops taking it while that Pusher exists. The wireless bridge never takes from it. |
| Container Connector |
mvn_container_connector · Ochre Froglight |
Links the vanilla containers touching it (chests, trapped and copper chests, barrels, shulker boxes) to its network: the Terminal shows their items, deposits fill them and withdrawals empty them. They are the last storage in both directions (see the order below). Items move exactly as they are; a shulker box never goes into another one. A double chest counts once. |
Connect it to the network and put containers on any side. Grabbers, Pushers and Greedy Cells of the same network leave linked containers alone (they already are its storage). On claimed land the container must be in land the network may use. |
| Quantum Workbench |
mvn_quantum_workbench · Brain Coral Block |
Upgrades a Quantum Cell T1–T5 to the next tier, keeping its cargo. |
Cell in the centre, 8 diamonds around it, press Entangle & Upgrade, take the result. |
💧 Fluids
Fluids live in their own storage, separate from items: Quantum Fluid Cells and Fluid DRAM Modules
installed in DRAM Bays.
| Device |
id · block |
What it does |
How to use it |
| Quantum Fluid Cell |
mvn_fluid_cell · Prismarine Bricks |
Holds one fluid — Water, Lava, Milk, Powder Snow or Honey — up to fluids.cell-capacity-mb (64,000 mB = 64 buckets). All fluid cells of a network form its fluid storage. |
Right-click with a filled bucket / honey bottle to pour into that cell; with an empty bucket to fill it (Water, Lava, Milk, Powder Snow). Or use the Terminal's fluid page: deposit buckets/bottles, withdraw with an empty bucket (honey with a glass bottle). |
| Liquid Pump |
mvn_liquid_pump · Blue Stained Glass |
Each cycle drains one source block of water or lava directly below it (1,000 mB). The block is removed only if the whole 1,000 mB fit in the network. |
Place it on top of the liquid. Right-click to choose ANY / WATER / LAVA. |
🔄 Item transport
| Device |
id · block |
What it does |
How to use it |
| Simple Grabber |
mvn_grabber · Observer |
Imports from adjacent containers into the network: up to 128 items of one type per cycle, through all six faces. From a furnace it only takes the result. An item the network does not accept (no space, quota reached) goes back to its slot and the grabber moves on to the next item, so one unwanted item never blocks a chest. Next to a Quantum Cell or an Infinity Barrel that is not wired to the network it empties it too (the Grabber does not pull that storage into the network). |
Right-click for the filter (whitelist/blacklist). Empty filter = everything. |
| Advanced Grabber |
mvn_grabber_ht · Sticky Piston |
Same, ×8 (transfer.ht-multiplier): 1,024 per cycle, and it can be restricted to one face. |
Filter menu + face selector. |
| Simple Pusher |
mvn_pusher · Target |
Exports from the network into adjacent containers: up to 128 items per cycle, through all six faces (it has no face selector: use an Advanced Pusher for a single side). It never puts anything into another network block. |
The filter decides which items leave, not where they go. Empty whitelist = idle (so a fresh pusher never empties the network); blacklist = everything except what is listed: whatever you blacklist stays in the network. |
| Advanced Pusher |
mvn_pusher_ht · Piston |
Same, ×8, and with the face selector it delivers only to that side. |
Filter menu + face selector. For a machine, pick the machine's face. |
| Network Vacuum |
mvn_vacuum · Sponge |
Every 10 ticks picks up dropped items within vacuum.radius (4 blocks) into the network. |
Optional filter. Items that do not fit stay on the ground. |
| Network Purger |
mvn_purger · Magma Block |
Deletes up to 128 items per cycle that match its filter. |
Without a filter it deletes nothing, on purpose. |
| Network Quota Limiter |
mvn_limiter · Target |
Caps how much of one item the network may hold. Every deposit (grabbers, vacuum, terminal, crafting results, wireless bridge) stops at the cap. |
Right-click: set the target item, the limit and on/off. Several limiters on one item: the lowest wins. |
| Quota Manager |
mvn_quota_manager · Verdant Froglight |
One screen for every Quota Limiter of its network: each limited item with its limit, the network's stock, a usage bar and whether it is enforced, plus how many limiters are still free. |
Right-click it. Add an item with the Add button (item on the cursor), on a free limiter, or Shift-Click it in your inventory: it takes one free Quota Limiter (the item is only copied); with none free nothing is added, so place more limiters to limit more items. On a limited item: left-click types the limit (500, 64k, 1m), Shift+right-click turns it on/off, right-click removes the item (the limiter is free again), a click with another item replaces it. |
| Wireless Transmitter |
mvn_transmitter · Conduit |
One end of a wireless bridge. If it holds the link to a Receiver, it pushes up to 128 items per cycle that pass its filter into the receiver's network. |
Right-click: filter menu, plus a button that opens its own network's terminal. Link: shift+right-click a placed Transmitter holding a Receiver item, or a placed Receiver holding a Transmitter item. |
| Wireless Receiver |
mvn_receiver · Redstone Lamp |
The other end. If it holds the link to a Transmitter, it pulls up to 128 items per cycle that pass its filter from the transmitter's network into its own. Works across distance and worlds as long as the other end's chunk is loaded. |
Right-click: filter menu, plus a button that opens the remote network's terminal. Empty whitelist = nothing crosses, on purpose. |
Containers that Grabbers, Pushers and Greedy Cells work with: chests, trapped chests, barrels,
hoppers, dispensers, droppers, furnaces, blast furnaces, smokers, brewing stands, chiseled
bookshelves, shulker boxes, and — with Slimefun installed — Slimefun machines (only the slots the
machine declares for input/output). Never another MultiverseNets block.
How a Pusher delivers (designed for feeding machines such as a Slimefun Smeltery):
- At most one stack per slot. A 128 or 1,024 item cycle used to land in a single slot and
everything above one stack was lost: that is what emptied whole networks.
- With a whitelist of several items (e.g. the three ingredients of an alloy), each item gets its
share of the target's slots (9 slots / 3 ingredients = 3 each) and they are served in turn within
the same cycle. The first ingredient no longer floods the machine and locks the recipe out.
- Into a furnace, blast furnace or smoker: from above everything goes to the input; from a side,
fuel goes to the fuel slot and the rest to the input. Never into the result slot.
- What does not fit goes back to the network; nothing is lost.
Tip for machines that take and return items in the same block (a Smeltery puts its result in
the dispenser when it has no output chest): add an output chest, point the Advanced Grabber at that
chest and the Advanced Pusher at the dispenser. A grabber facing the dispenser also takes back the
ingredients you just pushed.
Hoppers: hoppers (and hopper minecarts) do not interact with any MultiverseNets block,
neither to insert nor to extract. A hopper on top of an Infinity Barrel used to be able to delete its
whole stack.
🛠️ Crafting
| Device |
id · block |
What it does |
How to use it |
| Blueprint |
mvn_blueprint · item (Book) |
A recipe: full 3×3 grid + result in its PDC. Crafting never consumes it. |
Encode it in a Recipe Encoder and install it in a crafter. Installing moves the Blueprint into the crafter; removing it, replacing it or Clear All gives it back. |
| Recipe Encoder |
mvn_encoder · Smithing Table |
Builds a recipe in a 3×3 template grid (clicking only marks slots, no items are spent) and writes it to a Blueprint (blank or already encoded). |
Fill the grid, put a Blueprint in the blue slot, press Encode. Clicking an encoded Blueprint loads its recipe into the grid. Blueprints left in its slots stay stored in the block (one viewer at a time sees them). |
| Slimefun Recipe Encoder |
mvn_sf_encoder · Enchanting Table |
Same for Slimefun recipes. Blueprints left in its slots also stay stored in the block, so you do not have to bring blank Blueprints every time. |
Needs Slimefun; disable with slimefun-machines.encoder (or every Slimefun machine with slimefun-machines.enabled). |
| Auto-Crafter |
mvn_crafter · Crafting Table |
Every 20 ticks tries each installed vanilla Blueprint once (up to crafter.max-recipes, 18). All-or-nothing: if any ingredient is missing nothing is taken, and if the result does not fit the whole craft is undone. |
Right-click, click Blueprints in. Refuses Slimefun Blueprints. |
| Slimefun Auto-Crafter |
mvn_sf_crafter · Crying Obsidian |
Same, and it accepts Slimefun and vanilla Blueprints: mix both in the same machine. |
Disabled entirely (recipe, placing, menu and crafting) with slimefun-machines.crafters: false or slimefun-machines.enabled: false. |
| Stock Crafter |
mvn_stock_crafter · Loom |
Same as the Auto-Crafter, but it skips a Blueprint while the network already holds 64 of its output. |
Vanilla Blueprints only. |
| Slimefun Stock Crafter |
mvn_sf_stock_crafter · Block of Amethyst |
Same as the Stock Crafter, with Slimefun and vanilla Blueprints. |
Disabled like the Slimefun Auto-Crafter. |
| Request Crafter |
mvn_request_crafter · Fletching Table |
Holds Blueprints that are only crafted on demand from a Request Terminal (never automatically). |
Install Blueprints like in an Auto-Crafter. |
| Slimefun Request Crafter |
mvn_sf_request_crafter · Purpur Pillar |
Same, with Slimefun and vanilla Blueprints. |
— |
| Request Terminal |
mvn_request_terminal · Lectern |
Lists everything the network's Request Crafters can make and crafts it on demand, resolving chains (logs → planks → crafting table) with the network's stock. |
Left-click 1 batch, shift+left-click 10, right-click 64, shift+right-click asks for a number in chat. Toggle delivery to your inventory or to the network. |
| Network Crafting Grid |
mvn_crafting_grid · Cartography Table |
A crafting table that pulls ingredients from the network; the template grid is stored in the block. |
Right-click, set the grid, craft. |
🧰 Tools
| Device |
id · block |
What it does |
How to use it |
| Configuration Wrench |
mvn_configurator · item (Comparator) |
Copies a filter (exact templates, materials and whitelist/blacklist mode) from one device to another. |
Shift+right-click a filterable device to copy, right-click another to paste. |
| Network Rake |
mvn_rake · item (Dead Bush) |
Dismantles a node instantly and gives it back to you with its state (filter, Blueprints, binding). 250 uses (rake.uses). |
Right-click a node. It refuses controllers and storage that still holds items or fluid. |
🔩 Components
Intermediate parts the base devices are crafted from, so no device recipe can clash with a vanilla
recipe. They are hand items: they cannot be placed or used, and no vanilla recipe accepts them.
Blueprints encoded with the old device recipes no longer work: encode them again. Their recipes are in
Recipes & functions.
| Component |
id · item |
Used to craft |
| Silicon Wafer (×2) |
mvn_silicon_wafer · Prismarine Crystals |
Network Circuit, Storage Matrix, Blank Blueprint |
| Network Circuit (×2) |
mvn_network_circuit · Prismarine Shard |
Controller, Cable, Terminal, Simple Grabber, Simple Pusher, Vacuum, Purger, Quota Limiter, Monitor, Probe, both Recipe Encoders, Configuration Wrench, Container Connector; Logic Processor, Storage Matrix |
| Logic Processor |
mvn_logic_processor · Shulker Shell |
Controller, Auto-Crafter and Slimefun Auto-Crafter, both Request Crafters, Request Terminal, Crafting Grid; Quantum Core (×2) |
| Storage Matrix |
mvn_storage_matrix · Disc Fragment |
Quantum Cell T1, Infinity Barrel, Greedy Cell, Quantum Fluid Cell, DRAM Bay, L1 CPU Cache Module |
| Transfer Coil (×2) |
mvn_transfer_coil · Tripwire Hook |
Simple and Advanced Grabber, Simple and Advanced Pusher, Vacuum, Liquid Pump, Container Connector |
| Quantum Core |
mvn_quantum_core · Echo Shard |
Wireless Terminal, Wireless Transmitter, Wireless Receiver, Network Router, Quantum Workbench |
🐔 GeneticChickengineering
| Device |
id · block |
What it does |
How to use it |
| Genetic Chicken Sorter |
mvn_chicken_sorter · Hay Bale |
A machine dedicated only to the pocket chickens of the GeneticChickengineering addon. It reads their genes and moves only chickens that meet every rule; any other item is ignored. Up to 16 chickens per cycle. |
Right-click. The menu reads top to bottom: control bar (start/stop, direction Push network → block or Pull block → network, side, a summary book that says in plain words which chickens pass right now, and help), accepted products (18 slots showing each product's own item; click one with a pocket chicken on the cursor or shift+click a chicken in your inventory, click a product to remove it; empty = any product) and gene rules grouped as tier (min/max; recessive genes, special species 7-9), genes (minimum DNA strength 0-6, pure genes only) and identity (sequenced/unsequenced DNA, adult/baby). Every rule shows its value in its name and stack size and glows while active: left +1, right −1, shift-click resets it. The tier range can never be left empty. Bottom row: clear products, reset gene rules, close. Starts stopped: turn it on once it is set up. |
With this addon installed every chicken is a unique item (it carries its own DNA). The network no
longer merges two different chickens into one stack: a chicken could previously come out with
another one's DNA.
Filterable devices: Grabbers, Pushers, Vacuum, Purger, Greedy Cell, Wireless Transmitter and Receiver. All of
them support whitelist and blacklist mode, and in the Grabber/Pusher menus clicking a face button
opens the container on that face.
🔀 How items move inside and between networks
1. What belongs to a network
On every scan the controller walks through every connected MultiverseNets block, face to face. A
network is scanned immediately after one of its nodes is placed or broken; within
network.scan-interval-ticks when it may have changed (a chunk of it loaded, a Slimefun cable or
barrel was placed or broken next to it); and otherwise only every network.full-rescan-ticks. The scan:
- never loads chunks — nodes in unloaded chunks are simply not part of the network until they load;
- reads every neighbour from memory (one lookup, nothing decoded), so a scan costs the same in a
dense chunk as in a sparse one;
- stops at another controller (
foreign controller at x,y,z);
- never goes from a Grabber into a Quantum Cell or an Infinity Barrel: a Grabber touching one
empties it into the network like a chest. Wire the storage by cable instead and it is network
storage (and the Grabber leaves it alone);
- stops at land the network's owner cannot use (see Land protection);
- with Slimefun installed, also walks through Slimefun blocks whose id contains
CABLE or BRIDGE
and adds touching Slimefun barrels to the storage.
There is no per-node "which network am I in" state: the topology is rebuilt from scratch every
scan, so a node can never point to a network that no longer exists.
2. The internal storages and their order
A network's item storage is the sum of five internal storages. Every deposit — from a grabber,
the vacuum, the terminal, a crafting result or the wireless bridge — first checks the
Quota Limiters, then fills in this order:
| # |
Where the items go |
Condition |
| 1 |
Greedy Cells |
their filter matches, or they already hold the item |
| 2 |
Memory modules (DRAM Bays) |
they already hold that item type |
| 3 |
Slimefun barrels |
they already hold that item type |
| 4 |
Quantum Cells / Infinity Barrels |
they already hold that item type |
| 5 |
Memory modules (DRAM Bays) |
free space, new item type |
| 6 |
Slimefun barrels |
empty |
| 7 |
Quantum Cells / Infinity Barrels |
empty (the cell adopts the item type) |
| 8 |
Greedy Cells without a filter |
general overflow |
| 9 |
Containers linked by a Container Connector |
stacks of the same item first, then empty slots |
Whatever does not fit is returned to whoever deposited it (it is never deleted).
Withdrawals read in this order: memory modules → Quantum Cells / Infinity Barrels → Slimefun
barrels → Greedy Cells → linked containers. Pushers, terminals, crafting and the API can take from Greedy Cells, but a
Greedy Cell always keeps 1 unit of every item defined in its filter (its internal filter). A
Pusher that has the item in its whitelist releases it instead: the Greedy Cell moves all of it
to the other storages and stops taking it while that Pusher exists. A Greedy Cell's own suction and
the wireless bridge never take from Greedy Cells.
A single withdrawal always returns one item type (the first one that matches). A pusher with a
whitelist of several items makes one withdrawal per item, in turn, within the same cycle.
3. One cycle, step by step
Every 5 ticks the ticker runs these per network (each on its own configurable interval):
| Interval |
Device |
Per device |
| transfer (5 t) |
Grabber / Advanced Grabber |
Up to 128 / 1,024 of one type from the first face that yields something. If the network refuses part of it, it is first offered to Pushers whose filter accepts it; what is still left goes back to the slots it came from (output slots only, never a machine's input) and the grabber tries the next item in the same cycle. Only if it can not go back does it wait in the grabber's transit buffer (the grabber pauses until it clears; the buffer survives breaking the block). |
| transfer |
DRAM Unloader |
Moves up to 4,096 items and 64,000 mB from its cards into the network; what does not fit stays on the card. |
| transfer |
DRAM Loader |
While started, pulls up to 4,096 of its target item (or 64,000 mB of its fluid) into its card; stops at the chosen amount or when the card is full. |
| transfer |
Pusher / Advanced Pusher |
Only with a container next to it: takes up to 128 / 1,024 items (a multi-item whitelist in turn) and inserts them into the adjacent containers with the rules above; what does not fit goes back to the network, or waits in the pusher's transit buffer if the network is full meanwhile (retried first on the next cycle). |
| transfer |
Genetic Chicken Sorter |
Up to 16 chickens that meet its rules, in the chosen direction (push/pull). |
| transfer |
Greedy Cell |
Pulls up to 512 matching items, pushes up to 256 into adjacent non-network containers. |
| transfer |
Purger |
Deletes up to 128 matching items (only with a filter). |
| transfer |
Wireless Receiver / Transmitter |
Pulls / pushes up to 128 matching items across the bridge (see below). |
| transfer |
Liquid Pump |
Drains one source block (1,000 mB), only if it fits whole. |
| vacuum (10 t) |
Vacuum |
Picks up dropped items within the radius. |
| craft (20 t) |
Auto-Crafter / Slimefun Auto-Crafter |
Tries each installed Blueprint once. |
| craft (20 t) |
Stock Crafter / Slimefun Stock Crafter |
Same, but skips a Blueprint while the network holds 64 of its output. |
Idle grabbers and pushers back off: after finding nothing they only check every third cycle, and
after 30 idle cycles every sixth (1.5 s with the default interval), until something moves again, so a
thousand idle devices cost almost nothing. A Purger that found nothing to delete does not look again
until something in the network changes (or 5 s pass), so a new item is still purged on the next cycle.
4. Between networks: the wireless bridge
Two networks never merge through the air. The only way items cross is a Transmitter / Receiver
link, and the end that holds the link is the one that moves items:
Network A Network B
[Controller]-[Cells]-[Transmitter] ~~~~~~~~~~~ [Receiver]-[Cells]-[Controller]
Receiver linked to the Transmitter: B pulls from A what passes the RECEIVER's filter
Transmitter linked to the Receiver: A pushes into B what passes the TRANSMITTER's filter
- Linking: shift+right-click a placed Transmitter holding a Receiver item (the receiver pulls),
or a placed Receiver holding a Transmitter item (the transmitter pushes). Link both for a
two-way exchange.
- Filter on the end that moves: whitelist or blacklist, exact templates or materials. An
empty whitelist moves nothing; an empty blacklist moves everything.
- The other end's filter counts too: if the passive end has a filter (entries, or blacklist
mode), an item only crosses when it passes both. Neither end overrides the other; a passive
end left untouched (empty whitelist) does not restrict.
- Up to 128 items of one type per cycle and per linked device. Greedy Cells are never drained.
- Works across any distance and across worlds, but only while the other end's chunk is loaded.
- Both ends pass the protection check, each with the owner of its own network.
- If the destination cannot take the items they go back to the source; if the source cannot take
them back either they drop next to the device that moved them — never into the void.
- The Receiver's menu has a button that opens A's terminal, so you can use A's storage by hand
from B's base (only if you are allowed to access A's land).
5. Shared buses: two controllers on the same cables
If two controllers end up connected (a cable touching both), each one builds its own network and
both include the cables and devices between them. /mvnets doctor, the Probe and the hologram
report it as foreign controller at x,y,z. While that lasts:
- Every shared device still works once per cycle: it is assigned to the first of the two
networks (stable order by world and controller position). Previously every shared grabber,
pusher, purger, pump and crafter worked twice per cycle.
- Shared cells are visible from both terminals.
- Shared DRAM Bays are visible from both networks, like cells. A module recovered from an old controller
waits in that network's Terminal.
The clean fix is to keep one controller per network, and use a Transmitter/Receiver pair if you
really want two networks to exchange items.
6. Fluids
Fluid storage is separate: Quantum Fluid Cells and Fluid DRAM Modules (in DRAM Bays) hold fluids, and
only the Liquid Pump, the Terminal's fluid page, the Terminal's input slot and direct right-clicks on
a fluid cell move them. A deposit fills cells that already hold that fluid first, then Fluid DRAMs,
then empty cells.
Deposits are all-or-nothing: a bucket, bottle or source block is consumed only if its whole
volume fits, so a nearly full network can never keep both the fluid and the bucket.
7. Nothing is lost, nothing is duplicated
- Breaking a node stores its state in the dropped item (cell cargo, filters, face, transit buffer,
Blueprints, crafting grid, receiver link, limiter, fluid, pump filter, chicken sorter rules) and
placing it restores it. The Rake does the same. A DRAM Bay drops each of its modules separately,
with the whole stock inside.
- Pushers never leave more than one stack in a slot and never put anything into another network
node.
- Hoppers cannot touch any device.
- All GUIs have anti-dupe guards and return anything left in real slots when closed.
- Crafting is all-or-nothing, including when only part of the result fits.
- Nodes are immune to pistons and explosions.
💾 Storage and performance
Every placed device keeps its state (filters, cargo, rules, links…) in region files inside the
world folder: <world>/multiversenets/r.<rx>.<rz>.mvn, one file per 32×32 chunks, like
Minecraft's own region files. Nothing is written into the chunk itself.
- No per-chunk limit. A chunk holds as many cables and devices as fit in it. The chunk's own
save does not change, so a dense build never makes a chunk heavy to save or load.
- Cables cost almost nothing. A node still in its default state — every cable, every device
nobody configured — stores only its type and position (20 bytes). Only configured devices store
their full state.
- Off the main thread. A region is read in the background as soon as one of its chunks loads.
Only regions that changed are written: every
storage.autosave-seconds (30 s), on /save-all,
with /mvnets save and on shutdown. The autosave spreads its main-thread work over several ticks
(at most 2 ms per tick), so a busy world never costs one long tick. Each write goes to a temporary file that replaces the old one
in a single move, so a crash leaves the old file or the new one, never half of each.
- In memory only while in use. A region stays loaded while one of its chunks with devices is
loaded and is dropped after it is saved.
- A damaged file never stops the server. A file that fails its checksum is renamed to
.corrupt-<time> (kept for inspection) and that region starts empty.
- The data travels with the world. Copying or backing up the world folder keeps its networks.
- Automatic migration. Chunks written by 5.2 or earlier move their device data out of the chunk
the first time they load after the update; there is nothing to do. The migration is one-way: a
5.2 jar would not see those devices afterwards.
🛡️ Land protection
Supported: ProtectionStones, WorldGuard, Lands, Towny, GriefPrevention (plus BentoBox islands for
player access).
- The Controller remembers who placed it; that player is the network's owner. Controllers from
before this existed adopt the first player allowed to open them.
- The scan does not extend the network into land its owner cannot use, and every block a network
reads from or writes to is checked — grabbers, pushers, overflow to pushers, greedy cells,
vacuum, pump and both ends of a wireless bridge, in either direction.
- Players cannot open devices on protected land they do not own (
multiversenets.protection.bypass
and multiversenets.admin skip it). That includes opening a remote network through a Receiver.
- Escape hatches:
protection.exempt-worlds, protection.exempt-locations, and
protection.block-network-linking: false.
⌨️ Commands
| Command |
Description |
Permission |
/mvnets help |
Command list |
multiversenets.use |
/mvnets guide [en|es] |
Opens the guide menu: every device with its recipe, what it does and how to use it, plus how networks work. English/Spanish toggle inside |
multiversenets.use |
/mvnets give <id> [n] |
Give a device |
multiversenets.admin |
/mvnets doctor |
Rescan and diagnose all networks (also says whether the Slimefun integration is active) |
multiversenets.admin |
/mvnets stats |
Global statistics, including node storage (regions in memory, on disk and waiting to be saved) |
multiversenets.admin |
/mvnets inspect |
Inspect the block you are looking at (type, network, contents, filter) |
multiversenets.admin |
/mvnets repair |
Force a rescan of the network you are looking at |
multiversenets.admin |
/mvnets recipes |
Re-register and re-unlock all crafting recipes |
multiversenets.admin |
/mvnets save |
Save the node region files now instead of waiting for the autosave |
multiversenets.admin |
/mvnets reload |
Reload configuration, protection providers and recipes |
multiversenets.admin |
⚙️ Configuration
The most relevant keys of config.yml (every key is documented in the file itself, in English and
Spanish):
| Key |
Default |
Effect |
network.scan-interval-ticks |
20 |
Minimum gap between rescans of a network that may have changed |
network.full-rescan-ticks |
600 |
Periodic full rescan of an untouched network |
network.max-nodes |
16384 |
Maximum nodes per network |
storage.autosave-seconds |
30 |
Background save interval of the node region files |
network.op-interval-ticks.transfer / vacuum / craft |
5 / 10 / 20 |
Intervals of each family of operations |
transfer.items-per-op |
128 |
Items per Grabber/Pusher/Purger/Receiver operation |
transfer.ht-multiplier |
8 |
Multiplier for Advanced Grabbers/Pushers |
transfer.module-items-per-op |
4096 |
Items a DRAM Loader / Unloader moves per cycle |
transfer.module-fluid-per-op |
64000 |
Fluid (mB) a DRAM Loader / Unloader moves per cycle |
cells.capacities |
65,536 … 2,000,000,000 |
Capacity per cell tier |
virtual-cache.tier-1 … tier-5 |
2,048 … 524,288 |
Capacity of each item memory module tier |
greedy.capacity / barrel.capacity |
262,144 / 2,000,000,000 |
Greedy Cell / Infinity Barrel capacity |
fluids.cell-capacity-mb |
64,000 |
Fluid cell capacity |
fluids.dram-capacity-mb |
512,000 |
Total capacity of a Fluid DRAM Module |
vacuum.radius |
4.0 |
Vacuum pickup radius |
crafter.max-recipes |
18 |
Blueprints per crafter |
wireless.local-range-without-router |
64 |
Wireless Terminal range without a Router |
wireless.combat-cooldown-seconds |
10 |
Wireless Terminal combat lock |
compat.slimefun |
true |
Slimefun machines, cables and barrels integration |
slimefun-machines.enabled |
true |
Master switch of the Slimefun machines (encoder, Auto-Crafter, Stock Crafter, Request Crafter): off = no recipe, cannot be placed, no menu, no work |
slimefun-machines.encoder / slimefun-machines.crafters |
true |
Each Slimefun machine on its own (the old sf-encoder.enabled / sf-crafter.enabled keys still work) |
blocked-worlds |
[] |
Worlds where devices cannot be placed |
protection.* |
— |
See Land protection |
🔗 Slimefun integration (optional)
MultiverseNets does not depend on Slimefun. If it is installed it is detected at startup
(both the DrakesCraft fork and the original) and, with compat.slimefun: true:
- Grabbers, Pushers, Greedy Cells and crafters work with Slimefun machines like with a chest,
using only the slots the machine declares for input and output.
- Inserting follows the machine's own rule, like Networks: each insert tops up the slots that
already hold the item and opens at most one new slot. Machines such as the Electric
Smeltery or the Heated Pressure Chamber only accept an item in the slot that already holds
it, so each ingredient stays in one stack and the other slots remain free for the other
ingredients. Ordinary machines still fill every input slot, one per cycle.
- Slimefun blocks whose id contains
CABLE or BRIDGE conduct a MultiverseNets network, and
Slimefun barrels touching it become part of its storage.
- Slimefun encoder and crafters become usable.
Without Slimefun the bridge stays inert and nothing else changes. /mvnets doctor says on its first
line whether the integration is active.
🤝 Coexistence with Networks
Both plugins can be installed at the same time. Their identifiers never collide:
|
MultiverseNets |
NetworksV6-Drake |
| Plugin name |
MultiverseNets |
NetworksV6-Drake |
| Main class |
com.chagui68.multiversenets.… |
io.github.sefiraat.networks.… |
| Command |
/mvnets |
/networks |
| Permissions |
multiversenets.* |
networks.* |
| Items |
own, via PDC, with vanilla recipes |
Slimefun's (NTW_*) |
Networks registers no vanilla recipes (theirs go through the Slimefun crafting table), so the 66
recipes here do not clash either. Five tests in NetworksCoexistenceTest pin the identifiers down,
because what breaks coexistence is an identifier renamed by accident, not the code.
Interactions to keep in mind with the Slimefun integration active: a MultiverseNets Grabber can
pull from a Networks block (it is a Slimefun item with its own menu), and a Networks block whose id
contains CABLE or BRIDGE (e.g. NTW_BRIDGE) conducts a MultiverseNets network. If you prefer
each network to stick to its own blocks:
compat:
slimefun: false
🔍 How it differs from Networks
|
Networks (Slimefun addon) |
MultiverseNets |
| Dependencies |
Slimefun + its chain |
None, only the Paper API |
| Network membership |
Each node stores its root |
Recalculated by BFS from the controller |
| Orphan nodes |
Possible |
Structurally impossible: every scan rebuilds the topology |
| Diagnosis |
Added later (/networks doctor) |
/mvnets doctor, Probe, Monitor, hologram |
| Ticker |
Slimefun's cycle |
Own, with per-operation intervals in the config |
| Node data |
Slimefun's BlockStorage |
Own region files in the world folder, saved off the main thread; cables and unconfigured devices store only their type |
The price is that scanning costs one BFS over up to max-nodes blocks — predictable, bounded work
in exchange for no state that can be corrupted. It only runs when something may have changed, plus
once every full-rescan-ticks to catch what no event reports (land claims, blocks edited by other
plugins).
🛠️ Building
mvn clean package
That builds the release jar (1.21.11 API, Java 21 bytecode, runs on 1.21.11, 26.1 and 26.2). To
check the code against the newer APIs (needs JDK 25):
mvn -P api-26.1 clean compile
mvn -P api-26.2 clean compile
The jar is generated at target/MultiverseNets-v<version>.jar.
📋 Compatibility
| Parameter |
Requirement |
| Server |
Paper / Purpur 1.21.11, 26.1 (26.1 – 26.1.2) and 26.2 — the same jar for all three |
| Java |
The one your server needs: Java 21 on 1.21.11, Java 25 on 26.1 and 26.2 |
How each version is checked before a release (.github/workflows/verify.yml):
| Version |
Check |
| 1.21.11 |
The jar is built against this API and the whole test suite runs on it. |
| 26.1 |
The same sources compile against the Paper 26.1.2 API (mvn -P api-26.1 clean compile, JDK 25). |
| 26.2 |
The same sources compile against the Paper 26.2 API (mvn -P api-26.2 clean compile, JDK 25). |
The test server (MockBukkit) only exists for 1.21, so on 26.x the check is that every call the
plugin makes exists there; nothing it uses is marked for removal in those versions.
| Dependencies | None (Slimefun and protection plugins are optional) |
Not Folia-compatible. The network ticker, the topology scan and every GUI run on Paper's
global scheduler and assume the main thread owns the blocks they touch. Install it on Paper or
Purpur.
📄 License & Sovereign Authorship
Copyright © 2026 Chagui68 · Slimefun: New Horizons.
This project is an original sovereign creation engineered by Chagui68 for the DrakesCraft network. All intellectual authorship belongs to Chagui68. Commercial resale, repackaging in paid setups, or removing creator attribution is strictly prohibited.
评论 0
登录后参与评分
还没有评论,来抢沙发吧