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

Spring Blocks remain in registry regardless of config #31

Open
laceflowermc opened this issue May 5, 2021 · 3 comments
Open

Spring Blocks remain in registry regardless of config #31

laceflowermc opened this issue May 5, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@laceflowermc
Copy link

If the spring block config is changed, the spring block remains registered to the block registry on the server, causing a mismatch when a client without the mod connects, thus being incompatible with vanilla clients.

@lhns
Copy link
Owner

lhns commented May 6, 2021

You are probably using the forge version aren't you?
Because I tested this on fabric and it works pretty well but forge might handle things differently.
I will have to look into that.

@lhns lhns added the bug Something isn't working label May 6, 2021
@lhns
Copy link
Owner

lhns commented May 11, 2021

I tested this and it seems like vanilla clients can connect without a problem to forge or fabric servers running this mod.
It might be that only forge clients that are missing the mod are complaining.

@laceflowermc
Copy link
Author

Sorry, i should've been more specific - yeah, I've only tested on a forge client without the mod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants