STags is a customizable prefix, suffix, and player tag system for Minecraft Fabric servers.
It allows server administrators to create simple text tags or styled badges, assign tags manually, configure automatic unlock requirements, define priorities, and control where prefixes and suffixes are displayed.
Players can browse the tags they own and choose which prefix and suffix they want to use.
| Requirement | Version |
|---|---|
| Minecraft | 1.20.1 & 1.21.1 |
| Mod Loader | Fabric |
| Fabric Loader | 0.18.4 or newer |
| Fabric API | Required |
| Java | Java 17/21 |
| Installation | Client and Server |
STags is designed to be installed on both the Minecraft client and the server.
The same mod JAR is used on both sides.
STags supports two independent tag types:
Players can have one active prefix and one active suffix at the same time.
Example:
[ADMIN] Steve [Builder]
Prefixes appear before the player's name while suffixes appear after it.
Players can open their personal tag menu using:
/tags
The interface separates:
Players only see tags they actually own or have unlocked.
Locked tags are not displayed in the player's tag list.
Players can:
Every tag can have a numeric priority.
When automatic priority mode is enabled, STags automatically selects the highest-priority tag available to the player.
Example:
Member = 10
VIP = 30
Moderator = 70
Admin = 100
If the player owns all four tags, Admin is automatically selected.
Players can also manually select another available tag when player selection is enabled for that tag.
Simple tags use normal Minecraft text formatting.
Administrators can create tags such as:
&c[ADMIN]
or:
&c[&lADMIN&c]
Minecraft formatting codes are supported, including colors and text styles.
Examples:
&6[VIP]
&b[Builder]
&c[&lADMIN&c]
Hexadecimal colors are also supported where available.
STags also provides a Stylish tag mode.
Stylish tags use:
Instead of displaying only formatted text, STags renders the tag as a badge.
The goal is to keep Stylish tags clean and readable while maintaining the normal Minecraft visual style.
The same Stylish appearance can be used in:
Server administrators can control where prefixes and suffixes are displayed.
The Display menu is available inside:
/admintags
Prefix and suffix visibility can be configured independently for:
Controls whether the active tag appears in chat.
Controls whether the active tag appears in Minecraft's TAB player list.
Controls whether the active tag appears around the player's name above their character.
This makes it possible to configure setups such as:
Prefix:
Chat: ON
TAB: ON
Nameplate: ON
Suffix:
Chat: ON
TAB: OFF
Nameplate: OFF
Tags can be configured with automatic unlock requirements.
STags tracks supported actions server-side and unlocks the corresponding tag after the required amount is reached.
Available requirement types include:
Unlock the tag after breaking a specific block a configured number of times.
Example:
Block ID: minecraft:diamond_ore
Amount: 500
Unlock the tag after placing a specific block.
Example:
Block ID: minecraft:stone
Amount: 1000
Unlock the tag after interacting with a specific block.
This can be used with:
Example:
Block ID: minecraft:chest
Amount: 250
Unlock the tag after dying a configured number of times.
Specific death requirements are also available.
Supported death categories include:
Example:
Requirement: Die by Fire
Amount: 10
Unlock the tag after killing a specific entity.
Example:
Entity ID: minecraft:zombie
Amount: 500
Unlock the tag after killing other players.
Example:
Amount: 25
Unlock the tag after eating a specific item.
Example:
Item ID: minecraft:golden_apple
Amount: 20
Unlock the tag after drinking a specific item.
Example:
Item ID: minecraft:potion
Amount: 50
STags uses Minecraft registry IDs for requirement targets.
This means requirements can work with blocks, items, and entities added by other mods.
Examples:
minecraft:diamond_ore
minecraft:chest
minecraft:golden_apple
minecraft:zombie
Modded examples:
modid:machine
modid:special_block
modid:custom_food
modid:custom_entity
STags does not require a hardcoded list of vanilla content.
Requirements that use blocks or entities can be configured without manually typing registry IDs.
The administrator can press the Select button inside the requirement editor.
STags temporarily provides a selection tool.
For block requirements:
Select
↓
Click the block
↓
STags captures the Block ID
↓
Returns to the Requirement editor
For entity requirements:
Select
↓
Click the entity
↓
STags captures the Entity ID
↓
Returns to the Requirement editor
The temporary selector is automatically removed when the selection finishes.
It is not counted as requirement progress while being used for configuration.
Tags do not automatically belong to every player simply because they have no requirement.
A tag without an automatic requirement must still be granted by an administrator.
This allows tags such as:
to remain controlled by the server.
Administrators can open the STags administration interface using:
/admintags
The player /tags menu and administrative menu are completely separate.
The administrative interface includes:
Administrators can configure:
Administrators can directly grant or revoke tags from players.
Manual grants override automatic requirement restrictions.
This makes it possible to give a tag even when the player has not completed its normal requirement.
/admintags
Opens the STags administration interface.
/admintags give <player> <tag-id>
Example:
/admintags give Steve admin
Immediately grants the specified tag to the player.
/admintags remove <player> <tag-id>
Example:
/admintags remove Steve admin
Removes the manually granted tag.
| Command | Permission | Function |
|---|---|---|
/tags |
Player | Opens the personal tag menu |
/admintags |
Admin | Opens the administration menu |
/admintags give <player> <tag-id> |
Admin | Grants a tag to a player |
/admintags remove <player> <tag-id> |
Admin | Removes a tag from a player |
STags includes optional integration support for SChat.
STags is responsible for:
SChat only requests the active prefix and suffix from STags.
This allows SChat formats to use:
{prefix}
{player}
{suffix}
Example:
{prefix}{player}{suffix}: {message}
which can produce:
[ADMIN] Steve [Builder]: Hello!
STags remains responsible for deciding which tags the player currently has active.
SChat is not required for using STags in the player list or player nameplates.
Important STags operations are controlled by the server.
The client cannot directly grant itself tags or complete requirements.
The server validates operations such as:
This prevents normal client-side manipulation from directly changing server tag data.
STags saves important information across server restarts.
Stored information includes:
STags automatically uses the language selected by each player in Minecraft.
There is no separate language selector inside the mod.
Currently included languages:
| Language | Minecraft Code |
|---|---|
| English | en_us |
| Portuguese, Brazil | pt_br |
| Spanish | es_es |
| Japanese | ja_jp |
| Simplified Chinese | zh_cn |
| Hindi | hi_in |
| Arabic | ar_sa |
Different players connected to the same server can use different languages at the same time.
STags uses custom Minecraft interfaces designed to remain simple and responsive.
The interface includes:
Requirement menus automatically adapt to the selected requirement type.
For example, death and player-kill requirements only display the Amount field because no registry ID is necessary.
mods folder.mods folder./admintags to configure tags.STags is designed to use the same mod installation on both the client and server.
Mod: STags
Author: Silas T.
Minecraft: 1.20.1 / 1.21.1
Loader: Fabric
Java: 17/21
License: All Rights Reserved
