Citadel Reskins

How it works

Every order is one zip that installs on a DayZ server the same way, whether a server owner or a player bought it.

  1. Pick your skinsA single item, a weapon with its matching attachments, or a whole collection as a bundle.
  2. Choose the licenceFor one player (their Steam64) or a whole server (its IP and port).
  3. Pay with StripeCard, Apple Pay or Google Pay. We never see your card details.
  4. Download the zipStraight away, and from the link in your email whenever you need it again.
  5. Drop it on the serverMod folder, key and server files. Players buy and hand it to their server owner, who installs it the same way.

What's in the zip

CitadelReskins_CR-2026-00042/ ├─ READ ME FIRST.txt ├─ LICENSE.txt · license.json ├─ @CitadelReskins/ │ ├─ addons/ CitadelSkins.pbo + one signed pbo per skin │ └─ keys/ AxionDevKey.bikey ├─ keys/ AxionDevKey.bikey (for the server's keys folder) └─ server_files/ ├─ types_CitadelReskins.xml ├─ cfgspawnabletypes.example.xml ├─ expansion/Market/CitadelReskins.json └─ lbmaster/SkinSystem/Repaints.json · Permissions.json

Installing on a server

  1. Copy @CitadelReskins into the server's root folder, beside your other mods. On a later order, copy its addons into the same folder and let the newer CitadelSkins.pbo replace the old one: one folder holds every order.
  2. Copy keys\AxionDevKey.bikey into the server's keys folder. The pbos are signed with it; without the key the server kicks anyone who loads them.
  3. Add @CitadelReskins to -mod=, not -serverMod=: players need the textures. Ship it to them the way you ship your other client mods.
  4. Load it after the mods the skins are made for (A6, AJ's Weapons, FOG, BaseBuildingPlus). Vanilla skins need nothing else.
  5. Add the entries from types_CitadelReskins.xml to your mission's db\types.xml. They are nominal 0: skins never spawn as loot, you hand them out by trader, reward or admin tools.

Expansion Market

Copy expansion\Market\CitadelReskins.json to profiles\ExpansionMod\Market and add CitadelReskins to a trader. Prices in the file are placeholders; set your own. Weapons are sold with their matching attachments.

LBmaster SkinSystem

Merge Repaints.json and Permissions.json into profiles\LBmaster\Config\SkinSystem. Players can then repaint the base item with the skin, and its attachments follow. On a player licence the repaint is limited to a permission group that holds that player's Steam64 only.

Checking it worked

When the server starts, CitadelSkins checks every skin it loads and writes one line to the server's .RPT log: [CitadelSkins] self-test: … 0 problems. Any problem is named on its own line.

Bought as a player?

Give the zip to your server's owner or admin. Your licence names your Steam64; on servers with LBmaster's SkinSystem the skin is yours alone.

Stuck? Get in touch with your order number.