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

Global control of client-movement #127

Closed
wants to merge 1 commit into from
Closed

Conversation

mmontone
Copy link
Contributor

Hi.

I would like to control global value of client-movement using a global variable as default that can be changed to switch between client/server movement when it has not been explicitly specified.

Do you agree?

@rabbibotton
Copy link
Owner

rabbibotton commented May 10, 2022 via email

@mmontone
Copy link
Contributor Author

mmontone commented May 10, 2022 via email

@rabbibotton
Copy link
Owner

rabbibotton commented May 10, 2022 via email

@mmontone
Copy link
Contributor Author

mmontone commented May 10, 2022 via email

@rabbibotton
Copy link
Owner

A may consider adding a global to one of the tutorials, but I don't think it makes sense to change the framework. The only reason for changing to start with is to moderate network traffic or add responsiveness on slow networks and I think those type of changes should be thought out on a window by window basis.

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