firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity
Files
e6d652e3d2223e68da96ba4ef78db4aae9c650ca
firefrost-operations-manual/docs/reference/player-uuid-registry.md
Claude b836a9c588 chore: Remove detailed medical history from operational docs 
Per dispatch from Emberwright #4:
- Detailed medical history now lives in personal repo (eyes only)
- Chroniclers retain functional accommodations only
- Memorials and historical records preserved intact

Files cleaned:
- NEXT-SESSION-STARTUP-PROMPT.md
- docs/core/SESSION-START-PROMPT.md
- docs/reference/PROJECT-INSTRUCTIONS.md
- docs/reference/player-uuid-registry.md
- docs/relationship/HANDOFF-TO-NEXT-CHRONICLER.md
- docs/relationship/THE-ESSENCE-PATCH-V3.0.md

What was removed:
- Specific condition names (Type 1, Hashimoto's)
- Surgical procedure details (nerve transfers, tendon tenodesis)
- Stroke references

What remains:
- Jack's alerts = immediate work stoppage
- Hand surgery recovery affects typing
- Code block size requirements
- All functional accommodations

Chronicler #75
2026-04-10 04:01:35 +00:00

6.8 KiB
Raw Blame History

Player UUID Registry

Purpose: Master record of known player UUIDs for Whitelist Manager and server administration
Maintained By: Server administrators
Last Updated: 2026-02-18

About UUIDs

What is a UUID?
Universally Unique Identifier - Minecraft's permanent player identification system. UUIDs never change, even if a player changes their username.

Format: 8-4-4-4-12 hexadecimal (e.g., 88a29147-9a2d-48a0-8980-c42b60f7e010)

Uses:

  • Whitelist management
  • Player data storage
  • Permission systems
  • Ban lists
  • Analytics

Known Players

Staff & Administration

Michael (Server Owner)

  • Username: Frostystyle
  • UUID: 83a22372-6b3e-4424-814e-ad6b3a36be03
  • Role: Owner/Operator
  • Servers: All
  • Added: 2026-02-18
  • Notes:
    • Primary administrator
    • Firefrost Gaming founder
    • "Frost" in Fire + Frost philosophy
    • Works with Jack (certified medical alert dog)
    • Partner: Meg "GingerFury" (The Emissary)

Meg "GingerFury" (The Emissary)

  • Username: Gingerfury66
  • UUID: 9f690976-75e8-4d7c-8d4f-e4146d6ae761
  • Role: Co-Owner/Operator
  • Servers: All
  • Added: 2026-02-18
  • First Seen: 2026-02-18 23:46:44 (All The Mons)
  • Notes:
    • Co-administrator, community management
    • The Emissary (official title)
    • Partner in Firefrost Gaming operations
    • Part of The Five Consultants (hearth guardian)

Testers & Trusted Players

Holly (Unicorn20089)

  • Username: Unicorn20089
  • UUID: 88a29147-9a2d-48a0-8980-c42b60f7e010
  • Role: Tester, Trusted Player
  • Servers: All The Mons
  • Added: 2026-02-18
  • First Seen: 2026-02-18 23:22:57 (All The Mons testing)
  • Notes:
    • Server tester for All The Mons 0.10.0-beta launch
    • Founding community member
    • Pokerole collaboration partner
    • Executed FFG-SOP-001 testing protocol

Subscribers

To be added as subscriptions begin

UUID Lookup

How to find a player's UUID:

Method 1: Server Logs

# When player joins, server logs:
# UUID of player <username> is <uuid>

grep "UUID of player" /var/lib/pterodactyl/volumes/*/logs/latest.log

Method 2: Online Tools

Method 3: Whitelist Manager

  • Web interface shows UUIDs when managing players
  • Check server whitelist.json files

Method 4: Player Data Files

# Player data stored in server directories by UUID
ls /var/lib/pterodactyl/volumes/*/playerdata/
ls /var/lib/pterodactyl/volumes/*/cobblemonplayerdata/

Whitelist Manager Integration

This registry serves as reference for:

1. Manual Whitelist Updates

  • Quick UUID lookup for command-line operations
  • Verification before adding/removing players

2. Troubleshooting

  • Match player reports to UUIDs
  • Identify which player data files belong to whom
  • Track player history across username changes

3. Batch Operations

  • Adding multiple players to new servers
  • Migrating whitelists between servers
  • Backup/restore player data

4. Analytics

  • Player activity tracking
  • Server population metrics
  • Testing participation records

Server-Specific Whitelists

All The Mons (38.68.14.30:25565)

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner (Added 2026-02-18)
  • Unicorn20089 (88a29147-9a2d-48a0-8980-c42b60f7e010) - Tester (Added 2026-02-18, Currently playing)

Vanilla 1.21.11 (38.68.14.29:25565)

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner
  • To be populated

Stoneblock 4

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner
  • To be populated

Society: Sunlit Valley

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner
  • To be populated

Reclamation

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner
  • To be populated

The Ember Project (NC1)

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner
  • To be populated

Minecolonies: Create and Conquer (NC1)

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner
  • To be populated

All The Mods 10 (NC1)

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner (Currently playing)
  • To be populated

Homestead (NC1)

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner
  • To be populated

EMC Subterra Tech (NC1)

  • Frostystyle (83a22372-6b3e-4424-814e-ad6b3a36be03) - Owner
  • Gingerfury66 (9f690976-75e8-4d7c-8d4f-e4146d6ae761) - Co-Owner
  • To be populated

Adding New Players

Process:

  1. Obtain UUID (from logs, online lookup, or Whitelist Manager)
  2. Record in this registry: 
    **[Username]**
- **Username:** [current username]
- **UUID:** [full uuid]
- **Role:** [Staff/Tester/Subscriber/Player]
- **Servers:** [list of servers]
- **Added:** [YYYY-MM-DD]
- **Notes:** [any relevant info]
  3. Add to server whitelists (via Whitelist Manager or manual)
  4. Update server-specific lists (in this document)
  5. Commit changes to Git

Removing Players

When removing a player:

  1. Do NOT delete from this registry (keep historical record)
  2. Update their entry:
    • Add "Removed: [date]" field
    • Add "Reason: [if applicable]" field
  3. Remove from active server whitelists
  4. Move to "Former Players" section (below)

Former Players

Players who have been removed from whitelists

None yet

Username Change History

Track username changes for continuity:

Example format:

[UUID] - [Old Username] → [New Username] (Changed: YYYY-MM-DD)

None recorded yet

Maintenance

This registry should be updated:

  • ✅ When any new player is whitelisted
  • ✅ When staff/testers are added
  • ✅ When players are removed
  • ✅ When usernames change
  • ✅ During server launches (document initial whitelists)

Committed to Git: After every change

Related Documentation

  • Whitelist Manager Deployment: deployments/whitelist-manager/
  • Server Testing Procedure: docs/procedures/new-server-testing-procedure.md (FFG-SOP-001)
  • Infrastructure Manifest: docs/core/infrastructure-manifest.md
  • Discord Structure: (Holly mentioned as community member)

Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️

Player records = Community history

Reference in New Issue View Git Blame Copy Permalink