Skip to main content

TDUtilities feature reference

Mod version shipped with FlammiCraft: 1.32.0

Handbook overview

Little Big Redstone integrations formerly documented here moved to the Little Big Redstone fork in TDUtilities 1.15.0.

Performance HUD

Use /tdu hud to toggle a personal performance overlay, or /tdu hud on and /tdu hud off to set its state. Visibility is saved and restored on reconnect. Both client and server need a version supporting this feature; no operator permission is required.

Use /tdu hud bossbar for a native top-centre bossbar showing TPS, average MSPT and player-list ping, and /tdu hud panel for the side panel. Each command toggles its view. Both accept on and off to set an explicit state, for example /tdu hud bossbar off. When both are enabled, the panel shows P95/maximum MSPT and FPS; TPS, mean MSPT and ping appear only in the bossbar. Disabling the bossbar restores these panel rows. Commands save both views and overall visibility across disconnects and game restarts. /tdu hud off hides both views; /tdu hud on restores the selection, enabling the panel if neither view is selected. The bossbar uses the same server data and works with servers supporting the original performance HUD.

The bossbar has ten segments, each representing 10% of the average tick budget (5 ms at 20 TPS). It is green below 50%, yellow from 50% to below 100%, and red at 100% or above. At 20 TPS, yellow starts at 25 ms and red at 50 ms; thresholds follow the configured server tick rate. Yellow is an early reserve warning, while 100% means the average tick uses the entire target budget. The title includes the unclipped percentage, so overload above 100% remains visible even with a full bar. Missing data shows the waiting/stale message with an empty white bar. It stacks with normal bossbars, uses the normal Minecraft GUI scale and is independent of the panel's position/scale settings.

The overlay shows server TPS, mean/P95/maximum tick duration (MSPT), player-list ping and client FPS. Server statistics cover the latest ten seconds (a shorter window during startup), with one shared update per second sent only to viewers. TPS counts completed ticks against elapsed monotonic time, capped at the server's configured tick rate. MSPT uses Minecraft's existing server tick timings. P95 is the nearest-rank 95th percentile. A missing update for more than three seconds replaces server values with dashes and shows the age of the last update.

On dedicated servers with Spark 1.10.124 or newer, the HUD prefers Spark's official API for TPS and mean/P95/maximum MSPT using its SECONDS_10 windows. The panel shows Source: Spark or Source: TDUtilities. Invalid or unavailable Spark data falls back as a complete set to the native measurements described above. Spark is optional and is not bundled or required on the client. Spark's tick-duration window in the tested version holds up to 200 ticks, so its nominal ten-second window can span longer under lag; its percentile calculation is used unchanged. Integrated servers always use native server measurements to avoid confusing Spark's client and server API singletons. Older HUD clients still receive the original statistics packet, without the source indicator.

In tdutilities-client.toml, [performanceHud] provides x, y, scale, bossbar, panel and visible. Coordinates are GUI pixels from the top left; defaults are 4, 34 and 0.85. After editing and saving the file, run /tdu hud reload in game to apply these six settings immediately. bossbar and panel independently select each view. visible = true enables the selected views automatically on supported servers. bossbar and visible default to false; panel defaults to true, including when upgrading a configuration without this setting. The toggle/on/off commands save overall visibility, and bossbar/panel commands save individual views. Unsupported servers leave the stored preference intact while keeping the HUD inactive. The reload command works with the HUD on or off and does not require a server update. Invalid settings are rejected together; reload does not write the file. The panel stays within the screen and follows F1 HUD visibility. MSPT colours compare tick duration with the current target tick budget (50 ms at 20 TPS).

What Are They Up To

Cluster AFK status

From 1.30.0, each cluster backend writes its local WATUT AFK flags to the shared MariaDB table tdu_afk_status, keyed by player UUID and backend. Configure the same TDLibrary database and enable the cluster with unique backend IDs. Use matching TDUtilities builds on clients and all backends.

From 1.32.0 the AFK status and the activity log borrow their database connections from TDLibrary's shared pool, which requires TDLibrary 0.74.0 or newer.

Backends refresh their flags and read current ones off the server thread every 20 ticks. Flags expire ten seconds after their last database write. The display selects the fresh flag for the backend on which TDLibrary currently sees the player. During a transfer the icon can disappear until the destination provides its flag. If the cluster or database becomes unavailable, stale remote icons clear. Joining clients receive the available remote snapshot. The activity log continues to record AFK history separately in tdu_afk.

With announceIdleStatesInChat enabled at both ends, AFK and return messages also appear on other backends for players online at the time. GUI images, mouse input, typing and inventory visuals keep their existing distribution. WATUT still uses its input reports, client privacy settings and the backend's idle threshold. An updated TD LeaderBoard can show remote AFK players without a local TAB entry.

Automated checks cover ownership changes, expiration, malformed announcements, client cleanup, and MariaDB writes and reads from two backend IDs. Check the visible icon and chat in-game across two backends, during a transfer and after a database interruption.

The WATUT 1.21.0-1.2.7 implementation is integrated under TDUtilities: typing and GUI indicators, typing-speed and mouse animations, idle poses and indicators above players and in the player list, dynamic GUI images with blur shaders, and item-transfer visuals. It requires TDUtilities on both client and server, without CoroUtil. The standalone WATUT JAR is no longer needed; if it is still installed, its implementation takes precedence and TDUtilities disables its own WATUT hooks.

WATUT settings are part of the existing TDUtilities configurations under [watut]: common settings in tdutilities-common.toml, server rules in config/tdutilities-server.toml, and client display and privacy settings in tdutilities-client.toml. Server rules use native NeoForge synchronization. Legacy tdutilities-watut-*.toml values supply defaults for missing settings; existing values in the shared TDUtilities configurations take precedence. Legacy files are read without modification. Standalone watut-*.toml files are not imported or changed. The default idle threshold is five minutes; idle chat announcements are off by default. The client privacy settings dontSendDetailedGUIInfo, dontSendItemInfo and the send* switches remain available. Dynamic images are bounded to 1024 pixels per axis; the optional entire-screen mode scales larger screens to this bound. Normal GUI images retain upstream's 256 by 256 resolution. Client packets cannot supply other players' identities, server configuration or item-transfer events. GUI image decompression rejects malformed, truncated and oversized data. Global status updates are separated from nearby-only GUI images and mouse data. The server limits each player's packet rate, status updates and decoded image bytes, and checks image chunk order. Images have a 4 MiB decoded-byte budget per second with a one-image burst at the maximum resolution; the configured GUI update interval also applies. Excess updates are dropped without disconnecting players. Item-transfer visuals use the current block menu and stop when it closes or the player changes dimension.

Held-item arm adjustments are ordered array-of-table entries in tdutilities-client.toml under [[watut.armAdjustments]]. Each rule has filters, an optional only_if_mod_installed mod ID and an adjustment table. Filters support exact item IDs, @namespace, and * at either end. The first matching active rule wins. Axes accept degrees or "DISABLED"; zero leaves that hand unaffected. For example:

[[watut.armAdjustments]]
filters = ["minecraft:bow"]

[watut.armAdjustments.adjustment]
matchingHandX = "DISABLED"
matchingHandY = "DISABLED"

Use /tdu watut reload after saving to apply the rules immediately. The old /tdu watut reloadJSON command remains an alias and reads the same TOML rules. Reload validates the complete list before replacing the active rules; on failure, the file and last valid rules remain intact. Repair the reported file and run the command again. No separate JSON configuration is created. WATUT and HUD commands share the /tdu root.

Curios and utility additions

The features of Colorful Hearts, Diagonal Wrench, Enchantment Descriptions, FlickerFix, Moog's Glow Up and Not Enough Recipe Book are integrated for Minecraft 1.21.1. The corresponding standalone mods (colorfulhearts, diagonalwrench, enchdesc, flickerfix, glow_up and nerb) take precedence. Their installed JARs remain separate from TDUtilities; manually remove a standalone mod only when testing its integrated replacement.

