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

feature/projectile-clearing #56

Draft
wants to merge 5 commits into
base: dev
Choose a base branch
from
Draft

Conversation

popstarfreas
Copy link
Owner

@popstarfreas popstarfreas commented Dec 17, 2019

@popstarfreas popstarfreas changed the title feature/projectile clearing feature/projectile-clearing Dec 17, 2019
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") {

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.

Copy link
Owner Author

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.

@popstarfreas popstarfreas force-pushed the feature/projectile-clearing branch from 38a5df8 to f1e139e Compare May 18, 2020 15:47
@popstarfreas
Copy link
Owner Author

Updated for 1.4:
Dimensions-v5.8.3-feature-projectile-clearing.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants