2 ms·
The main thing I’ve run into is that you can’t build the project anymore. This is especially common, for example, if you want to revive the source of a Minecra
by bombcar 3y ago
The main thing I’ve run into is that you can’t build the project anymore.
This is especially common, for example, if you want to revive the source of a Minecraft 1.7.10 mod, say.
As more and more code build scripts pull in external things, the harder it is to get them running again years later.
- criley2 3y agoIs that actually challenging? My MC launcher can pull in 1.7.10, add a mod loader, and load mods into it just fine. Do you mean if you try to run a 1.7.10 mod in a modern MC version? That's not a realistic goal because of dramatic API changes between versions. There are a number of breaking versions that require basically rewriting mods. But you can still play the on the old version and most modded minecraft players are many breaking versions behind by default. This is the norm in most games, where game updates are routinely expected to break all backwards compatibility. And considering modding minecraft has never been officially supported, it's surprising it works as well as it does. I'm playing a 1.7.10 pack lately actually, still just as good as when it came out!
- fao_ 3y agoEh? The poster clearly said: > if you want to revive the source of a Minecraft 1.7.10 mod i.e. if you want to change/alter or recompile a mod for version 1.7.10 None of the things you have mentioned apply to this.
- bombcar 3y agoExactly. You can easily find compiled 1.7.10 mods everywhere, and even the source, but getting the source to build requires some work: https://github.com/GTNewHorizons/ExampleMod1.7.10 https://github.com/GTNewHorizons/ExampleMod1.7.10