Tracks
Tracks are ordered sequences of groups that define promotion and demotion paths. They allow you to easily move players up or down a rank ladder with simple commands.
What are Tracks?
A track is a named list of groups in order from lowest to highest. When you promote a player on a track, they move to the next group. When you demote, they move to the previous group.
text
Staff Track:
helper → mod → admin → owner
(lowest) (highest)
Donor Track:
vip → vip+ → mvp → mvp+
(lowest) (highest)Why Use Tracks?
- Simple promotion - One command to promote, no need to remember group names
- Prevent mistakes - Can't accidentally skip ranks
- Clear hierarchy - Documents your rank structure
- Automation - Can be integrated with other plugins
Creating a Track
| Command | Description |
|---|---|
/hp track create <name> | Create a new track |
/hp track append <track> <group> | Add group to end of track |
/hp track insert <track> <group> <position> | Insert at position |
Example: Staff Track
text
# Create the track
/hp track create staff
# Add groups in order (lowest to highest)
/hp track append staff helper
/hp track append staff mod
/hp track append staff admin
/hp track append staff owner
# Track is now: helper → mod → admin → ownerExample: Donor Track
text
# Create the track
/hp track create donor
# Add donor ranks
/hp track append donor vip
/hp track append donor vip+
/hp track append donor mvp
/hp track append donor mvp+
# Track is now: vip → vip+ → mvp → mvp+Create the groups before adding them to tracks. Use
/hp group createif the groups don't exist yet.Using Tracks
Promoting Players
| Command | Description |
|---|---|
/hp user promote <player> <track> | Promote player on track |
text
# Steve is currently "helper" on the staff track
/hp user promote Steve staff
# Steve is now "mod" (moved up one rank)
# Promote again
/hp user promote Steve staff
# Steve is now "admin"Demoting Players
| Command | Description |
|---|---|
/hp user demote <player> <track> | Demote player on track |
text
# Steve is currently "admin"
/hp user demote Steve staff
# Steve is now "mod"
# Demote again
/hp user demote Steve staff
# Steve is now "helper"Edge Cases
text
# What happens at the ends of a track?
# Promoting at the top:
# Steve is "owner" (top of staff track)
/hp user promote Steve staff
# Error: Player is already at the top of the track
# Demoting at the bottom:
# Steve is "helper" (bottom of staff track)
/hp user demote Steve staff
# Error: Player is already at the bottom of the trackManaging Tracks
Viewing Tracks
| Command | Description |
|---|---|
/hp track list | List all tracks |
/hp track info <track> | View track details |
text
/hp track info staff
# Output:
# Track: staff
# Groups (in order):
# 1. helper
# 2. mod
# 3. admin
# 4. ownerModifying Tracks
| Command | Description |
|---|---|
/hp track insert <track> <group> <position> | Insert at position |
/hp track remove <track> <group> | Remove group from track |
/hp track clear <track> | Remove all groups from track |
text
# Insert "senior-mod" between mod and admin
/hp track insert staff senior-mod 3
# Track is now: helper → mod → senior-mod → admin → owner
# Remove a group from the track
/hp track remove staff senior-mod
# Track is back to: helper → mod → admin → ownerDeleting Tracks
| Command | Description |
|---|---|
/hp track delete <track> | Delete a track entirely |
Deleting a track doesn't delete the groups - it only removes the track definition. Players remain in their current groups.
Track Order
The order of groups in a track matters. Position 1 is the "lowest" rank, and higher positions are "higher" ranks.
text
Track: staff
Position 1: helper (lowest - entry level)
Position 2: mod (promoted from helper)
Position 3: admin (promoted from mod)
Position 4: owner (highest - promoted from admin)Track order is independent of group weight. A group can be "low" in one track but "high" in another.
Multiple Tracks
You can have multiple tracks for different promotion paths. A player can be promoted on different tracks independently.
text
# Staff track for staff ranks
/hp track create staff
/hp track append staff helper
/hp track append staff mod
/hp track append staff admin
# Donor track for donor ranks
/hp track create donor
/hp track append donor vip
/hp track append donor vip+
/hp track append donor mvp
# A player can be in both:
# - "mod" from staff track
# - "mvp" from donor track
# Promote on staff track (affects staff rank only)
/hp user promote Steve staff
# Promote on donor track (affects donor rank only)
/hp user promote Steve donorTrack and Group Relationship
Important things to understand:
- A group can be in multiple tracks (or none)
- Tracks don't affect group inheritance - set that separately
- Promoting adds the new group and removes the old one from that track
- Players can have groups from multiple tracks simultaneously
text
# Example: "default" could be in both tracks
/hp track append staff default # Entry to staff track
/hp track append donor default # Entry to donor track
# When promoting from default:
/hp user promote Steve staff # Removes default, adds helper
/hp user promote Steve donor # Removes default, adds vip
# But if Steve is already "helper":
/hp user promote Steve donor # Adds vip (default not removed, Steve didn't have it)Common Track Patterns
Simple Staff Hierarchy
text
/hp track create staff
/hp track append staff helper
/hp track append staff mod
/hp track append staff admin
/hp track append staff ownerDonor Tiers
text
/hp track create donor
/hp track append donor vip
/hp track append donor vip-plus
/hp track append donor elite
/hp track append donor legendPrison Ranks
text
/hp track create prison
/hp track append prison a
/hp track append prison b
/hp track append prison c
/hp track append prison d
/hp track append prison freeFaction Ranks
text
/hp track create faction
/hp track append faction recruit
/hp track append faction member
/hp track append faction officer
/hp track append faction leaderBest Practices
Do
- Use descriptive track names
- Keep tracks focused (staff track, donor track, not mixed)
- Document what each track is for
- Test promotions and demotions after setting up
Don't
- Put unrelated groups in the same track
- Forget to create groups before adding to tracks
- Confuse track order with group weight
See Also
- Groups - Creating groups for tracks
- Weight - How weight differs from track order
- Track Commands - Complete command reference
- User Commands - Promote/demote commands