SkinsRestorer skin gets overridden when rejoining server

[Mitterrss]

What happened?

When I set a skin for me using SkinsRestorer, it works normally. But the moment I rejoin the server, the skin is reset to my account's original one.

I have already set "forwardSkin" to false and "nameChangeCheck" to true as the plugin says that "It is needed to allow premium name change to work correctly". Still does not work. I'm running on Paper and have the latest version of both plugins (SkinsRestorer & FastLogin). Have also tried the fix for nameChangeCheck (setting user-cache-size to 0 in spigot.yml and deleting usercache.json).

I'm sure that FastLogin is the cause because when I removed it the skin that was set did not get reset on rejoin.

Steps to reproduce

You need a premium account for this.

1. Install SkinsRestorer, AuthMe, ProtocolLib and FastLogin in your server
2. Open FastLogin's config.yml file
3. Set forwardSkin to false and nameChangeCheck to true
4. Restart to apply changes
5. After joining the server, set any skin with /skin
6. Once the skin is set, leave the server and then join it again
7. Your skin was reset to your original one - that should not happen.

Plugin list

AuthMe, ChatManager, Citizens, CleanPing, CommandAPI, DecentHolograms, DiscordSRV, dynmap, Elevator, EpicRename, Essentials, EssentialsWarpGUI, explock, EZColors, ezEdits, fakeplayer, FastAsyncWorldEdit, FastLogin, floodgate, Geyser-Spigot, GSit, HeadDatabase, Images, ItemEdit, LuckPerms, MTVehicles, ProtocolLib, RealTimePlugin, SimpleClans, SkBee, SkinsRestorer, Skript, skript-gui, Stopwatch, Timer, Vault, ViaBackwards, ViaVersion, voicechat

Configuration file

https://hastebin.com/share/nopiwegifa.yaml

Server log

No response

Plugin version

1.12-SNAPSHOT-65a379c

Platform

Spigot

Relevance

• I tried the latest build
  (build refers to development builds not necessary a release version; i.e. v1.10 is out of date)

• I checked for existing tickets -
  If there are, please vote them with a thumbs reaction and not create new ones