firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity

Task #64: Upload The Catalyst (Arcane) Minecraft Skin — Holly #84

New Issue
Open
opened 2026-03-20 20:46:18 -05:00 by mkrause612 · 0 comments
mkrause612 commented 2026-03-20 20:46:18 -05:00
Owner
Copy Link

Objective

Upload The Catalyst (Arcane Storm) Minecraft skin to Holly's Minecraft Java Edition profile.

Character Details

  • Name: The Catalyst (Holly/unicorn20089)
  • Element: Arcane Storm (purple lightning)
  • Colors: Deep purple (#6A0572), electric violet (#A64AC9), silver
  • Theme: Arcane robes with lightning/storm patterns

Skin Files Ready

Location: branding/minecraft-skins/

Two versions:

  • the-catalyst-arcane-64x64.png (standard, 9.7K)
  • the-catalyst-arcane-128x128.png (HD, 32K)

Recommendation: Use 64x64 (standard) version

Upload Instructions

Step 1: Download skin file from ops manual
Step 2: Go to https://www.minecraft.net/ and log in
Step 3: Profile → Choose File → Upload skin
Step 4: Select Alex model (slim arms)
Step 5: Test in Minecraft Java Edition (F5 to view character)
Step 6: Test on Firefrost server, verify others can see it

BONUS: Take Trinity group screenshot with all three founders together!

Full detailed instructions: docs/tasks/catalyst-arcane-skin/README.md

Verification Checklist

  • Skin uploaded to minecraft.net
  • Alex model selected
  • Visible in singleplayer
  • Visible on Firefrost server
  • Other players confirm they see it
  • Screenshot taken
  • BONUS: Trinity group screenshot

Time Estimate

10-15 minutes

Dependencies

  • Skin files generated (COMPLETE - by Task #61)
  • Holly's Minecraft account access
  • Minecraft Java Edition

Success Criteria

  • Arcane Storm skin live on Holly's account
  • Purple robes, lightning patterns, silver trim visible
  • Works on Firefrost servers
  • Team can see it

Related Tasks

  • Task #61: AI-Generated Minecraft Skins (parent)
  • Task #62: Michael's Frost skin
  • Task #63: Meg's Fire skin
### Objective Upload The Catalyst (Arcane Storm) Minecraft skin to Holly's Minecraft Java Edition profile. ### Character Details - **Name:** The Catalyst (Holly/unicorn20089) - **Element:** Arcane Storm (purple lightning) - **Colors:** Deep purple (#6A0572), electric violet (#A64AC9), silver - **Theme:** Arcane robes with lightning/storm patterns ### Skin Files Ready **Location:** `branding/minecraft-skins/` Two versions: - `the-catalyst-arcane-64x64.png` (standard, 9.7K) - `the-catalyst-arcane-128x128.png` (HD, 32K) **Recommendation:** Use 64x64 (standard) version ### Upload Instructions **Step 1:** Download skin file from ops manual **Step 2:** Go to https://www.minecraft.net/ and log in **Step 3:** Profile → Choose File → Upload skin **Step 4:** Select **Alex model** (slim arms) **Step 5:** Test in Minecraft Java Edition (F5 to view character) **Step 6:** Test on Firefrost server, verify others can see it **BONUS:** Take Trinity group screenshot with all three founders together! **Full detailed instructions:** `docs/tasks/catalyst-arcane-skin/README.md` ### Verification Checklist - [ ] Skin uploaded to minecraft.net - [ ] Alex model selected - [ ] Visible in singleplayer - [ ] Visible on Firefrost server - [ ] Other players confirm they see it - [ ] Screenshot taken - [ ] BONUS: Trinity group screenshot ### Time Estimate 10-15 minutes ### Dependencies - Skin files generated (COMPLETE - by Task #61) - Holly's Minecraft account access - Minecraft Java Edition ### Success Criteria - Arcane Storm skin live on Holly's account - Purple robes, lightning patterns, silver trim visible - Works on Firefrost servers - Team can see it ### Related Tasks - Task #61: AI-Generated Minecraft Skins (parent) - Task #62: Michael's Frost skin - Task #63: Meg's Fire skin
mkrause612 added the
status
to-do
priority
high
type
task
area/websitefor/holly labels 2026-03-20 20:49:31 -05:00
mkrause612 added
status
backlog
 and removed
status
to-do
 labels 2026-03-20 20:53:55 -05:00
mkrause612 added this to the Firefrost Operations project 2026-03-20 20:57:38 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/automation
n8n workflows and automation
 area/billing
Paymenter billing system
 area/development-tools
Internal tools for workflow automation and team productivity
 area/email
Mailcow email system
 area/game-servers
Minecraft or other game servers
 area/networking
Network infrastructure and configuration
 area/operations
General operations and documentation
 area/panel
Pterodactyl Panel
 area/website
Ghost CMS website
 area/wings
Pterodactyl Wings
 duplicate
This issue is a duplicate of another issue
 for/holly
Assigned to Holly (unicorn20089)
 for/meg
Assigned to Meg (GingerFury)
 for/michael
Assigned to Michael (Frostystyle)
 good-first-issue
Good for newcomers
 help-wanted
Extra attention needed
 needs-board-sync
New issue needs to be added to project board
 operations
priority
critical
Emergency — immediate attention required
priority
high
Important — address soon
priority
low
Nice to have, not urgent
priority
medium
Normal priority
status
backlog
Not yet started, in backlog
status
blocked
Cannot proceed, blocked by dependency
status
done
Completed and closed
status
in-progress
Currently being worked on
status
review
Work complete, awaiting review
status
to-do
Ready to start, in queue
type
bug
Something isn't working
type
docs
Documentation improvements or additions
type
feature
New feature or enhancement request
type
infrastructure
Infrastructure, deployment, or DevOps work
type
refactor
Code refactoring or technical debt
type
task
General task or work item
wont-do
This will not be worked on
No Label area/website for/holly
priority
high
status
backlog
type
task
Milestone
No items
No Milestone
Projects
Clear projects
No project Firefrost Operations
Assignees
Clear assignees
Gingerfury Unicorn20089 mkrause612
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: firefrost-gaming/firefrost-operations-manual#84
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?