Skip to content
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

error when shutting down the server (purpur) saving data in (velocity) #3330

Closed
sk98q opened this issue Nov 28, 2023 · 4 comments
Closed

error when shutting down the server (purpur) saving data in (velocity) #3330

sk98q opened this issue Nov 28, 2023 · 4 comments
Labels
Bug Issues that contain unintended behavior status: Awaiting Reply Issues that require clarification from the reporter

Comments

@sk98q
Copy link

sk98q commented Nov 28, 2023

Describe the issue

**I was on the server, I had played 39 minutes to the total time. The total time was 50 minutes.

I decided to install another plugin, and the total time flew off when the server was turned off. The player's data was not saved and reset to zero before the previous visits.**

Exceptions & Other Logs

logs clear.

**logs clear. no create - server shutting in button "close"**

Plugin versions

latest

Additional information

server purpur (latest) 1.18.2

plugins:
LP
LiteBans

plugins instal:
essentials.
image (1)

@sk98q sk98q added the Bug Issues that contain unintended behavior label Nov 28, 2023
@AuroraLS3
Copy link
Collaborator

If storing sessions fails during shutdown they're saved next time the server starts - are there any errors during the next enable after shutdown?

@sk98q
Copy link
Author

sk98q commented Nov 30, 2023

If storing sessions fails during shutdown they're saved next time the server starts - are there any errors during the next enable after shutdown?

No errors... Stupidly stable start-up without errors, no data is saved when shut down

@AuroraLS3
Copy link
Collaborator

Did the server that the player was on have Plan installed?

@AuroraLS3
Copy link
Collaborator

Closing as stale

@AuroraLS3 AuroraLS3 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 20, 2024
@AuroraLS3 AuroraLS3 added the status: Awaiting Reply Issues that require clarification from the reporter label Jan 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues that contain unintended behavior status: Awaiting Reply Issues that require clarification from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants