Guides

Allumeria Skins

Default faces, custom layers, and why first-person hides your body.

Last updated:

Skins and Characters

Allumeria is first-person. Steam threads titled “How do you see your own character?” and “Skin template?” started the week Early Access opened because the game shows arms and a hotbar, not a full-body mirror. Skins still matter: friends see you in multiplayer, and the default set is how you tell four people apart in a cave.

Built-in skins

As of late demo and 0.15 you pick a name and a skin at character create. The four shipped examples are Amber, Clay, Jasper, and Ruby. Ruby is the historic default. Characters keep inventory and stats across worlds; the skin is part of the character file, not the world file. You can make a throwaway world to test a look without losing a Forest Pickaxe.

The player model got wider arms in 0.12 so Ruby stopped looking like a breadstick. Held items without a 3D model show as sprites. None of that is a third-person toggle. If you want a full-body shot, use F2 screenshots from a friend’s view in co-op, or wait for a camera mode that 0.15 does not advertise.

Custom files

Drop skin files into /res/textures/skins/ or edit the examples already there. Official notes describe lots of layers and quads so custom skins can carry more detail than a single PNG. There is no Steam Workshop button yet. Asset Packs from 0.14.3 are the texture hook for broader packs; skins are still a folder drop. If a file does nothing, you put it in the wrong install directory (demo versus paid) or the game is still using a cached example. Restart the client after a copy.

Do not download “Allumeria skin injector” executables. This is a Steam voxel game, not a Roblox experience. If an antivirus quarantines a random injector, that is not an Allumeria bug. Launch issues that are actually the game belong on troubleshooting.

Seeing yourself

First-person hides the torso. Reflections in water are not a reliable vanity mirror. Practical options: join a friend’s hosted world and ask them to stand back; build a screenshot booth with RGB lamps from the building guide; or accept that your main view is tools and torches. F1 hides HUD for cleaner shots. F2 writes to your pictures folder. Both binds are in controls.

Skins do not change hitboxes, stamina, or merchant prices. They will not make a Farmer sell bait. They will not open a Forest Door. Equip Gecko Gloves if you want to climb your own statue for a screenshot.

Co-op etiquette

Install the skin before you press Join Game. Mid-session file drops may not appear until a reconnect. Hosts who care about identity can keep a chest of named hats as a backup, but hats are items, not the layered skin system. If two Rubys enter a Forest Dungeon, paint your lamps different colours. Colour trails are cheaper than voice chat arguments.

Custom skins are cosmetic freedom the same way the Paint Roller is. Use both after the first night in getting started, not instead of a Flint Pickaxe. When Workshop support exists, this page will point at it from the links page. Until then, the skins folder is the whole pipeline.

FAQ

Frequently Asked Questions

Quick answers to the most common questions.

How do I see my Allumeria character?

The game is first-person. Use co-op, F2 screenshots from a friend’s camera, or wait. There is no shipped third-person toggle in 0.15.

Where do custom skins go?

Place files in /res/textures/skins/ inside the game folder, or edit the four example skins. Restart after copying.

What are the default skins?

Amber, Clay, Jasper, and Ruby. Ruby is the usual default name and look.

Do skins change gameplay?

No. They are cosmetic. Shops, dungeons, and bosses ignore them.