这些驱动器根据为每个驱动器设置的频率相互链接。所有具有相同频率和隐私级别的驱动器共享相同的内容,无论它们是由谁制作的。无论是在你的 AE2 系统中、另一个维度中,还是在其他玩家的系统中,内容都是全局同步的。
EnderDrives
EnderDrives 是一款模组,提供了一种将物品存储在末地——但以数字形式。每种驱动器根据其容量有类型数量限制。
这是一种出于游戏玩法机制的人工限制,而非存储能力的限制,但强烈建议尽量保持系统中的类型数量最少。
该系统已可靠测试支持高达 250,000 种类型。超过此数值请谨慎操作。
传输模式
双向:
设置为双向(默认)的驱动器提供正常的磁盘驱动器功能。你可以像往常一样输入/提取物品。
输入:
设置为输入的驱动器仅允许玩家和自动化系统向其中输入物品。你可以查看堆叠情况,但无法移除它们。
输出:
设置为输出的驱动器仅允许玩家和自动化系统从驱动器中提取物品,永远不会插入。
范围 / 隐私选项
全局:
在此范围内存储的物品将在整个服务器范围内共享。任何拥有设置为相同频率驱动器的玩家都可以访问相同的共享库存。
私有:
处于私有模式的驱动器与你的 UUID 绑定,只有你能将其分配到自己的私有空间。其他玩家可以通过你的 ME 系统使用该驱动器,但库存仅属于你一人。
团队:
团队驱动器可由你的 FTB Team 中的所有成员访问。任何成员都可以制作一个驱动器并将其设置为团队频率。内部数据绑定到队伍所有者的 UUID,因此即使队伍解散,原始所有者仍然可以访问。
由 EnderDB 提供支持
为了处理如此大规模的存储,EnderDrives 使用了一个专门构建的数据库 EnderDB。所有物品都以其完整的数据组件(NBT)进行存储,确保在识别和追踪物品时的完美准确性。
每个存储的物品都按其 频率、范围 和 完整 NBT 以及 数量 进行索引。数量以带符号的 64 位长整型存储,允许单个记录中最多包含 9 千万亿个物品。
EnderDB 特性
EnderDB 的目标是 速度、可靠性 和 效率。EnderDB 使用了:
- 旋转预写日志(WAL) 用于数据完整性
- 批量提交 用于性能优化
- CRC32 校验和 用于数据完整性
- 紧凑二进制存储 用于性能优化
- 内存缓存 用于性能优化
- 专用后台线程
- 安全处理关闭和崩溃
所有操作均为 原子性,确保 即使在世界损坏或服务器故障的情况下也绝不会丢失或损坏任何数据。
数据保存在你的世界文件夹中:
saves/world/data/enderdrives/enderdrives.bin
预写日志(WAL)文件与该文件一起存储,用于恢复和性能优化。
These drives link together based on the frequency set for each drive. All drives with the same frequency and privacy share the same contents, regardless of who crafted them. Whether in your AE2 system, another dimension, or on another player’s system, the contents are globally synchronized.
EnderDrives
EnderDrives is a mod that offers a way to store your items in the End — but digitally. Each drive has a type limit based on its capacity.
This is an artificial limit for gameplay mechanics, not due to storage limitations, but it is heavily suggested to try and keep the least amount of types in the system as possible.
The system has been reliably tested up to 250,000 types. Exceed that with caution.
Transfer Mode
Bidirectional:
Drives set to Bidirectional (default) facilitate normal disk drive function. You are able to input/extract items like normal.
Input:
Drives set to Input will only allow the player and automations to input items. You are able to view the stacks, but you will be unable to remove them.
Output:
Drives set to Output will only allow the player and automations to pull from the drive, never insert.
Scope / Privacy Options
Global:
Items stored under this scope are shared server-wide. Any player with a drive set to the same frequency can access the same shared inventory.
Private:
Drives in private mode are tied to your UUID and only you can assign them to your private space. Other players can use the drive through your ME system, but the inventory is yours alone.
Team:
Team drives are accessible by all members of your FTB Team. Any member can craft a drive and set it to a team frequency. Internally, the data is tied to the party owner’s UUID, so even if the team disbands, the original owner still has access.
Powered by EnderDB
To handle storage at such large scales, EnderDrives uses a purpose-built database called EnderDB. All items are stored with their full data component (NBT), ensuring perfect accuracy in identifying and tracking items.
Each stored item is indexed by its frequency, scope, and full NBT, along with a count. The count is stored as a signed 64-bit long, allowing up to 9 quintillion items in a single record.
EnderDB Features
The goal of EnderDB is speed, reliability, and efficiency. EnderDB uses:
- Rotating Write-Ahead Logging (WAL) for data integrity
- Batch Commits for performance
- CRC32 Checksums for data integrity
- Compact Binary Storage for performance
- In-Memory Caching for performance
- Dedicated Background Threading
- Safe Handling of Shutdowns and Crashes
All operations are atomic, ensuring that no data is ever lost or corrupted, even in the event of world corruption or server failure.
Data is saved in your world folder:
saves/world/data/enderdrives/enderdrives.bin
Write-ahead log (WAL) files are stored alongside this file for recovery and performance.
评论 0
登录后参与评分
还没有评论,来抢沙发吧