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

feat: remove MAX_PLAYER limit for networked games #407

Merged

Conversation

dignifiedquire
Copy link
Contributor

@dignifiedquire dignifiedquire commented Jun 1, 2024

Naive pass at removing the max player limit. I haven't thought all parts through, but putting this here for a first round of feedback.

Closes #298

@dignifiedquire dignifiedquire marked this pull request as ready for review June 1, 2024 17:44
@MaxCWhitehead
Copy link
Collaborator

@dignifiedquire Change here looks good, thank you!

I expect this will break compilation of jumpy due to API changes. Usually when making changes to bones that will break dependents (just Jumpy atm) will open a PR on jumpy too with relevant adjustments so if update bones version in cargo.lock won't have extra stuff to chase down to get it running.

@MaxCWhitehead MaxCWhitehead merged commit 6a55dc2 into fishfolk:main Jul 3, 2024
10 checks passed
MaxCWhitehead added a commit to fishfolk/jumpy that referenced this pull request Jul 4, 2024
matching PR to fishfolk/bones#407

---------

Co-authored-by: Max Whitehead <max.blackllama.alt3@gmail.com>
@dignifiedquire dignifiedquire deleted the feat-remove-player-limit branch July 4, 2024 10:15
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.

Remove this limitation on max players, a variety of types use this for static arrays,
2 participants