BlueMapSkinSupport: Correct Player Skins on BlueMap

Understanding BlueMapSkinSupport and Custom Player Heads BlueMap has become a favorite tool for server owners who want to render their Minecraft worlds in a stunning 3D web viewer. However, one common frustration is that player heads on the map often show up as the default Steve or Alex skin, esp...

Download BlueMapSkinSupport for Minecraft 1.20.6, 1.9

Original name: BlueMapSkinSupport

Minecraft: 1.20.6, 1.9

FileVersionLoaderSize
BlueMapSkinSupport-2.0.jar1.20.6—43 КБDownload
BlueMapSkinSupport-3.0.jar1.20.6—43 КБDownload
BlueMapOfflineSkinSupport-1.0.jar1.9—41 КБDownload
BlueMapOfflineSkinSupport-1.1.jar1.9—42 КБDownload
BlueMapOfflineSkinSupport-1.2.jar1.9—42 КБDownload
BlueMapOfflineSkinSupport-1.3.jar1.9—42 КБDownload

Understanding BlueMapSkinSupport and Custom Player Heads

BlueMap has become a favorite tool for server owners who want to render their Minecraft worlds in a stunning 3D web viewer. However, one common frustration is that player heads on the map often show up as the default Steve or Alex skin, especially on offline-mode servers or when custom skin plugins are in use. BlueMapSkinSupport steps in to solve exactly that problem, making sure every player’s unique appearance is reflected accurately on the map.

How It Works with Custom Skins

BlueMap normally fetches skins directly from Mojang’s servers, which works fine for online-mode servers where everyone has a legitimate account. But things get messy when you run an offline-mode server or rely on plugins like SkinsRestorer to let players choose their own skins. In those setups, BlueMap’s built-in skin downloader either fails or pulls the wrong data, leaving you with a sea of identical heads. BlueMapSkinSupport intercepts the skin request process, pulling the correct skin from whatever custom provider you have installed—or even handling offline-mode servers with no extra plugins. The generated player heads are visually identical to BlueMap’s native ones, so the map experience stays seamless.

Supported Skin Provider Plugins

The plugin works right out of the box with the most popular skin management tools:

  • SkinsRestorer / SkinsRestorerX (version 15.x or higher, with 14.1 as the minimum). This is the recommended choice for most server owners.
  • CustomSkinsManager (deprecated, but supported for legacy setups). The original project was abandoned, but support was added because some communities still rely on it.

Even if you don’t use any custom skin plugin, BlueMapSkinSupport will still function. It simply ensures that player heads appear correctly in offline-mode environments where Mojang skin servers aren’t accessible.

Installing BlueMapSkinSupport on Your Server

Getting the plugin up and running is a straightforward process, but a few prerequisites need to be in place first.

Prerequisites

  • A Minecraft server running Paper (recommended), Spigot, or CraftBukkit for version 1.8 or higher. Any Bukkit-compatible server software should work, including forks.
  • BlueMap 3.8 or higher (BlueMapAPI 2.3.0 or later). Older versions down to BlueMap 2.1 are technically supported with a minor source code tweak, but sticking to the latest release is advised.
  • Optionally, one of the supported custom skin provider plugins listed above.

If you’re running a network with Waterfall or BungeeCord, remember that the plugin must be installed on every backend Minecraft server individually—it doesn’t sit on the proxy.

Step-by-Step Installation

  1. Stop your server completely with the /stop command.
  2. Download the latest JAR file from the GitHub releases page. (Look for the file named something like BlueMapSkinSupport-x.x.x.jar.)
  3. Place the JAR into your server’s /plugins/ directory.
  4. If you want to tweak behavior, open /plugins/BlueMapSkinSupport/config.yml after the first run. The default configuration works for most setups, but you can adjust settings if needed.
  5. Edit BlueMap’s plugin.conf file and disable its built-in skin downloader. This prevents BlueMap from overwriting the skins generated by BlueMapSkinSupport.
  6. Start your server and enjoy correctly displayed player heads on the BlueMap web UI.

For those who prefer a more streamlined approach to server management, the foxygame.net launcher provides a modern, flexible way to handle plugins—you can install BlueMapSkinSupport directly from its menu without manually moving JAR files around. This convenience makes it an excellent choice for both newcomers and experienced admins looking to save time.

Building from Source

If you want to compile the plugin yourself, the process is simple and well-documented. You’ll need IntelliJ IDEA (the free Community Edition is perfect) or a working Maven command-line setup, plus Adoptium Temurin 8 LTS (OpenJDK + HotSpot JVM) for compatibility. Newer JDK versions work too, but version 8 was targeted to ensure broad server compatibility.

Using IntelliJ IDEA

  1. Clone the repository: git clone https://github.com/akemin-dayo/BlueMapSkinSupport.git
  2. Open the cloned project directory in IntelliJ IDEA.
  3. Open the Maven panel on the right, navigate to “Lifecycle,” and double-click package.
  4. Your fresh JAR will appear in the /target/ folder.

Using the Command Line

  1. git clone https://github.com/akemin-dayo/BlueMapSkinSupport.git
  2. cd BlueMapSkinSupport
  3. mvn package
  4. Grab the built JAR from the /target/ folder.

No matter which method you choose, the resulting plugin file is identical and ready to drop into your server’s plugins folder.

Conclusion

BlueMapSkinSupport fills a small but crucial gap in the BlueMap ecosystem. By bridging the divide between custom skin providers, offline-mode servers, and the map’s rendering engine, it ensures every player’s chosen look is faithfully represented. The installation is painless, the configuration minimal, and the end result is a more immersive map experience for everyone who visits your server’s web view. Whether you run a small private community or a large network, this plugin is a worthwhile addition to your toolkit.