![]() ![]() sr createcustom - Define a usable custom skin. sr drop - Removes skins data from database. skin update - Updates your current skin. wildcards ("*") don't work Player commands: only works with "NewPermissions: true" (if false see old perms!) config.yml) More info & Permissions see our command page. Here's a list with commands and permissions to use them Note: If you use the plugin with BungeeCord/Velocity you will need to set the permission on the BungeeCord/Velocity side (e.g. Optional Edit the config inside velocity/plugins/skinsrestorer/ folder.Restart (/restart or /stop) all servers. ![]() ![]() Check & set on every Paper server paper.yml -> velocity-support: enabled: true.Place the SkinsRestorer.jar in /plugins/ folder of every Velocity server.Place the SkinsRestorer.jar in /plugins/ folders of every Paper server.Optional Edit the config inside bungee/plugins/SkinsRestorer/ folder.Give permissions inside the bungeeserver.Check & set on every Spigot server spigot.yml -> bungeecord: true.Place the plugin in /plugins/ folder of every BungeeCord server.Place the plugin in /plugins/ folders of every Spigotserver.Note: Make sure to review BungeeCord installation steps if you're using a proxy! For Spigot / Paper: To install SkinsRestorer, read our installation guide. Loading configuration from file: E:\Users\Ocelot\AppData\Roaming\.tlauncher\tlauncher-2.0.Nederlands Where can I use SkinsRestorer?Ĭurrently, you can use SkinsRestorer on these platforms: Servers:įollow this little guide, so you don't go wrong Here follows the Entirety of the console output from the launcher: I have tested this issue with Alternative launchers, all still show the same issue. (I played perfectly fine Thursday night for hours, come Saturday, it is Broken) This issue is NOT present when starting 1.12. The game still crashes with both 32 and 64bit versions of Javaw.exe I have reinstalled Java, GPU drivers, Minecraft and its Libraries, and Disabled Integrated GPU. The game worked perfectly a night or two ago. The game will no longer start on version 1.14.3 down to 1.13. If Monitor 1 is disabled via Second Screen Only mode, the crash will occur. Monitor 1 is my Secondary, and Monitor 2 is the Primary. I have successfully replicated the issue and fixed by switching back to Extend mode. EDIT: This issue I have found is caused when you have two displays and Windows is projecting on Second Screen Only mode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |