-
-
Notifications
You must be signed in to change notification settings - Fork 480
Fixes #4299 - Isolate Client Resource Cache by Server #4311
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
base: master
Are you sure you want to change the base?
Conversation
…gacy resource migration
I like the idea. |
With the current automatic migration, shared resources will be copied into each server's folder the first time the client connects.
but if he don't have the resource, for sure it will be downloaded |
Will it only be copied after joining for the first time after this update? |
Yes it , it will only be copied once when you join a server for the first time after the update, as the migration only runs if the server's specific path doesn’t already have the file. After that, the resource in each server’s folder is independent, so if a player saves new handlings in one server, those changes will not appear in another server For real example , So, no the player’s handlings will not be shared across servers since each server has it's own directory. But the player could still do it manually by copying the data, or the server could use a database instead of relying on file based settings. |
For: #4299
the implementation includes automatic migration for legacy cached resources, allowing a smooth transition without user interaction or data loss.
While legacy support is currently maintained for backward compatibility, it may be deprecated in the future to simplify the system further. Removing legacy support would reduce maintenance overhead .. but if we didn't implement it for now .. it would require clients to re-download resources when connecting to servers for the first time after the change.