SmartUtility

SmartUtility Feedback on Google Forms

I’m actively looking for feedback to help decide the direction of future updates.

→ Take the Smart Utility Feedback Survey

It only takes a few minutes, and every response helps shape future versions of the mod.

Smart Utility

Twenty-three quality-of-life features in one mod, each with its own switch. Everything that touches
gameplay runs on the server, so your players connect with a plain vanilla client and it just
works.

Most of these you would otherwise install as twenty-three separate mods, each with its own config
file and its own update schedule. This is one jar, one config, and anything you do not want
stays off.

Features

The feature menu

Players do not have to read this page to find out what a server runs. With the mod installed
on the client, K opens an in-game menu listing every feature: what it does, how it is
used, and the settings that are actually in force on the server you are on, read live rather
than printed from the defaults. Features the server has switched off are greyed out and say
so.

Without the mod on the client, /smartutility feature list and
/smartutility feature info <feature> print the same thing into chat.

Still to come

Twenty-three features is where the mod stands, not necessarily where it stops. Nothing is currently
planned; further ideas are tracked in the project’s own backlog and only announced once picked up.
Each one would arrive with its own toggle and its own config section, so anything you do not want
stays off, and existing config files pick up the new keys on the next start.

Everything is optional

Every feature has its own toggle. Change it in the config, or in-game:

/smartutility feature list
/smartutility feature enable <feature>
/smartutility feature disable <feature>

Changes apply immediately, no restart — with one exception: Custom Enchants is a datapack, so its
switch takes effect on the next /reload or restart, and the command says so when you use it.
/su works as a shorthand, and the feature menu
described above shows the same states with the reasoning next to them.

Eight features add a command of their own, because a player invokes or reads them rather than
triggering them by playing:

/crafting                          open a crafting grid where you stand
/enderchest                        open your own ender chest
/serverstats                       the server-wide totals, largest first
/sethome [name]                    save a home where you stand
/home [name]                       teleport back to it, across dimensions too
/delhome <name>                    remove one
/homes                             list your own
/friend add <player>               send a request, or confirm one already waiting
/friend remove <name>              remove a friend, or cancel/decline a request
/friend list                       friends, plus requests sent and received
/backpack create <name>            start a group; you become its owner
/backpack invite <group> <player>  owner only, invites a player
/backpack accept|decline <group>   join a group you were invited to, or turn it down
/backpack open <group>             open its shared storage, for any member
/backpack leave <group>            leave; the owner leaving disbands it instead
/backpack kick <group> <player>    owner only, removes a member, even one who is offline
/backpack disband <group>          owner only, ends the group; its contents go to the owner
/backpack list                     your groups and any pending invites
/nether                             Nether coordinates matching your Overworld position
/overworld                          Overworld coordinates matching your Nether position
/aura <style>                      pick a cosmetic particle aura for yourself
/aura off                          turn it off

All are open to every player, and all work from a vanilla client.

Two features are not the server’s alone to show. The Armor Durability HUD is drawn on the client
and never reaches the server, so its toggle sits in the client’s own config and
/smartutility feature enable armorDurabilityHud is refused rather than writing a value the
server does not own — each player decides whether they want it. The friend HUD panel is similar
but stays a server switch: /friend itself works from a vanilla client, but the live position
panel only draws with the mod installed there.

Configuration

Three files, each written where it belongs:

• config/smartutility-common.toml: logging, plus the one switch that must be read before a
  world is loaded (Custom Enchants)
• config/smartutility-server.toml: everything else about gameplay
• config/smartutility-client.toml: the durability HUD, on the client only — a dedicated server
  never creates this one

You can also edit all of it in-game under Mods → Smart Utility → Config. No extra config
library needed. A single world can override the server config with its own copy in
<world>/serverconfig/.

Built for servers

• Every gameplay decision is made on the server. Clients cannot set their own multipliers or limits.
  The one client-side feature is a readout of what the player is already holding, and changes
  nothing in the world.
• Modded crops, logs, leaves and ores are picked up through tags and vanilla’s own block types,
  not through hardcoded lists, so there are no config entries for content from other mods.
• Mob head drops go through NeoForge’s Global Loot Modifiers, so they stack with other loot
  mods instead of overwriting them.
• Multi-block features respect cancelled break events, spawn protection and the world border,
  and they check every block, not just the one that was clicked.
• No mixins anywhere. Only official NeoForge events.
• The two features with a key binding send an optional packet, so a vanilla client is never
  refused a connection over it and simply uses the command instead.
• English and German translations included.

Installation

There is one file per game version, and they are not interchangeable:

1. Install NeoForge for your game version.
2. Drop the matching jar into your server’s mods folder.
3. Start the server once, then edit config/smartutility-server.toml (smartutility-synced.toml
   on 26.3).

All three files carry the same features, and each names a version range bounded at both ends, so the
wrong one is refused at load instead of failing later.

Installing it on the client is optional. It adds the config screen, the feature menu on K, a
key for the crafting grid and the ender chest instead of their commands, and two panels that
exist only there: the durability HUD and the friend HUD.

FAQ

Do my players need to install anything?
For twenty-one of the twenty-three features, no: they work for players on a plain vanilla client. The
exceptions are the Armor Durability HUD and the friend HUD panel, both drawn on the player’s own
screen and both needing the mod there — Friends’ own commands, /friend add|remove|list, work
without it the same as any other. Otherwise the client jar only adds the feature menu, the config
screen and three key bindings, all of which have a command behind them anyway.

How do players see what this server has enabled?
With the mod on the client, K opens the feature menu, which lists every feature with the
settings in force here. Without it, /smartutility feature list prints the same thing.

Does it set the keepInventory gamerule?
No, and it does not read it either. A gamerule is written into your world and outlives the
mod; this switch is per instance and leaves nothing behind.

Does it conflict with other vein miner, tree feller or auto replant mods?
Yes, but run only one of each kind. They react to the same event and would both fire. Smart
Utility’s own features are safe together.

Does it work with grave mods?
Not usefully. Both take the inventory at death, whichever runs first wins. Pick one, or leave
Keep Inventory off.