VOIDAMP SKIN GENERATOR

🎨 The workshop

Every paintable part of VOIDAMP, listed by its plain name:

• Chrome — the player's body: the main chrome, its light and dark edges, and the panels the windows sit in.
• Buttons — the face of every button and the lettering on it.
• The accent — the highlight color, the spark that says whose player this is.
• The LCD — the glowing readout: its dark background, the bright green of playing time, the amber of the tuner, the dim green of what's asleep.
• The playlist — the song list's background and lettering, and the colors of the song you've selected.
• Fonts — the LCD face (with title and time sizes) and the interface face and sizes.

Paint one part or paint them all — a two-color touch-up and a full re-skin are both just skins.

🪜 The workflow — five steps

• 1 · Pick a starting skin — any skin VOIDAMP already wears, or a pack a friend handed you.
• 2 · Paint — pick a part, pick a color; it changes.
• 3 · Preview — a living model of VOIDAMP (deck, equalizer, playlist, tuner) wears your skin as you paint. What you see is what the player will wear.
• 4 · Export — name your skin, sign it with your name as its creator, and out comes your skin three ways: a one-file pack, a Skin Code, and a preview card — ready to keep, and ready to trade.
• 5 · Install into VOIDAMP — drop the pack into VOIDAMP's skins and pick it in the Skins menu. VOIDAMP's guarded loader checks it first, then wears it.

🔒 A skin pack is data — never code

A skin pack is the exact same kind of file VOIDAMP itself is dressed in: a skin.json — a list of colors and fonts, in a folder. There is nothing in a skin that can run, execute, or phone home, because a skin is data, never code — information the player reads, never instructions it obeys.

• The guarded loader — before VOIDAMP wears any pack, it checks it: every color a real color, every part accounted for. A missing part falls back to a safe default; a broken pack is refused in plain words. Never a crash, never a half-painted player.
• The worst case is ugly — a bad skin can be garish. It cannot be dangerous. Switch back in one pick and it's gone.
• Your name rides inside — the creator name you sign at export lives in the pack itself, wherever it travels.
• Sharing is handing over a file — no marketplace, no account, no upload. Files between people, the house way; a pack you receive gets the same guarded check as one you made.

The generator itself is a local, offline tool. It makes files. It has no accounts, nothing to sign into, and no network door at all — a paint bench doesn't need one.

🤝 Make it. Trade it.

A skin you make is a skin you can trade — dead easy, with anyone. It works because a skin is data, never code: safe to pass around by design. When you finish a skin, the Generator hands it to you three ways:

• The Skin Code — your whole skin as one copy-paste block of text. It rides anywhere text goes: an email, an X post, a Discord message. A friend pastes the code into VOIDAMP — or into the Generator — and the skin is theirs.
• The preview card — a picture of your skin on the player, made for posting on socials so people can see it first. Paste the Skin Code under the picture, and anyone who wants it takes it right from the post.
• The one-file pack — the skin as a single file: attach it to an email, or send it sealed, person to person, with QDROP.

No accounts. No servers. Nothing is hosted anywhere — people trade hand to hand, and every skin that arrives gets the same guarded loader check as one you made yourself.

⬇️ Downloads

📖 The manual (PDF)

The full guide is ready to read now — what the Skin Generator is, the five-step workflow, what a skin pack is, and the parts you can paint.

VOIDAMP Skin Generator — How It Works (PDF)
What it is, the five steps from starting skin to wearing yours, the data-never-code promise and the guarded loader, the paintable parts, and sharing skins. 4 pages · SHA-256: 3fb6eddfc3bc235eac5ec182442bcb7d4e7f498a749c513063da8d6c22af54c4