colorfulHearts in tdutilities-client.toml compresses health into ten heart icons and absorption into at most one additional row. Rendering uses the original Colorful Hearts 1.21.1 sprite-atlas and texture compositing code. The first row uses vanilla hearts by default; additional rows use the original palettes. colorfulHeartsSettings.health and colorfulHeartsSettings.absorption provide vanillaHearts, colors, poisonedColors, witheredColors and frozenColors, with colours in #RRGGBB format. The old integer heartColors list is retained for recovery and no longer affects rendering. Half hearts, hardcore borders, blinking, regeneration and low-health shaking follow the original renderer. Player-list hearts also follow the original, including vanilla's numeric fallback. Reload resources after editing heart settings. The relocated overlay-event types are internal to TDUtilities and do not replace the standalone mod's public API.

enchantmentDescriptions adds descriptions while holding Shift. All vanilla 1.21.1 enchantments have English, German and Ukrainian descriptions. Modded enchantments use their existing .desc or .description translations; unknown descriptions are omitted. Bookshelf and Prickle are not required for this feature. nightVisionFlickerFix keeps night vision steady until a linear fade over its last second, including effects with infinite duration.

tdutilities:diagonal_wrench switches blocks listed in Diagonal Blocks' conversion maps. Shared properties, including waterlogging, are retained and connections are recalculated. It respects cancelled item interactions, spawn protection and player build permissions. diagonalWrench controls its use. Diagonal Blocks is optional at runtime; the wrench's recipe requires it and is suppressed when standalone Diagonal Wrench is installed. The tool uses the unmodified original Diagonal Wrench 1.0.1 texture, bundled locally so the standalone mod is not needed.

disableRecipeBook in the common configuration disables tracking new unlocks, recipe book packets and the recipe book UI. Recipes remain available for crafting and lookup by recipe ID. Existing recipe book NBT is kept unchanged, including malformed and unknown fields. Consequently old player files do not shrink as they do with standalone NERB; loading no longer parses those lists. The server setting is fixed per player session to avoid discarding preserved data on a configuration reload. Restart both sides after changing it. When EMI is installed, the recipe book button stays and toggles the sidebar types listed in emiToggleSidebars in the client configuration. The default is craftables. An empty list toggles the whole EMI UI. Unknown names are ignored. Without EMI the button is removed. JEI is left unchanged.

glowUp in the common configuration enables the following glow ink utilities:

  • Find tdutilities:glow_trim_template in shipwreck treasure and underwater ruins, with a ten-percent chance per chest, or brush suspicious sand and gravel in warm and cold ocean ruins for a ten-percent chance per find. Duplicate it with diamonds and glow ink. Smith already trimmed armour with this template and glow ink for a steady glow, or an echo shard for a pulse. Existing trim, enchantments, durability and other components are retained.
  • Put a banner and glow ink into a loom's banner and dye slots. The final pattern glows; a blank banner instead gets a glowing base. Placing, dropping and picking the banner retain its glow. Supplementaries flags can be inked in the loom or by right-clicking; crafting a flag from a glowing banner preserves the glow. Flags glow as a whole and retain their data when placed or dropped.
  • Right-click a decorated pot's patterned side with glow ink. Only that side's pattern glows. Whole-pot drops and pick-block retain the data; breaking a pot into sherds follows vanilla rules.
  • Use glow ink on an unsheared sheep to make its wool glow. Its dye colour and shearing behaviour are retained and the inked state persists across saves.
  • Craft glow torches with torches and glow ink; floor and wall torches can be waterlogged and emit light level fifteen. Craft glow paste with a slime ball and glow ink; it attaches to block faces and emits level eight. Paste becomes visible near a player holding it.
  • Brew awkward potions with glow ink, then extend with redstone or strengthen with glowstone. A thrown revealing potion makes affected entities glow and places temporary lights only in air, within the world border and where the throwing player may build. Placement protection events are respected. Lights expire with the potion's duration, including after chunk reloads.

The Revealing status-effect entry (tdutilities:revealing) is hidden from EMI's ingredient list. Its potions and brewing recipes remain visible, and the effect still works. The filter resource is included in the source; its in-game display still requires acceptance after manual installation.

The glow switch suppresses recipes, brewing, ink interactions and special rendering. Existing light blocks retain their light emission and saved data. Glow content uses vanilla item and block art; pot emission masks are derived from the active resource pack. The upstream configuration screen is not included.

New items, blocks, potions and glow data use the tdutilities namespace. Existing glow_up items, blocks and ink data are not automatically migrated. Do not remove Moog's Glow Up from an existing world expecting those objects to be converted automatically. Test any manual migration on a copy before changing a live world. These integrations still require client/server gameplay and visual acceptance after installation; a build or unit test does not prove that acceptance.

No Villager Death Messages and Yeetus Experimentus features are independently implemented. noVillagerDeathMessages in tdutilities-common.toml suppresses the vanilla villager death log entry, preserving death processing, reputation and point-of-interest cleanup. skipExperimentalWarnings in tdutilities-client.toml skips experimental world creation, world loading and datapack confirmation dialogs. Both settings default to true. Saved lifecycle data and experimental flags remain unchanged; deprecated-world, old customised world, version, recovery and low-disk-space warnings remain active. Standalone novillagerdm and yeetusexperimentus take precedence; remove them manually to use the TDUtilities settings.

Chat Heads is integrated under tdutilities. Player messages show their sender's skin and hat layer before the name by default; heads also appear in player-name suggestions. UUID sender information takes priority, with profile/display-name heuristics and nickname aliases for chat formats that do not supply UUIDs. Heuristics can identify the wrong sender on custom servers; use UUID_ONLY to disable guessing or HEURISTIC_ONLY when required by the server's chat format. The [chatHeads] section in tdutilities-client.toml controls enabled, renderPosition (BEFORE_NAME or BEFORE_LINE), senderDetection, smartHeuristics, system messages, shadow, hat enlargement, text offsets, alias detection and persistent nickname=profileName aliases. Detected /realname aliases last until disconnect. Restart after changing settings so existing chat lines are rebuilt. ModernUI's text engine and Caxton force heads before the line. The server resource-pack marker assets/tdutilities/disable disables heads for that connection. No Cloth Config or Architectury is required.

Clean Swing Through Grass is provided by TDUtilities' own implementation. When attacking a non-colliding plant, the aimed living entity overlapping that plant's outline takes the hit instead of the plant. Normal entity reach, solid-block occlusion, Minecraft's attack checks and ordinary sword sweeps apply; the feature does not attack every entity overlapping a plant. Without a valid target the plant can still be broken normally. cleanSwingThroughGrass in tdutilities-client.toml defaults to true. Both additions run only on the client and use normal server packet handling. Standalone chat_heads and cleanswing take precedence when installed. Remove those mods manually to use the integrated versions.

Burnable Cobwebs is integrated into TDUtilities. Right-click a cobweb with a normal or soul torch (including modded TorchBlock items), or flint and steel, to remove it without drops. Redstone torches, lanterns and fire charges are excluded, matching the original item selection. Torches are not consumed; damageable lighters lose one durability point, except in creative mode. Smoke and the vanilla extinguishing sound are sent from the server. Cancelled or denied interactions, spawn protection and player build permissions are respected. The server setting burnableCobwebs in tdutilities-server.toml defaults to true. The original mod is no longer required; remove it manually when switching to this integration. Its unused custom burn sound and icon are retained under tdutilities.

/wits lists the registry IDs of structures whose bounding boxes contain your current position. Click an ID to copy it. Operators with permission level 2 can query other locations using /witsop <dimension> <x> <y> <z>, including relative coordinates. Like WITS, this detects saved structures, not world-generation features such as dungeon rooms or desert wells. The common setting structureCommands enables these commands and requires a restart; standalone WITS takes precedence when installed. The empty Elytra slot uses a grey wing pictogram.

The Curios Additions datapack is integrated as configurable slot definitions. Back, belt, body, bracelet, charm, feet, hands, head, necklace and ring default to five slots each. As in the original datapack, only belt is additionally assigned to players; the other slot types retain the entity assignments supplied by their original mods. Backpack is not resized. Normal and soul lanterns can optionally be equipped in belt slots; this does not add a light renderer.

