SkinsRestorer LogoSkinsRestorer

Configuration reference

Find exact configuration keys by section and avoid obsolete examples.

SkinsRestorer 15.12.6All platformsReviewed

This reference covers every declared configuration property in SkinsRestorer 15.12.6. It separates lookup tables from server management procedures.

File structure

Edit the existing sections in the active config.yml. On Bukkit, the file is plugins/SkinsRestorer/config.yml.

Storage settings

Default skins and cache durations control fallback selection and account lookup caching.

Command settings

Command behavior covers cooldowns, restrictions, history, favorites, and command registration.

Login settings

Login behavior controls canceled logins, online-mode selection application, and client warnings.

Server settings (Backend only)

Server behavior covers refresh, mounts, sound, and backend proxy detection. Server-specific values do not configure the proxy itself.

Proxy settings (Proxy only)

Proxy command restrictions allow or block commands by backend name.

API settings

External services covers MineSkin keys, recommendations, batching, and Ely.by.

GUI settings

Menu categories and entries lists the exact category keys and defaults.

Advanced settings

Advanced behavior changes join application, refresh workarounds, and external connections.

Debug settings

Messages and diagnostics covers dev.debug, locales, prefixes, and dates.

Correct common outdated keys

  • Use database.type: MYSQL or POSTGRESQL for new SQL configuration. Earlier database.enabled configuration is migrated by the plugin.
  • commands.perSkinPermissions is a boolean, not a section with enabled and list.
  • Use api.mineskinAPIKey and api.mineskinSecretSkins with that exact capitalization.
  • Use gui.custom and gui.custom.onlyShowList, rather than customSkins and onlyList.
  • Use proxy.notAllowedCommandServers.ifNoServerBlockCommand.
  • Mount refresh keys include OnSkinUpdate, such as server.dismountPlayerOnSkinUpdate.

Apply an excerpt

Edit the matching section in the existing file. Do not paste duplicate top-level keys. Restart after storage, proxy detection, or command registration changes.

For permissions, use the command reference. For release verification and maintenance, use the documentation sources.

Did this page help?

Last updated on

On this page