-- Did you know we have a discord? https://discord.gg/J6h8NzdgCK --

🧰 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

/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

/rules
/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

/workbench
/craft

Opens a portable vanilla crafting table.

Unused crafting ingredients are returned when the menu closes.

Ender Chest

/enderchest
/ec

Opens the player's real ender chest inventory.

🎁 Kits

/kit [name]
/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

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.

Azentials - Server Essentials

Compatibility

Minecraft: Java Edition

Platforms

Supported environments

Links

Tags

Creators

Details