Elytra uses its own elytra Curios slot with exactly one item. Elytras cannot be newly equipped in back, backpack or other Curios slots. Vanilla Elytra, Soul Elytra and HDPE Elytra support flight, normal durability loss and rendering. This integration does not promise textures or special abilities for other mods' Elytras. Curios' render toggle controls wing visibility without disabling flight. Soul Elytra uses Deeper and Darker's boost key and cooldown, including -1 to disable boosts. The server rechecks current equipment, flight, usability and cooldown on each request.

TDLibrary 0.19.0 or newer owns the optional Elytra Slot/Deeper and Darker cooldown adapter, Artifacts supporting-block chunk-access repair and Underground Worlds vanilla registry-bootstrap repair. TDUtilities no longer registers these hooks. Its own Curios Elytra support and Soul Elytra boost remain here.

Beautiful Enchanted Books supplies 694 enchantment-specific models from its 1.21 source under tdutilities:books/. The first stored enchantment selects the appearance, including Stellarity's void-locket aliases. Unrecognised enchantments retain the normal model. Resource packs can override the imported models and textures in that namespace.

Berry protection prevents berry-bush and cactus damage to villagers and living entities wearing both leggings and boots. The master switch, villager protection, armour protection and global damage suppression for each plant are independently configurable.

Craft tdutilities:tape_measure from three grey wool, two yellow wool and an iron ingot, or find it in Tools & Utilities. Right-click two blocks to create an outlined box with inclusive X/Y/Z block dimensions. Like Measurements, three separate dimension numbers follow the nearest box edges, with camera-facing text and outlines visible through blocks. Text size defaults to 0.02 and line width to 2; newly created client configs use the original yellow colours. Existing colour overrides remain active. The unfinished box follows the targeted block. Sneak-right-click a block to undo the last box, or sneak-right-click air to clear all boxes. Measurements disappear when the tape is no longer held, on a dimension change or on disconnect. They are local overlays and are not saved in worlds. Measuring does not activate the targeted block. The item remains registered and craftable when the measurement feature is disabled, but creates no boxes.

The model gap fix reduces atlas UV shrink and slightly moves generated item edges inward. It uses NeoForge's existing item seam correction and adds no replacement span generator. If the standalone modelfix mod is present, its geometry settings take precedence. Reload resources after changing TDUtilities' geometry settings.

Nether ore fixes restore missing vanilla configured ore features in minecraft:is_nether biomes, preserving existing features and their placement rates. Independent placement IDs avoid reusing the same placed feature in conflicting biome orders. Existing Nether Gold and Quartz variants, including basalt-delta rates, count as present. Optional extra Ancient Debris uses one additional vanilla large-debris placement per chunk in the triangular Y=8–24 range. These settings only affect new chunks and require a server restart. Unlike the standalone Netherite Tweaks, this implementation does not add supplemental gold/quartz generation to biomes that already have those ores.

Configuration Settings
config/tdutilities-common.toml [curios]: additions, the ten *Slots values (0–64), lanternsInBelt, elytraSlot; [netherOres]: ancientDebrisFix, extraAncientDebris, goldFix, quartzFix
config/tdutilities-server.toml [berryProtection]: enabled, disableVillagerDamage, disableDamageWhenArmored, disableBerryDamage, disableCactusDamage; measurements
config/tdutilities-client.toml beautifulEnchantedBooks; [modelGapFix]: enabled, uvShrinkMultiplier, itemEdgeInset; [measurements]: maximumBoxes, lineColor, textColor, textSize, lineWidth, lineWidthMax

Server configuration is synchronised to connected clients. Common slot definitions are determined by the server and synchronised through Curios; use matching common settings on clients for lantern equip prediction. Restart after changing common settings. Shrinking or disabling occupied slots uses Curios' normal invalid-stack recovery; empty affected slots before changing their size.

The existing standalone JARs and datapack are not modified by this repository. When switching manually, first move Elytras out of back/backpack into inventory, then use the new slot. Disable the external Curios Additions datapack so its slot definitions do not compete with config. The integrated features can replace Elytra Slot (and its TDElytraSlotCompat patch), Hey Berry, Measurements, Model Gap Fix and Netherite Tweaks. Existing measurements:tape_measure items are not converted; craft the TDUtilities item. The incompatible standalone mods listed in the handbook must be removed manually. Curios remains required for its slots; Caelus is not required by TDUtilities. Installation and in-game testing are manual; a successful build does not establish client rendering or world-generation acceptance.

Dimensions and portals

TDUtilities adds two dimensions that were previously defined through KubeJS and BBL Portals.

Dimension Portal frame Activator Portal
tdutilities:mining Blackstone Seal of the Deep Rift (tdutilities:mining_portal_activator) green molten portal
tdutilities:event Polished Blackstone Bricks Event Seal (tdutilities:event_portal_activator) nether-style portal

Build a nether-style frame (2–21 wide, 3–21 tall inside) and use the matching activator on the frame. Portals can only be lit in the Overworld; the activator is not consumed and is only obtainable through an operator command. Travelling creates or reuses a matching exit portal like a nether portal, with a 1:1 coordinate scale. Each portal leads back to the Overworld.

The Mining Dimension is a flat 384-block deep stone world with bedrock floor and ceiling. Its ores, rock deposits, building materials, chambers, geodes and small structures are generated from the settings in tools/mining/ (see tools/mining/README.md). The worldgen data references blocks and features from the FlammiCraft modpack (AE2, Create, Mekanism, All The Ores, Quark, Regions Unexplored, Lithostitched, YUNG's mods and others) and is not meant to load outside that pack.

Mining Dimension extras:

  • Veinrock: dormant origins spread over exposed Stone and Deepslate in ten stages. Finished Veinrock counts as Cobblestone and smelts into Stone.
  • Forsaken chamber: one sealed Alex's Caves Forsaken room per world, 1,800 to 2,000 blocks from the first portal arrival. Operators use /miningboss, /miningboss anchor and /miningboss reset. Distances and floor height are in the server config tdutilities-server.toml. The room template has a fixed size of 25 x 18 x 25 blocks; the former horizontalRadius and height settings are removed. Saved chambers with incompatible dimensions, out-of-range floor heights or malformed state are preserved and blocked for manual recovery. Supported saved floor heights are -48 through 280, inclusive.

From 1.30.0, the chamber save lives at <world>/dimensions/tdutilities/mining/data/tdutilities_forsaken_chamber.dat. The Mining backend owns generation, anchor changes and resets. A player with operator level 2 can run /miningboss on another backend to request status and coordinates from the owner. The teleport link is available when the command runs on the Mining backend.

If the Mining save is absent, TDUtilities copies the valid legacy file from <world>/data/tdutilities_forsaken_chamber.dat on the Mining backend and retains the original. If the latest valid legacy save lives on another backend, back it up and supply it at that legacy path on the Mining backend before the first start. An existing Mining save takes precedence. For future backend moves, back up and restore the whole Mining dimension, including its data directory. Automated checks cover legacy import and corrupt-file preservation. Check remote lookup and the restored chamber in-game after upgrading.

The event dimension tdutilities:event is a flat grass world for temporary server events. Snapshots are taken by copying <world>/dimensions/tdutilities/event/ while the server is stopped.

Quartz and Flammit use the tdutilities: namespace. Saved blocks, items and dimensions from the former KubeJS setup are not migrated.

Inventory utilities

TDUtilities includes inventory mending and inventory totems, replacing the functionality of Inventory Mending 1.3 and Inventory Totem 3.5 without requiring Collective.

  • Collected XP first repairs eligible equipped items, then randomly selected damaged enchanted items in the inventory. Vanilla XP consumption and modded repair ratios remain in effect.
  • A totem can activate directly from the inventory when neither hand holds one. It is consumed by the normal death-protection path, including effects, animation, statistics, advancements and NeoForge's cancellable totem-use event. Damage that bypasses vanilla totems, such as /kill, also bypasses inventory totems; this differs from Inventory Totem's death-event implementation.

Both features default to enabled. The [inventory] section in tdutilities-server.toml provides inventoryMending, inventoryTotem and mendToolbarOnly (default false). The old inventorymending.json5 is not read or changed. Only the player's direct inventory is searched, including the hotbar; contents of backpacks, shulker boxes and other containers are not searched.

When switching to TDUtilities, remove the two standalone mods manually to avoid overlapping handlers. Keep Collective if another mod still requires it.

Name tags

Name tags no longer need an anvil. A right-click with a name tag in hand opens a rename window that renames the held tag, including offhand. The typed codes such as &4 convert to the game's formatting codes before the name is stored; unrecognized pairings keep the ampersand. The bound is 128 characters after conversion and the window rejects an empty commit.

Naming a mob keeps vanilla behavior plus the following rules:

  • A tag carrying the identical name as the mob's current name is not consumed.
  • Renaming a named mob returns its old name as a fresh name tag; the inventory takes it when there is room, otherwise the tag drops at the player.
  • Naming keeps the mob's persistence protection and plays a short pickup-style sound.
  • Sneak shears on a named living entity cancel the vanilla shear interaction, remove the name and return it as a name tag. Unnamed mobs and unsneaked shears keep vanilla shearing (sheep, goats, snow golems and mooshrooms).
  • Named living entities other than players drop a name tag with their name on death. This includes mobs a player did not name and continues to respect counts the entity produced otherwise.

The server settings [nameTags] in tdutilities-server.toml provide editor (rename commits are accepted on the server), renameSound, keepSameName, shearsRemoveName, mobsDropNameTag and returnOldNameTag; all default to true. The client setting [nameTags] editorScreen opens the rename window on right-click. Both sides must enable their settings, because the server validates every commit independently of the client window. Server settings use NeoForge's synchronized server configuration, so the client predictions follow the values of the current server. Restart both sides after changing any setting.

Activity log

On a dedicated server TDUtilities can write player sessions, AFK periods and time per dimension to MariaDB. AFK uses the integrated What Are They Up To idle state. The standalone WATUT mod is incompatible. From 1.28.0 it has no settings of its own: it runs whenever [database] enabled = true is set in TDLibrary's private config/tdlibrary-database.toml, using that connection. Single-player worlds never log. An old config/tdutilities-database.toml is no longer read and can be deleted. The tables are created on server start:

Table One row per Columns
tdu_session login player_uuid, player_name, backend (cluster backend ID, empty on a single server), login_at, logout_at, end_reason (logout, shutdown, crash_recovered), duration_s
tdu_afk AFK period session_id, player_uuid, afk_start, afk_end, end_reason (returned, logout, shutdown, crash_recovered), duration_s
tdu_dimension stay in a dimension session_id, player_uuid, dimension (e.g. tdutilities:mining), entered_at, left_at, end_reason (changed, logout, shutdown, crash_recovered), duration_s

New intervals use UTC from 0.10.2 onward, so daylight-saving changes do not affect durations. Existing rows retain their original server-local timestamps and are not converted. Record the upgrade time when comparing historical and new timestamps; recovery closes old rows using their stored heartbeat. Idle state and dimension are checked once per second, so respawns and teleports count as dimension changes too. After a crash, open rows are closed at the last heartbeat (at most one minute old) on the next start of the same backend, so cluster backends sharing the database never close each other's sessions. Rows from before 1.28.0 have an empty backend and are closed by the next server that starts.

Failed writes remain queued in memory and are retried in order on the next activity event or heartbeat. The queue does not survive a process exit; if the database remains unavailable during shutdown, the next start recovers existing open intervals from their last successfully written heartbeat.

-- Online and active time per player
SELECT s.player_name,
       SUM(s.duration_s) / 3600 AS online_h,
       (SUM(s.duration_s) - COALESCE(SUM(a.afk_s), 0)) / 3600 AS active_h
FROM tdu_session s
LEFT JOIN (SELECT session_id, SUM(duration_s) AS afk_s FROM tdu_afk GROUP BY session_id) a ON a.session_id = s.id
GROUP BY s.player_uuid, s.player_name;

-- Hours per player and dimension
SELECT s.player_name, d.dimension, SUM(d.duration_s) / 3600 AS hours
FROM tdu_dimension d JOIN tdu_session s ON s.id = d.session_id
GROUP BY s.player_uuid, s.player_name, d.dimension;