-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database bug #6
Comments
The SQLite data.db does not have cross-server capabilities. Are you sure there are no errors in console related to PunishmentsX at all? |
Yes, all i got was that I've sent, yes I know it's cross-server capabilities, i was using it for single-server use |
I can send you the database, but that would reveal the ip's of my players wouldn't it? |
I don't need the database. My issue is that I'm unable to reproduce the issue based on your steps.
I also tried restarting server 2 and there was still not data loss or bugs/errors. |
I didn't put it on 2 servers, i use a lobby to join my server which is on a bungee server (lobby) that connect to my server, does that makes sense? the only issue I gives is the server, not from the lobby were the plugin is not installed |
Okay, well I am still unable to reproduce any sort of issues arising from switching servers using the bungeecord "/server" command. Do you have any more information that I could use to reproduce the issue? |
I'm not sure what would be helpful to you, it's after they have a punishment it sometimes won't let them join, sometimes it's only when the server restarts (maybe that has to do with something?) |
Nobody else seems to have this issue, and I can't reproduce it. It seems like a problem/incompatibility with your enviroment. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Screenshots
https://gyazo.com/a6729ba8e90c65e65944af82865f071f
Server Information:
Additional information
Add any other information about the problem here.
The problem is fixed whenever I delete the data.db file and restart the server, but that isn't a valid solution if I have to keep doing that...
The text was updated successfully, but these errors were encountered: