-
Notifications
You must be signed in to change notification settings - Fork 3
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
Mod Request: Recipe Cache #38
Comments
I actually took a look at that mod last night, but when I looked at the code it was really poorly made. The code is entirely Mixins with no helpers or anything. I'm leaving this open as I can't confirm nor deny that this has any performance benefits, so if possible, I'd like to see some numbers from either the creator or any user. |
Yeah, I didn't have a lot of basis for the performance benfits of this mod, so I didn't know whether it would be classed as an optimization mod. |
The developer even left a remapped jar in their GitLab repo 😂 |
I used this mod, and it seems to reduce networking overhead on servers and there seem to be fewer fps drops in singleplayer when opening a crafting table or furnace over and over (on my pc anyway - which isn't a great benchmark, seeing as the parts are nearing to a decade old). |
Requirements for a mod to be added:
Mod name: Recipe Cache
Type of mod (e.g. rendering, lighting, extra): ticking optimization (crafting tables and furnaces)
Repository (e.g. GitHub, GitLab, Gitea): https://gitlab.com/biom4st3r/optimizedcrafting
Developer/organization: biome4st3r
Additional notes:
This mod seems like it does the same as fastbench and fastfurnace, but is actively maintained. It also has less bugs from fastfurnace, and acts as both mods in one. However, I haven't tested this mod extensively myself, so I don't know if it offers significant performance benefits on servers. I also found a bug myself in fastbench - using it on an online server made the items I crafted invisible - this isn't in recipecache, so perhaps it's a better alternative?
The text was updated successfully, but these errors were encountered: