- #Minecraft sp viper squad 1.10 mod#
- #Minecraft sp viper squad 1.10 update#
- #Minecraft sp viper squad 1.10 mods#
#Minecraft sp viper squad 1.10 mods#
When implemented this way, not all mods are forced to switch at once. If that isn't currently possible, I'd say it's worth making it possible in upstream Forge, given the huge potential gains.
#Minecraft sp viper squad 1.10 mod#
I don't know if it's currently possible in Forge to hook into the module loading process itself, be it as coremod or otherwise, but if so, it should be possible to write this functionality as a mod that'll handle the loading/caching of all other mods. "But SharkWipf, wouldn't that require a massive rework of the entire mod loading process and all mods?"
#Minecraft sp viper squad 1.10 update#
Checking if a config file has changed, or if an update is available, and invalidating the cache could/should be handled by a single system for all mods. Loaded blocks/items/hooks are the same every launch (if the config doesn't change).Īdditional downloaded libraries generally won't magically disappear.Īll of the above could be cached, and should make loading/initializing almost instant. As far as I can see, 90% of the initialization done during mod loading gives exactly the same results each time you start the client: Even if each mod would take "only" 1 second to load, it'd take 1.5 minutes for the client to finish loading mods. The new Direwolf20 modpack has, according to Curse, 71 mods. For some mods, this process takes 15+ seconds on a high-end machine, every time you launch the client. to the client, and generates everything it needs to generate. Each mod then proceeds with its initialization, adds their hooks, blocks, items, etc. From what I understand, each time you launch the client, it'll go through several stages of loading each mod. Especially with the amount of crashes modded Minecraft brings, this is a pretty big issue IMO. 15+ minutes to launch a pack on fairly high-end hardware isn't uncommon. Issue #1: Loading time The next most obvious issue would be the ridiculous loading times of bigger modpacks. Foamfix in particular helps a lot with the most obvious problem, the ridiculous RAM usage. Some of these issues have been (partially) tackled already, luckily, thanks to mods like Optifine and Fastcraft and the newcomer, Foamfix. However, as far as I can see there's a good number of huge performance bottlenecks that have been pretty much unchanged since day 1, and in my (admittedly fairly limited) view seem relatively easy to tackle, given the performance gains it'd bring.
Sure, this is mostly because we keep getting more and more great mods, and mods become more and more complex. Yet, somehow, it seems the performance of modded Minecraft is only getting worse, whereas Vanilla performance keeps getting better. Forge (& predecessors) have been around for almost as long. Minecraft has been around for a good 7 years now. Disclaimer: I am not a mod developer, I have some outdated Java knowledge, I'm a medior Linux sysadmin and back-end webdeveloper, and have run several modded Minecraft servers, so while I do have some technical background I don't know the exact ins and outs of Minecraft modding.