Adventurer's Titles

Adventurer's Titles

Adventurer's Titles is a progression-based achievement and title system for Minecraft 1.20.1 Fabric, designed to give players meaningful recognition for their accomplishments throughout their journey.

Unlock titles by completing achievements, defeating enemies and bosses, exploring dimensions, reaching progression milestones, joining teams, or meeting custom conditions configured by the server or modpack.

Once unlocked, titles can be equipped and displayed in-game, allowing players to show their achievements while also receiving configurable attribute bonuses.

Features

• Achievement-Based Titles — Unlock titles by completing configurable achievements and progression requirements.
• Equipable Titles — Players can choose which unlocked title they want to display.
• Persistent Progression — Once an achievement is unlocked, its progress remains completed even if the original condition later disappears.
• Custom Titles — Titles can be fully configured through JSON files, including names, descriptions, colors, icons, requirements, and rewards.
• Attribute Bonuses — Titles can provide configurable bonuses such as Attack Damage, Armor, Armor Toughness, Max Health, Movement Speed, Attack Speed, and Luck.
• Title Display — Equipped titles can be displayed above the player's head in the world.
• Chat Titles — Equipped titles can also appear alongside the player's name in chat without replacing or recoloring the player's name.
• Achievements Interface — Includes an in-game interface for viewing achievements, progress, unlocked titles, and available rewards.
• Title Interface — A dedicated title screen allows players to browse and equip their unlocked titles.
• Story Progression Support — Titles can be unlocked using player command tags, making the mod suitable for custom progression systems and modpacks.
• Retroactive Unlocking — Existing player tags are detected when entering the world, so previously completed progression can unlock titles automatically.
• Team Title — Includes a special team-based title that becomes permanently unlocked once a player has been part of a team.
• Dynamic Team Display — When the team title is equipped, the player's current team name can be displayed dynamically.
• Optional Integrations — FTB Quests and KubeJS can be used by modpacks to manage progression and player tags, but they are not required by the mod.
• Standalone Design — Adventurer's Titles works independently and does not require a questing system or scripting mod.

Achievement Requirements

Titles can use different types of requirements, including:

• Entity kills
• Advancements
• Statistics
• Mined blocks
• Crafted items
• Item usage
• Dimension visits
• Team membership
• Player command tags
• Multiple tag conditions
• Projectile hits from a minimum distance
• Target block hits from a minimum distance
• Hostile enemy kills
• Damage dealt to hostile enemies
• Unique generated loot containers

This allows the system to work with both simple survival achievements and more complex modpack progression systems.

Story Progression

Adventurer's Titles can read progression directly from player command tags.

This allows a modpack to connect its own story, milestones, quests, bosses, or dimension progression to titles without requiring Adventurer's Titles to directly depend on the system that manages the progression.

For example:

story_nether_complete → Lord of Flames

story_aether_complete → Celestial Conqueror

story_endgame_complete → Legend of the Journey

A title remains permanently unlocked after the required tag is detected, even if the tag is later removed.

zHuntersRPG Story Titles

The titles configured in tag_titles.json are used by my modpack zHuntersRPG to connect the modpack's story progression to Adventurer's Titles.

These story titles depend on command tags that are created by the progression systems used by the modpack.

Because of this, players using Adventurer's Titles outside of zHuntersRPG may see these story titles, but their corresponding tags will normally never be created, meaning the associated missions will not be completed.

Players and modpack authors who are not using zHuntersRPG are therefore recommended to modify or remove tag_titles.json and replace the existing story tags with their own progression tags.

This allows the story-title system to be adapted for other modpacks, servers, quests, bosses, dimensions, or custom progression systems.

Rewards

Titles can provide configurable rewards when unlocked.

Attribute Rewards

Titles can grant bonuses such as:

• Attack Damage
• Armor
• Armor Toughness
• Max Health
• Movement Speed
• Attack Speed
• Luck

Item Rewards

Titles can also provide item rewards configured directly in the title definition.

Item rewards are granted only once per title. If the player's inventory is full, the items are dropped at the player's position instead of being lost.

Configuration

Adventurer's Titles is designed to be highly configurable.

Title definitions can be created and modified using JSON configuration files.

The mod creates its configuration files inside:

config/adventurers_titles/

The main configuration files are:

titles.json — Normal achievement and progression titles.

tag_titles.json — Story-based titles unlocked through player command tags.

Resetting the Configuration

When a new version of the mod is installed, existing configuration files are normally preserved so that custom changes are not overwritten.

If you want to generate a completely new configuration using the current default files, close Minecraft and delete the entire:

config/adventurers_titles/

folder.

When Minecraft is started again, Adventurer's Titles will recreate the folder and generate fresh configuration files.

Important: Deleting the folder also removes your custom changes to the configuration. Make a backup before doing this if you want to preserve your edits.

Creating Custom Titles

New titles can be created directly inside:

config/adventurers_titles/titles.json

Each title contains its own ID, name, description, category, color, icon, requirement, and reward.

For example:

"id": "example_title"

The id is the internal identifier of the title and must be unique.

"title": "Título de Exemplo"

Defines the title name displayed to the player.

"description": "Fabrique sua primeira espada de ferro."

Defines the description displayed in the achievement interface.

"category": "Combate"

Defines the category of the title.

"color": "#D9A441"

Defines the title color using a hexadecimal RGB value.

"icon": "minecraft:iron_sword"

Defines the Minecraft item used as the title icon.

The requirement section defines what the player must do to unlock the title, while the reward section defines the bonuses or items received after unlocking it.

Requirement Configuration

