-
Notifications
You must be signed in to change notification settings - Fork 16
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
feature/projectile-clearing #56
base: dev
Are you sure you want to change the base?
Conversation
if (projectileSync.enabled && (projectileSync.when === "always" || this.currentServer.isSSC)) { | ||
const projectileIds = Array.from(this.currentServer.client.projectileTracking.keys()) | ||
projectileIds.forEach(projectileId => { | ||
if (projectileSync.type === "clear") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be more efficient to pull this if
higher, maybe even merge with the previous if
.
Unless you want to, eventually, do something with the projectiles outside the clear case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's another case "keep" that will be used for the opposite of clearing, which will update the server with the current client projectiles. Not sure whether this should be the default yet if not clearing.
38a5df8
to
f1e139e
Compare
Updated for 1.4: |
Test Release: Dimensions-v5.8.0-beta.0.zip