compatibility guide

SkinsRestorer Fabric, NeoForge and Forge Compatibility

Understand current SkinsRestorer Fabric and NeoForge support, why Forge searches can be outdated, loader matching, dependencies and safe mod installation.

SkinsRestorer Fabric, NeoForge and Forge Compatibility original feature illustration

Published: July 30, 2026 · Reading focus: compatibility

SkinsRestorer is commonly searched as a Forge mod, but current official installation documentation highlights Fabric and NeoForge mod builds for supported modern versions. Treat old Forge instructions as version-specific until verified.

Current mod platforms

Official documentation provides dedicated installation paths for Fabric and NeoForge. These mod releases currently focus on the latest supported Minecraft version and aim to provide the same core skin features as the Bukkit plugin on that release.

Fabric installation

Install the correct Fabric Loader for the server version, add the matching Fabric API dependency where required, then place the SkinsRestorer mod in the `mods` folder. Start the dedicated server and review dependency messages.

NeoForge installation

Use a current supported NeoForge server, place the matching SkinsRestorer mod in the `mods` folder, restart and use the status command to verify. Do not combine an unrelated plugin jar with a mod installation.

Useful command examples

Verify the mod status on supported mod builds.

/skinsrestorer status

Alternate status command where registered.

/sr status

Test the normal player-facing behaviour.

/skin Notch

What about Forge?

Search results and old community guides may mention Forge. Current official documentation lists NeoForge rather than a general current Forge path. Do not assume that a NeoForge build works on Forge; loaders are separate and compatibility must be explicit.

Match all four versions

Check Minecraft version, loader type, loader version and SkinsRestorer build. A mismatch in any one can produce missing-class, dependency or mapping errors during startup.

Server-side expectations

The mod is installed on the server environment described by the documentation. Client behaviour can still be affected by launcher or rendering conditions, but most setup errors should be investigated in the server log first.

Safe upgrade process

Create a copy of the server, update the loader and dependencies according to their requirements, then test SkinsRestorer. Upgrading everything directly on production makes it difficult to identify which change caused a failure.

Related SkinsRestorer guides

This guide is an independent resource. It does not replace the documentation shipped with the exact build you install. Return to the SkinsRestorer guide library or review the download safety notice.