Titles can use different requirement types depending on the type of progression you want to create.

Entity Kill

"type": "kill_entity"

Tracks kills of a specific entity.

Advancement

"type": "advancement"

Unlocks the title when a specified Minecraft advancement is completed.

Statistic

"type": "statistic"

Uses a Minecraft statistic as the progression source.

Mined Block

"type": "mined_block"

Tracks the number of blocks mined, with optional dimension restrictions.

Crafted Item

"type": "crafted_item"

Tracks the crafting of a specified item.

Item Usage

"type": "used_item"

Tracks the use of a specified item.

Dimension Visit

"type": "dimension_visit"

Unlocks the title after visiting a specified dimension.

Team Membership

"type": "team_membership"

Unlocks once the player has been part of a Minecraft scoreboard team.

The achievement remains permanently unlocked even if the player later leaves the team.

Player Tag

"type": "player_tag"

Unlocks the title when the player has the specified command tag.

Multiple Player Tags

Multiple tags can be configured using match: "any" or match: "all".

"match": "any" requires at least one of the configured tags.

"match": "all" requires all configured tags.

Projectile Hits From Distance

"type": "projectile_hit_from_distance"

Counts successful projectile hits against entities when the target is at least the configured minimum distance from the player.

Target Block Hits From Distance

"type": "target_hit_from_distance"

Counts projectile hits on target blocks when the configured minimum distance is reached.

Hostile Enemy Kills

"type": "hostile_kill"

Counts kills against enemies that are detected as aggressive toward the player.

This allows the requirement to work with hostile entities without requiring a manually maintained list of every enemy.

Hostile Enemy Damage

"type": "hostile_damage"

Tracks damage dealt to aggressive enemies.

Unique Loot Containers

"type": "unique_loot_container"

Counts unique generated loot containers opened by the player.

Opening the same generated container repeatedly does not increase the counter.

Vanilla generated loot chests and barrels are supported, while Lootr remains optional.

Reward Configuration

Rewards are configured inside the reward section of each title.

Attribute Rewards

Attributes can be configured using their Minecraft attribute ID, amount, and operation.

Supported operations include:

• addition
• multiply_base
• multiply_total

Attributes from supported optional mods can also be configured when those mods are installed.

Optional attribute integrations do not make those mods mandatory dependencies. If an optional attribute provider is not installed, only that specific attribute reward is ignored while the title itself remains available.

Item Rewards

Item rewards can be configured directly inside the title definition.

Item rewards are delivered only once per title.

If the player's inventory is full, the items are dropped at the player's position instead of being lost.

Editing Configuration

After modifying:

config/adventurers_titles/titles.json

or:

config/adventurers_titles/tag_titles.json

use:

/adtitles reload

to reload the configuration without restarting the game.

The configuration folder also contains a README.txt file with additional information about configuring titles and requirements.

Story Titles and tag_titles.json

Story-based titles are stored separately from normal achievements in:

config/adventurers_titles/tag_titles.json

This separation allows normal achievement titles in titles.json to coexist with titles controlled by external progression systems.

For a custom modpack, tag_titles.json can be edited to use your own player tags.

The tags can be created by Minecraft commands, datapacks, FTB Quests, KubeJS, or another external progression system.

For users of zHuntersRPG, the default tag_titles.json is already configured for the modpack's story progression.

For other modpacks and servers, the file should be modified or removed and replaced with custom story tags so that the corresponding progression titles can be unlocked.

Persistent Progress

Achievement completion is stored persistently with the player's data.

Once a title is unlocked:

• The achievement remains completed even if its original requirement is no longer true.
• Removing a required tag does not remove the achievement.
• Leaving a team does not remove the team achievement.
• Resetting an achievement is only possible through the administrative reset commands.

Item reward history is also stored separately, preventing previously claimed rewards from being duplicated after an administrative reset.

Team Compatibility

Adventurer's Titles uses Minecraft's existing vanilla scoreboard team system for team-based requirements.

It does not create its own scoreboard teams.

This means existing teams created by vanilla Minecraft, commands, datapacks, or other mods can continue to be used normally.

For servers using an enhanced team management system, Adventurer's Titles can work alongside Team System while continuing to use Minecraft's standard team membership.

Optional Integrations

FTB Quests

FTB Quests can be used by modpacks to manage quests and progression that eventually grant player tags used by Adventurer's Titles.

FTB Quests is not required for the core title system.

KubeJS

KubeJS can be used to create custom progression logic, assign player tags, or connect other systems to Adventurer's Titles.

KubeJS is not required.

Team System

Adventurer's Titles is compatible with Minecraft's vanilla scoreboard teams, allowing it to work alongside Team System without replacing the underlying team system.

Lootr

Lootr is an optional compatibility integration.

Adventurer's Titles does not require Lootr, but when Lootr is installed, its generated loot containers can be detected by the unique_loot_container requirement.

Without Lootr, vanilla generated loot containers continue to work normally.

Vanilla Compatibility

Adventurer's Titles is built around Minecraft's existing player, advancement, statistic, dimension, command tag, and scoreboard systems.

Existing progression systems do not need to be recreated when installing the mod.

Player progress can also be recognized retroactively when the corresponding condition is already present.

Installation

Install Adventurer's Titles on both the client and server.

Requirements

• Minecraft 1.20.1
• Fabric
• Fabric API

The mod does not require FTB Quests, KubeJS, or Lootr.

Compatibility

Minecraft 1.20.1

Fabric

Java 17+

Client & Server

Credits

Created by zClashTM.

License

Adventurer's Titles is licensed under the MIT License.