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

Non-persistent attributes #529

Closed
2 tasks done
npaton opened this issue Mar 28, 2024 · 0 comments · Fixed by #533
Closed
2 tasks done

Non-persistent attributes #529

npaton opened this issue Mar 28, 2024 · 0 comments · Fixed by #533
Labels
enhancement New feature or request

Comments

@npaton
Copy link
Contributor

npaton commented Mar 28, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem?

For synchronizing high-throughput data, such as mouse events, persistence can be a problem. Yet, it would be nice to have synchronization between players.

Describe the solution you'd like

Maybe an option on set() that would mark the change as non-persistent. E.g.:

player.set("mouse", xy, { ephemeral: true })
player.get("mouse")

This would not be persisted, so it would not find itself in the tajriba file, and the key would be null after a server restart. Otherwise it should work exactly the same as normal attributes. I don't know if we can/should support persistent and ephemeral updates on the same key.

Describe alternatives you've considered

No response

Teachability, Documentation, Adoption, Migration Strategy

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@npaton npaton added the enhancement New feature or request label Mar 28, 2024
@npaton npaton linked a pull request Mar 31, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant