SKELLETT SPAMMING ERROR!

  • Welcome to skUnity!

    Welcome to skUnity! This is a forum where members of the Skript community can communicate and interact. Skript Resource Creators can post their Resources for all to see and use.

    If you haven't done so already, feel free to join our official Discord server to expand your level of interaction with the comminuty!

    Now, what are you waiting for? Join the community now!

  • LOOKING FOR A VERSION OF SKRIPT?

    You can always check out skUnity Downloads for downloads and any other information about Skript!

Status
Not open for further replies.

Adrihun

Member
Feb 1, 2017
368
6
0
Problem: When i shut down my Spigot server (with skellett running on it connected to skellett proxy), it gives me a big error message inside Bungeecord.

https://hastebin.com/xetikezata.lua


Skript Version:
Skript 2.2 (dev25)
Skript Author: Bensku
Minecraft Version: 1.8.9 <- Spigot
1.11 <- Bungee
---

Addons using (including versions):
Skellett - 1.9.1
Skellett Proxy - 1.3.1

Troubleshooting:

Have you tried searching the docs? Yes
Have you tried searching the forums? Yes
What other methods have you tried to fix it? Looked at the error, looked in the config, restarting server, more..
 
Last edited:
Sorry
[doublepost=1495665037][/doublepost]@Duetro Do you know how to fix this?
 
Last edited by a moderator:
Post your configs, it's most likely a harmless error from SkellettProxy not being able to connect.
 
Every day , you create like 120 threads to ask help about things that you can easly resolve and do yourself , just testing or using debugs without the real necessary to spam help & bump here.

If in the future you want make something cool and done with your hands , you should start try to use your brain and fix this problems by yourself , without the feed of others.

That's just a suggestion.
 
What do you mean MY CODE? Its a plugin. I didn't make the plugin @LimeGlass Did.

You said this error never happened before. The error is 99% guaranteed to be from your code.

1. What was the last thing you coded before the error showed up? If you know which part of the code it was from, rework it.
2. The error is all from your code if you claim that you never got the error before until recently (without updating plugins).
 
Status
Not open for further replies.