-- 你知道我们有 Discord 吗? --
? Azentials
为 NeoForge 服务器打造的现代化、可配置的必备功能模组
Minecraft 1.21.1 · NeoForge · Java 21
以服务器为中心 · 客户端可选安装
通过一套统一且以服务器为中心的架构,提供家园、传送点、玩家工具、套装、管理工具等功能。
Azentials 是 Arctic's Essentials 的完全重写版后继者,基于共享基础设施重建,具备更安全的持久化机制、可配置权限以及可预测的服务器权威行为。
⚠️ 强烈建议提交 Bug 报告
Azentials 与许多服务器系统交互,包括传送、物品栏、持久化存储、权限、消息传递和玩家状态。
我是一名独立开发者,无法测试每一种可能的服务器设置或极端情况。因此,如果您遇到 Bug 或兼容性问题,请加入 Discord 并提交报告。
? 功能特性
- ? 家园 (Homes) - 创建和管理持久的个人传送位置
- ? 服务器传送点 (Server warps) - 由管理员管理的、对玩家可用的目的地
- ? 出生点与返回 (Spawn and Back) - 可配置的服务器出生点,支持记录离开前的位置和死亡历史
- ? 传送请求 (Teleport requests) -
/tpa 和 /tpahere,附带可点击的接受和拒绝控件
- ? 随机传送 (Random teleportation) - 带有可配置搜索限制和冷却时间的有界异步 RTP
- ⏱️ 共享传送生命周期 - 统一的预热时间、冷却时间、取消规则和目的地验证
- ?️ 安全传送验证 - 检查世界边界、站立空间、支撑物、流体、危险方块及维度访问权限
- ? AFK 与玩家状态 - 手动或自动 AFK、
/seen 指令以及持久化的游戏时长统计
- ? 私聊消息 -
/msg、/reply、屏蔽控制以及员工帮助请求
- ? 服务器信息 - 可配置的
/rules 和 /motd
- ? 便携工具 - 工作台、末影箱、垃圾桶菜单以及可配置的套装 (kits)
- ❤️ 管理工具 - 治疗、喂食、飞行、上帝模式、修复、广播以及实时物品栏编辑
- ? 权限感知命令 - NeoForge 权限节点,支持可选的外部提供商集成
- ? 受验证的持久化 - 阻止损坏或不支持的数据,而不是静默覆盖
- ? 以服务器为中心的设计 - 普通玩家无需在客户端安装 Azentials
- ?️ 可选增强的客户端 UI - 安装了 Azentials 的玩家可获得精美的物品栏编辑器,而原版客户端保留完整功能
? 家园
玩家可以创建和管理命名家园:
/sethome [name]
/home [name]
/delhome [name]
/homes
家园支持可配置的限制数量、传送预热时间、冷却时间以及 Azentials 共享的传送安全系统。
默认限制为每名玩家 3 个家园。
? 传送点
Azentials 提供持久的全服务器范围传送点:
/warp [name]
/setwarp <name>
/delwarp <name>
/warps
默认情况下,只有管理员可以创建和删除传送点,而普通玩家可以使用已配置的目的地。
? 出生点与返回
出生点
/spawn
/setspawn
/delspawn
在管理员创建自定义的 Azentials 出生点之前,/spawn 将回退到原版主世界的出生点。
返回
Azentials 会记录玩家在每次成功使用 Azentials 传送前所在的位置。
默认情况下,还会记录玩家最近一次死亡的位置。
成功使用 /back 会记录离开时的位置,允许玩家在两个最近的位置之间移动。
? 传送请求
Azentials 包含轻量级的玩家间传送请求功能:
/tpa <player>
/tpahere <player>
/tpaccept
/tpdeny
/tpcancel
/tptoggle
传入的请求包含可点击的 Accept(接受)和 Deny(拒绝)聊天控件。
每个按钮都与创建它的特定请求绑定,因此旧按钮不会意外接受或拒绝新的请求。
玩家可以通过 /tptoggle 持久禁用传入的传送邀请。
每位玩家只能有一个 outgoing(发出)请求,每个目标玩家只能有一个 incoming(接收)请求。请求会自动过期,当任一玩家下线时也会被移除。
? 随机传送
/rtp 在世界共享出生点周围的可配置环形区域内进行搜索。
Azentials 不会同步等待地形生成。
相反,RTP 采用以下策略:
- 使用公平的服务器全局队列
- 一次最多请求一个候选区块
- 在后续的服务器刻中检查区块是否就绪
- 限制候选区块的频率
- 限制区块加载量和总搜索时间
- 支持通过
/tpcancel 取消
- 在取消或失败的搜索后应用重试冷却时间
- 确保成功的目的地在任何配置的传送预热时间内保持加载状态
默认 RTP 范围为 500 到 5,000 格,最多尝试 24 次。
⏱️ 共享传送系统
家园、传送点、出生点、返回、TPA 和 RTP 均使用同一个共享的传送生命周期。
这确保了各功能的行为保持一致。
一名玩家同时只能有一个活跃的传送或 RTP 搜索。
活跃的传送可以通过以下方式取消:
- 死亡
- 重生
- 登出
- 维度切换
- 预热期间移动
- 受伤(如果已配置)
待处理的 TPA 邀请与活跃的传送操作是分开的。
每个传送功能都可以拥有独立的预热时间和冷却时间设置。
?️ 传送安全
在移动玩家之前,Azentials 会立即验证目的地。
检查项目包括:
- 世界边界
- 站立空间
- 玩家下方的支撑物
- 流体
- 已知的危险方块
- 维度可用性
台阶、楼梯和地毯可以提供有效的支撑。
不安全的目的地将被拒绝,而不是将玩家移动到猜测的附近位置。
失败的安全检查不会消耗成功的传送冷却时间,也不会修改 /back 记录。
? AFK、在线状态与游戏时长
AFK
/afk [reason]
玩家可以手动切换 AFK 状态,并可选择提供理由。
任何活动都会自动清除 AFK 状态。
自动闲置检测默认设置为 5 分钟,且可以禁用。
查看状态 (Seen)
/seen <player>
显示玩家是否在线、是否处于 AFK(空闲)状态,或已离线多久。
支持查询之前记录的昵称和 UUID,用于离线玩家的查找。
游戏时长
/playtime [player]
显示累计游戏时长,包括 AFK 时间。
新的 Azentials 用户档案将从 Minecraft 现有的游戏时长统计数据中初始化。
查询其他玩家的游戏时长需要额外的权限。
? 消息传递
Azentials 提供玩家间的私聊功能:
/msg <player> <message>
/tell <player> <message>
/w <player> <message>
/reply <message>
/r <message>
/ignore <player>
私聊功能保留了 Minecraft 正常的签名消息传递和过滤机制。
/reply 命令会回复该玩家最近的一条私聊对话。
当玩家登出时,回复目标会被清除。
被忽略的玩家之间无法进行私聊,也无法发送 TPA(传送请求)。
忽略某人不会过滤公共聊天内容。
? 员工求助
/helpop <message>
玩家可以向拥有接收权限的在线工作人员以及服务器控制台发送消息。
请求之间的默认冷却时间为 30 秒。
? 规则与 MOTD
这两个命令均会显示由服务器管理员配置的纯文本行内容。
? Ping 值
/ping [player]
显示玩家的延迟(以毫秒为单位)。
默认情况下,玩家可以检查自己的 Ping 值。
检查其他玩家的 Ping 值需要额外的权限。
? 玩家实用工具
垃圾桶
/trash
打开一个类似原版风格的物品处置菜单。
留在菜单内的物品会在菜单关闭时被删除。
光标上的物品会正常返还。
工作台
打开一个便携式的原版合成台。
未使用的合成材料会在菜单关闭时返还。
末影箱
打开玩家真实的末影箱背包。
? 套装 (Kits)
服务器可以配置带有持久化冷却时间的可重复使用物品套装。
套装支持以下特性:
- 自定义名称
- 可配置的冷却时间
- 每个套装最多包含 36 组物品
- 最多配置 256 个套装
- 持久化的冷却时间追踪
- 交付前的完整背包空间验证
只有当整个套装都能放入背包时,才会发放套装。
领取失败不会消耗套装的冷却时间。
套装数据从以下文件加载:
config/azentials-kits.json
Azentials 不会通过套装执行任意命令或加载任意物品数据。
❤️ 管理员命令
Azentials 包含专注的管理员实用工具:
/heal [player]
/feed [player]
/fly [player] [on|off]
/god [player] [on|off]
/repair [player]
/invsee <player>
/broadcast <message>
这些命令默认需要操作者等级 2。
对除自己以外的玩家使用 heal、feed、fly、god 或 repair 命令,还需要相应的 .others 权限。
? 背包编辑器
/invsee <player>
Azentials 包含一个面向在线玩家的实时物品栏编辑器。
当客户端和服务器都安装了最新版本的 Azentials 时,/invsee 命令会使用 Minecraft 原版容器纹理打开一个自定义界面。
该界面的布局包括:
- 目标玩家的物品栏和快捷栏
- 目标玩家的护甲槽位
- 目标玩家的主手/副手槽位(offhand)
- 你自己的物品栏和快捷栏
- 与目标玩家物品的实时同步
你可以正常拖拽物品,或在不同物品栏之间转移物品。
按住 Shift 键点击可在玩家之间转移物品。
护甲槽位仅接受有效的装备,且每个槽位只能容纳一件物品。
所有更改会立即应用到真实物品栏中。
可选的客户端增强
自定义物品栏界面是可选的。
未安装 Azentials 或使用不含自定义界面的旧版客户端的玩家,将收到一个功能正常的原版六行物品栏界面。
使用 /invsee 无需任何客户端模组或资源包。
这使得服务器管理员可以将 Azentials 完全保留在服务器端,同时为拥有客户端模组的玩家提供更简洁的界面。
? 以服务器为中心的设计
Azentials 主要设计为服务端模组。
玩家可以在本地不安装 Azentials 的情况下连接服务器。
核心命令、传送、工具、权限、持久化、预设箱(Kits)以及管理系统均保持服务器权威。
在客户端安装 Azentials 可启用可选的客户端增强功能,例如改进的物品栏编辑器界面。
在单人游戏中,由于客户端和集成服务器都安装了 Azentials,因此自动使用增强界面。
? 权限
Azentials 集成了 NeoForge 的权限 API。
不需要单独的权限提供者。
如果没有配置外部权限提供者,Azentials 会使用其内置的默认值。
大多数玩家命令默认允许执行。
管理命令通常需要操作者等级 2。
示例如下:
azentials.command.home
azentials.command.sethome
azentials.command.warp
azentials.command.spawn
azentials.command.back
azentials.command.tpa
azentials.command.rtp
azentials.command.msg
azentials.command.afk
azentials.command.kit
azentials.command.invsee
azentials.command.broadcast
其他权限节点控制针对其他玩家的操作等权限。
支持整数值的权限提供者还可以覆盖诸如最大家园数量、传送冷却时间等数值。
⚙️ 配置
Azentials 按用途分离其配置文件。
主要的传送和服务器设置存储在:
config/azentials-common.toml
玩家工具设置存储在:
config/azentials-utilities.toml
预设箱(Kits)存储在:
config/azentials-kits.json
家园、传送点、出生点、返回、TPA 和 RTP 系统各自拥有独立的启用开关。
更改功能启用开关需要重启服务器。
被禁用的功能不会注册其对应的命令。
其他兼容的配置值可以通过 NeoForge 进行热重载。
⏱️ 默认传送设置
| 功能 |
预热时间 |
冷却时间 |
其他默认设置 |
| 家 (Homes) |
3 秒 |
10 秒 |
每名玩家 3 个家 |
| 传送点 (Warps) |
3 秒 |
10 秒 |
跨维度旅行 |
| 出生点 (Spawn) |
3 秒 |
10 秒 |
跨维度旅行 |
| 返回 (Back) |
3 秒 |
10 秒 |
记录死亡位置 |
| TPA |
3 秒 |
10 秒 |
请求在 60 秒后过期 |
| RTP |
0 秒 |
60 秒 |
半径 500 至 5,000 格,24 次尝试 |
传送计时使用服务器刻(ticks)。
如果服务器运行严重滞后,配置的预热和冷却时间在现实中可能会更长。
? 持久化数据
Azentials 将持久化服务器数据存储在主世界(overworld)的 data 目录中。
当前包含的文件有:
azentials_homes.dat
azentials_warps.dat
azentials_spawn.dat
azentials_back.dat
azentials_players.dat
玩家数据包括以下信息:
- 最后上线时间
- 游戏时长
- 传送偏好设置
- 忽略的玩家列表
- 套件(Kit)冷却时间
?️ 数据安全
当持久化数据看起来损坏或不兼容时,Azentials 会故意采取保守策略。
损坏的文件、无效的记录、重复的记录或不受支持的架构都会阻止该存储被替换或截断,而是将其保留原样。
发生这种情况时:
- 命令会报告受影响的存储系统不可用
- 服务器日志会标识受影响的存储及其原因
- 原始文件受到保护,防止写入
这避免了无声地销毁可恢复的服务器数据。
进行备份时,请包括 Azentials 数据文件、两个 TOML 配置文件以及套件 JSON 文件。
在复制或还原持久化数据之前,请先停止服务器。
? 命令命名空间
所有主要的 Azentials 命令也均可通过 /azentials 调用。
例如:
/home
也可以用作:
/azentials home
这允许服务器避免与其他模组或插件发生根命令冲突。
/azentials 和 /azentials help [page] 会显示当前玩家有权使用的已启用命令。
? 安装
- 下载 Azentials JAR 文件
- 将其放入服务器的
mods 文件夹中
- 启动服务器
- 通过生成的配置文件配置 Azentials
如需增强的客户端界面,请在客户端安装相同版本的 Azentials。
客户端安装为可选操作。
? 要求
- Minecraft: 1.21.1
- 加载器: NeoForge 21.1.235 或兼容的后续 21.1.x 版本
- Java: Java 21
- 客户端模组: 可选
? Arctic's Essentials 的继任者
Azentials 是 Arctic's Essentials 的全面继任者。
该项目保留了最初的目标,即提供实用的服务器工具而无需不必要的冗余,但其内部架构已围绕较新的系统进行了重建,用于:
- 传送生命周期协调
- 权限处理
- 持久化存储
- 目的地安全性
- 客户端兼容性
- 库存同步
- 自动化测试
- 服务器管理
Azentials 是一个全新的实现,而非原始 Arctic's Essentials 代码库的延续。
? 可靠性与测试
Azentials 包含自动化的单元测试和 Minecraft GameTests,涵盖核心行为,例如:
- 传送到达安全性
- 取消的维度旅行
- 共享的传送生命周期行为
- 权限回退
- 配置
- 持久化
- 库存检查行为
开发构建版还使用无头服务器环境和协议级冒烟测试进行测试。
冒烟测试系统可以连接 vanilla 协议测试客户端(无需 Azentials 客户端模组),以验证仅服务端的兼容性。
? 许可与权限
保留所有权利 (ARR)
您被允许:
- ✔ 在服务器上使用该模组
- ✔ 将该模组包含在整合包中
- ✔ 作为整合包的一部分分发未修改的模组
您不得:
- ❌ 在其他网站上重新上传该模组
- ❌ 分发修改后的版本
- ❌ 声称该模组、代码或资产归自己所有
如需在整合包之外进行分发请求,请联系作者。
由 Azora Development 开发与维护。
-- Did you know we have a discord? --
? Azentials
Modern, configurable essentials for NeoForge servers
Minecraft 1.21.1 · NeoForge · Java 21
Server-first · Client optional
Homes, warps, teleportation, player utilities, kits, administration tools, and more through one consistent server-first system.
Azentials is the ground-up successor to Arctic's Essentials, rebuilt around shared infrastructure, safer persistence, configurable permissions, and predictable server-authoritative behavior.
⚠️ Bug reports strongly encouraged
Azentials interacts with many server systems including teleportation, inventories, persistence, permissions, messaging, and player state.
I’m one developer and cannot test every possible server setup or edge case, so if you encounter a bug or compatibility issue, please join the Discord and report it.
? Features
- ? Homes - create and manage persistent personal teleport locations
- ? Server warps - administrator-managed destinations available to players
- ? Spawn and Back - configurable server spawn with persistent previous-location and death history
- ? Teleport requests -
/tpa and /tpahere with clickable Accept and Deny controls
- ? Random teleportation - bounded asynchronous RTP with configurable search limits and cooldowns
- ⏱️ Shared teleport lifecycle - consistent warmups, cooldowns, cancellation rules, and destination validation
- ?️ Safe teleport validation - checks world bounds, standing space, support, fluids, dangerous blocks, and dimension access
- ? AFK and player status - manual or automatic AFK,
/seen, and persistent playtime
- ? Private messaging -
/msg, /reply, ignore controls, and staff help requests
- ? Server information - configurable
/rules and /motd
- ? Portable utilities - crafting table, ender chest, trash menu, and configurable kits
- ❤️ Administration tools - heal, feed, fly, god mode, repair, broadcasts, and live inventory editing
- ? Permission-aware commands - NeoForge permission nodes with optional external provider support
- ? Validated persistence - damaged or unsupported data is blocked instead of silently overwritten
- ? Server-first design - normal players do not need Azentials installed on their client
- ?️ Optional enhanced client UI - players with Azentials installed get a polished inventory editor while vanilla clients retain full functionality
? Homes
Players can create and manage named homes:
/sethome [name]
/home [name]
/delhome [name]
/homes
Homes support configurable limits, teleport warmups, cooldowns, and the shared Azentials teleport safety system.
The default limit is 3 homes per player.
? Warps
Azentials provides persistent server-wide warps:
/warp [name]
/setwarp <name>
/delwarp <name>
/warps
Warp creation and removal default to operators while normal players can use configured destinations.
? Spawn and Back
Spawn
/spawn
/setspawn
/delspawn
Until an administrator creates a custom Azentials spawn, /spawn falls back to the vanilla overworld spawn.
Back
Azentials records the location a player leaves before every successful Azentials teleport.
By default, a player's most recent death location is also recorded.
Using /back successfully records the location being left, allowing players to move between two recent locations.
? Teleport Requests
Azentials includes lightweight player-to-player teleport requests:
/tpa <player>
/tpahere <player>
/tpaccept
/tpdeny
/tpcancel
/tptoggle
Incoming requests include clickable Accept and Deny chat controls.
Each button is tied to the exact request that created it, so an old button cannot accidentally accept or deny a newer request.
Players can persistently disable incoming teleport invitations with /tptoggle.
Each player may have one outgoing request and each target may have one incoming request. Requests expire automatically and are removed when either player leaves.
? Random Teleport
/rtp searches a configurable ring around the world's shared spawn.
Azentials does not synchronously wait for terrain generation.
Instead, RTP:
- Uses a fair server-wide queue
- Requests at most one candidate chunk at a time
- Checks chunk readiness on later server ticks
- Limits candidate frequency
- Bounds chunk loading and total search time
- Supports cancellation through
/tpcancel
- Applies a retry cooldown after cancelled or failed searches
- Keeps a successful destination loaded through any configured teleport warmup
The default RTP range is 500 to 5,000 blocks with up to 24 attempts.
⏱️ Shared Teleport System
Homes, Warps, Spawn, Back, TPA, and RTP all use one shared teleport lifecycle.
This keeps behavior consistent across features.
A player may have one active teleport or RTP search at a time.
Active teleports can be cancelled by:
- Death
- Respawn
- Logout
- Dimension changes
- Movement during a warmup
- Damage when configured
Pending TPA invitations remain separate from active teleport operations.
Each teleport feature can have its own warmup and cooldown settings.
?️ Teleport Safety
Immediately before moving a player, Azentials validates the destination.
Checks include:
- World boundaries
- Standing space
- Support beneath the player
- Fluids
- Known dangerous blocks
- Dimension availability
Slabs, stairs, and carpets can provide valid support.
Unsafe destinations are rejected instead of moving the player to a guessed nearby position.
Failed safety checks do not consume the successful teleport cooldown or modify /back.
? AFK, Seen, and Playtime
AFK
/afk [reason]
Players can manually toggle AFK status and optionally provide a reason.
Activity automatically clears AFK.
Automatic idle detection defaults to 5 minutes and can be disabled.
Seen
/seen <player>
Shows whether a player is online, AFK, or how long they have been offline.
Previously recorded usernames and UUIDs are supported for offline lookups.
Playtime
/playtime [player]
Displays accumulated playtime, including AFK time.
New Azentials profiles initialize from Minecraft's existing playtime statistic.
Looking up another player's playtime requires an additional permission.
? Messaging
Azentials provides private player messaging:
/msg <player> <message>
/tell <player> <message>
/w <player> <message>
/reply <message>
/r <message>
/ignore <player>
Private messaging preserves Minecraft's normal signed-message delivery and filtering.
/reply targets the player's most recent private conversation.
Reply targets clear when a player logs out.
Ignored players cannot privately message each other or send TPA requests.
Ignoring does not filter public chat.
? Staff Requests
/helpop <message>
Players can send a message to online staff members with the receive permission and to the server console.
The default cooldown is 30 seconds between requests.
? Rules and MOTD
Both commands display configurable plain-text lines defined by the server owner.
? Ping
/ping [player]
Displays a player's latency in milliseconds.
Players can check their own ping by default.
Checking another player's ping requires an additional permission.
? Player Utilities
Trash
/trash
Opens a vanilla-style disposal menu.
Items left inside are deleted when the menu closes.
The cursor item is returned normally.
Workbench
Opens a portable vanilla crafting table.
Unused crafting ingredients are returned when the menu closes.
Ender Chest
Opens the player's real ender chest inventory.
? Kits
Servers can configure reusable item kits with persistent cooldowns.
Kits support:
- Custom names
- Configurable cooldowns
- Up to 36 item stacks per kit
- Up to 256 configured kits
- Persistent cooldown tracking
- Full inventory-space validation before delivery
A kit is only delivered if the entire kit fits.
Failed claims do not consume the kit cooldown.
Kit data is loaded from:
config/azentials-kits.json
Azentials does not execute arbitrary commands or load arbitrary item data through kits.
❤️ Administrator Commands
Azentials includes focused administration utilities:
/heal [player]
/feed [player]
/fly [player] [on|off]
/god [player] [on|off]
/repair [player]
/invsee <player>
/broadcast <message>
These commands default to operator level 2.
Targeting another player with heal, feed, fly, god, or repair additionally requires the corresponding .others permission.
? Inventory Editor
/invsee <player>
Azentials includes a live inventory editor for online players.
When both the client and server have the current version of Azentials installed, /invsee opens a custom screen using Minecraft's normal container textures.
The layout includes:
- Target inventory and hotbar
- Target armor slots
- Target offhand slot
- Your own inventory and hotbar
- Live synchronization with the target player
Items can be dragged normally or transferred between inventories.
Shift-clicking transfers items between players.
Armor slots only accept valid equipment and hold one item.
Changes apply immediately to the real inventory.
Optional client enhancement
The custom inventory screen is completely optional.
Clients without Azentials, or clients using an older version without the custom screen, receive a functional vanilla six-row inventory interface instead.
No client mod or resource pack is required to use /invsee.
This allows server owners to keep Azentials completely server-side while still giving players with the client mod a cleaner interface.
? Server-First Design
Azentials is designed primarily as a server mod.
Players can connect without installing Azentials locally.
Core commands, teleportation, utilities, permissions, persistence, kits, and administration systems remain server-authoritative.
Installing Azentials on the client enables optional client-side improvements such as the enhanced inventory editor interface.
Singleplayer automatically uses the enhanced interface because the client and integrated server both have Azentials installed.
? Permissions
Azentials integrates with NeoForge's Permission API.
A separate permissions provider is not required.
Without one, Azentials uses its built-in defaults.
Most player commands are allowed by default.
Administration commands generally require operator level 2.
Examples include:
azentials.command.home
azentials.command.sethome
azentials.command.warp
azentials.command.spawn
azentials.command.back
azentials.command.tpa
azentials.command.rtp
azentials.command.msg
azentials.command.afk
azentials.command.kit
azentials.command.invsee
azentials.command.broadcast
Additional permission nodes control actions such as targeting other players.
Permission providers that support integer values can also override values such as maximum home counts and teleport timing.
⚙️ Configuration
Azentials separates its configuration by purpose.
Main teleport and server settings are stored in:
config/azentials-common.toml
Player utility settings are stored in:
config/azentials-utilities.toml
Kits are stored in:
config/azentials-kits.json
The Homes, Warps, Spawn, Back, TPA, and RTP systems each have their own enable switch.
Changing feature enable switches requires a server restart.
Disabled features do not register their commands.
Other compatible configuration values can reload through NeoForge.
⏱️ Default Teleport Settings
| Feature |
Warmup |
Cooldown |
Other defaults |
| Homes |
3 seconds |
10 seconds |
3 homes per player |
| Warps |
3 seconds |
10 seconds |
Cross-dimension travel |
| Spawn |
3 seconds |
10 seconds |
Cross-dimension travel |
| Back |
3 seconds |
10 seconds |
Death locations recorded |
| TPA |
3 seconds |
10 seconds |
Requests expire after 60 seconds |
| RTP |
0 seconds |
60 seconds |
500 to 5,000 block radius, 24 attempts |
Teleport timing uses server ticks.
If the server is running significantly behind, configured warmups and cooldowns may take longer in real time.
? Persistent Data
Azentials stores persistent server data inside the overworld's data directory.
Current files include:
azentials_homes.dat
azentials_warps.dat
azentials_spawn.dat
azentials_back.dat
azentials_players.dat
Player data includes information such as:
- Last seen time
- Playtime
- Teleport preferences
- Ignored players
- Kit cooldowns
?️ Data Safety
Azentials is intentionally conservative when persistent data appears damaged or incompatible.
A damaged file, invalid record, duplicate record, or unsupported schema blocks that store instead of silently replacing or trimming it.
When this happens:
- Commands report that the affected storage system is unavailable
- The server log identifies the affected store and reason
- The original file is protected from writes
This avoids silently destroying recoverable server data.
For backups, include the Azentials data files, both TOML configuration files, and the kit JSON file.
Stop the server before copying or restoring persistent data.
? Command Namespace
All major Azentials commands are also available under /azentials.
For example:
/home
can also be used as:
/azentials home
This allows servers to avoid root-command conflicts with other mods or plugins.
/azentials and /azentials help [page] show enabled commands that the current player has permission to use.
? Installation
- Download the Azentials JAR
- Place it in the server's
mods folder
- Start the server
- Configure Azentials through the generated configuration files
For the enhanced client interface, install the same Azentials version on the client.
Client installation is optional.
? Requirements
- Minecraft: 1.21.1
- Loader: NeoForge 21.1.235 or compatible later 21.1.x
- Java: Java 21
- Client mod: Optional
? Successor to Arctic's Essentials
Azentials is the ground-up successor to Arctic's Essentials.
The project retains the original goal of providing practical server utilities without unnecessary bloat, but its internal architecture has been rebuilt around newer systems for:
- Teleport lifecycle coordination
- Permission handling
- Persistent storage
- Destination safety
- Client compatibility
- Inventory synchronization
- Automated testing
- Server administration
Azentials is a new implementation rather than a continuation of the original Arctic's Essentials codebase.
? Reliability and Testing
Azentials includes automated unit tests and Minecraft GameTests covering core behavior such as:
- Teleport arrival safety
- Cancelled dimension travel
- Shared teleport lifecycle behavior
- Permission fallbacks
- Configuration
- Persistence
- Inventory inspection behavior
Development builds are also tested using headless server environments and protocol-level smoke tests.
The smoke test system can connect vanilla-protocol test clients without the Azentials client mod to verify server-only compatibility.
? License & Permissions
All Rights Reserved (ARR)
You are allowed to:
- ✔ Use this mod on servers
- ✔ Include this mod in modpacks
- ✔ Distribute the mod unchanged as part of a modpack
You may not:
- ❌ Reupload the mod on other websites
- ❌ Redistribute modified versions
- ❌ Claim the mod, code, or assets as your own
For redistribution requests outside of modpacks, contact the author.
Developed and maintained by Azora Development.
评论 0
登录后参与评分
还没有评论,来抢沙发吧