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

fix sumo #10

Merged
merged 1 commit into from Apr 13, 2022
Merged

fix sumo #10

merged 1 commit into from Apr 13, 2022

Conversation

MicrocontrollersDev
Copy link
Collaborator

Description

This is probably extremely inefficient but it was the only way I was able to get it to work. RenderWorldLastEvent fires every tick or something, which was what was screwing me over in the beginning as I didn't know it did that. I added a check to only do stuff on the first fire. The old implementation also meant that it was impossible to change render distance at all. This has been fixed so that resetting render distance only happens if you have just come out of sumo. I also tested directly queueing another sumo after the first one ends and saw no problems there, so this shouldn't cause any issues.

The only possible issues I can think of are Alt-F4'ing the game while in a sumo match or getting the bug where Minecraft sometimes doesn't save changes if you leave the game quickly afterward.

Also, I added some more stuff to Game Tips Hider.

@MicrocontrollersDev
Copy link
Collaborator Author

going to merge, it worked fine in testing and it can be altered later, especially after testing

@MicrocontrollersDev MicrocontrollersDev merged commit 154bfcd into master Apr 13, 2022
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.

None yet

1 participant