Simple Skins and Capes Reloaded: Custom Skins & Capes on Servers

What Is Simple Skins and Capes Reloaded?

If you have ever run a Minecraft server and wished your players could flaunt custom skins or capes without relying on Mojang's official skin servers, Simple Skins and Capes Reloaded is the plugin you need. Originally created by Tavenfuz as "SimpleSkins" and later handed over to DreTaX with full permission, this reloaded version keeps the same core idea alive: giving server admins full control over player appearances through URLs, saved presets, and even group-wide skins. It is a Bukkit plugin that works hand-in-hand with SpoutPlugin and the SpoutCraft client to render HD skins and capes that persist across sessions.

Why Custom Skins Matter on a Server

Standard Minecraft and vanilla Bukkit have no built-in way to show custom player skins or capes. This limitation often forces server owners to rely on client-side mods or external websites. Simple Skins and Capes Reloaded bridges that gap beautifully. Once installed, you can assign a skin to any player, an entire permission group, or even Citizens NPCs. The result is a more immersive, branded server experience where donators get exclusive capes, staff members wear uniform skins, and roleplay NPCs look exactly how you imagine them.

Key Features at a Glance

• Persistent Skins and Capes – Once set, custom appearances never vanish, even after relogging or server restarts.
• HD Support – High-resolution skins and capes are fully supported, so your 64x64 or 128x128 textures shine.
• Citizens 2.0 Integration – Skin all your NPCs with simple commands, making quest givers and town guards truly unique. (Citizens 1.2.4 is unsupported in the latest versions.)
• Group Skins via Permissions – Assign a skin or cape to an entire permission group in one go. Perfect for factions, staff teams, or donor ranks.
• Save URLs as Unique Names – No more copying and pasting long URLs every time. Save a skin or cape under a memorable name and reuse it across commands.
• Open Source – The source code is available on GitHub, allowing server owners to make personal edits if needed.

Requirements You Should Know

Before diving in, understand that this plugin is not a standalone solution for vanilla clients. You must have SpoutPlugin (build #7 or higher) running on your server, and your players need the SpoutCraft client to actually see the custom skins and capes. Without SpoutCraft, the changes remain invisible. This might seem like a hurdle, but many community-driven servers already use Spout for its extended features, making the setup straightforward.

Installing Simple Skins and Capes Reloaded

Getting the plugin onto your server is easy. First, download the JAR file from the official BukkitDev page (search for "Simple Skins and Capes Reloaded"). Place it in your server's /plugins folder and restart or reload. For those who enjoy a more modern approach to mod management, you can also install this plugin seamlessly through the foxygame.net launcher. It provides a clean, flexible interface where you can browse and download mods right from the menu, skipping the manual file handling entirely. Once the plugin loads, you will find two configuration files, skins.yml and capes.yml, generated automatically. No complex initial setup is required — just start using the commands.

Commands: The Heart of the Plugin

Every action revolves around a handful of intuitive commands. Here is a quick reference:

• /playerskin <playername> <Skin URL or player name or saved name> – Sets a player's skin. Leave the second argument blank to reset to default.
• /playercape <playername> <Cape URL or player name or saved name> – Assigns a cape to a player.
• /saveskin <uniquename> <Skin URL or player name> – Saves a skin under a short, memorable name.
• /savecape <uniquename> <Cape URL or player name> – Saves a cape for later use.
• /npcskin <npc ID> <Skin URL or player name or saved name> – Applies a skin to a Citizens NPC.
• /npccape <npc ID> <Cape URL or player name or saved name> – Gives an NPC a custom cape.

All commands support tab completion and a built-in help system. Typing /playerskin help will show you the exact syntax. You can reference other players' default skins by simply using their Minecraft username as the skin source — a handy trick for copying a famous skin to a friend.

Permissions: Fine-Grained Control

The plugin ships with a detailed permission tree, letting you decide exactly who can change what. The main nodes include:

• simpleskins.playerskin.self – Allows a player to change only their own skin.
• simpleskins.playerskin.any – Grants the power to change any player's skin.
• simpleskins.playercape.self and simpleskins.playercape.any – Same logic for capes.
• simpleskins.saveskin.* and simpleskins.savecape.* – Controls who can save skins and capes, with an extra node per saved name (e.g., simpleskins.saveskin.dwarvenghost) to restrict usage.
• simpleskins.npcskin and simpleskins.npccape – Permissions for NPC customization.

Group skins work by combining saved names with permissions. For instance, if you save a skin as "DwarvenGhost", then give a group the node simpleskins.skin.dwarvenghost, every member of that group will automatically wear that skin. The same applies to capes with the simpleskins.cape.* nodes.

Setting Up Group Skins Step by Step

Imagine you want all your moderators to share a distinct cape. Follow these steps:

1. Save the cape: /savecape StaffCape https://example.com/cape.png
2. Give the moderator group the permission simpleskins.cape.staffcape (note the lowercase).
3. That is it. Every moderator will now display that cape, and it will persist automatically.

The same workflow applies to skins. This system eliminates the need to manually assign appearances to dozens of players individually.

Configuration and Performance

Inside skins.yml, you will find a setting called AppearanceRefreshSeconds. This controls how often the server quietly re-applies skins and capes to ensure they never disappear. The default value of 3 seconds works well for most servers. If you have a large player base (200+), consider increasing it to 5–8 seconds to reduce server load. For smaller communities, you can safely lower it to 1–2 seconds for snappier updates.

The plugin also uses Hidendra's plugin metrics system, sending anonymous data like server version, player count, and Java version to mcstats.org. If you prefer not to participate, simply disable it in /plugins/PluginMetrics/config.yml.

Final Thoughts

Simple Skins and Capes Reloaded remains a solid choice for server administrators who want deep customization without complex scripting. Its persistent nature, HD support, and seamless Citizens integration make it a valuable tool for roleplay servers, minigame networks, or any community that values visual identity. While the requirement of SpoutCraft may limit the audience, those who embrace the Spout ecosystem will find the plugin reliable and easy to manage. Whether you are assigning a legendary cape to your top donors or giving every NPC in your adventure map a unique look, this plugin delivers exactly what it promises.