[SOLVED] Reika's mods older version releases
- Thread starter AlCapella
- Start date
Just fix them, it's really not that difficult
Go into the Rotarycraft config and change the "Freeze Potion ID" to 90, it worked for me. I think there were 1 or 2 more conflicts, but they were nothing too big. If you want the older versions, download the older versions of the Monster pack and copy over the files from there.Still, why would someone not offer older versions?Just fix them, it's really not that difficult
So they don't get constant complaints about bugs that were already fixed in the latest version?
Which is why I dislike peopleWell people still do that
Yes, I was trying to configure an oldschool style manual mod pack and the inability to find previous versions conflicted with the custom config provided.
While it is rather simple to fix, I can see how you might not want to bugger around with configs. But it's modded Minecraft, you sort of should learn this stuff if you want maximum enjoyment.
Try and load your pack instance without any of Reikas mods make a throw away world (unless you don't car about world gen) and perform an item dump with NEI to see some free ID's. You can just change the potion ID mentioned to whatever but doing the dump first is a measure twice cut once dealy.
Also word of warning; If you ask anything of Reika, make damn sure you have good cause to ask lest she throw you in to an operational fusion powered turbine...
While it is rather simple to fix, I can see how you might not want to bugger around with configs. But it's modded Minecraft, you sort of should learn this stuff if you want maximum enjoyment.
Try and load your pack instance without any of Reikas mods make a throw away world (unless you don't car about world gen) and perform an item dump with NEI to see some free ID's. You can just change the potion ID mentioned to whatever but doing the dump first is a measure twice cut once dealy.
Also word of warning; If you ask anything of Reika, make damn sure you have good cause to ask lest she throw you in to an operational fusion powered turbine...
Considering the first thing Reika says when a bug is reported is "get the latest version", I can't imagine he'd ever want to voluntarily host known bad files.
Also, that potion conflict goes back at least a version or two.
Honestly, he rolls out content on an extremely frequent basis, and a lot of it is bugfixes to varying degrees of severity; you're never doing yourself a favour by back-versioning
Also, that potion conflict goes back at least a version or two.
Honestly, he rolls out content on an extremely frequent basis, and a lot of it is bugfixes to varying degrees of severity; you're never doing yourself a favour by back-versioning
This tickles me particularly since he gets at least a bit annoyed when folks refer to him as "she".
Considering the first thing Reika says when a bug is reported is "get the latest version", I can't imagine he'd ever want to voluntarily host known bad files.
Also, that potion conflict goes back at least a version or two.
Honestly, he rolls out content on an extremely frequent basis, and a lot of it is bugfixes to varying degrees of severity; you're never doing yourself a favour by back-versioning
This tickles me particularly since he gets at least a bit annoyed when folks refer to him as "she".
Wait what? I remember seeing a post stating the exact opposite?
I'm confuzzled...
Thanks to everyone that replied. The replies were interesting at several levels for me.
I'm new to "Reika's way of doing things" , so the comments were, let's say equal parts entertaining to me.
Most, if not all mod authors offer a few earlier releases of their mods. Granted, some do, and some don't. But if the mods are fairly big ones, and if the release cycles are staggered close to each other, it feels like a good practice to leave at least two earlier builds, as a means for people to switch one release behind (cf., calclavia?) in the eventuality of major issues cropping up in existing worlds. It's not some kind of sacrilege either to ask why there aren't at least two earlier releases as a fallback option - at least with massive mods.
Sure, I saw the crash log and the said conflicting ID, and I do know it is a matter of "I has hax0rzzz" with config files until things work. Many thanks for that angle.
Partly my fault for not writing this earlier as it may have avoided this small tangent the thread took, but it was an ungodly hour at my end, I was tired, and meh....
The other big reason for wanting to have an earlier release of the mod is for another reason too. There can also be mod interaction issues due to which people might want to revert back to an earlier version in order to confirm this. In this case, specifically, the minimap loses colour when using V22. On the MCF threads, people mentioning that V21 doesn't give them this problem. So, there's that reason for wanting an earlier release. To keep the mods playing nicely with each other until a few releases when interactivity bugs get ironed out peacefully.
P.S: Monster ships with V19.
I'm new to "Reika's way of doing things" , so the comments were, let's say equal parts entertaining to me.
Most, if not all mod authors offer a few earlier releases of their mods. Granted, some do, and some don't. But if the mods are fairly big ones, and if the release cycles are staggered close to each other, it feels like a good practice to leave at least two earlier builds, as a means for people to switch one release behind (cf., calclavia?) in the eventuality of major issues cropping up in existing worlds. It's not some kind of sacrilege either to ask why there aren't at least two earlier releases as a fallback option - at least with massive mods.
Sure, I saw the crash log and the said conflicting ID, and I do know it is a matter of "I has hax0rzzz" with config files until things work. Many thanks for that angle.
Partly my fault for not writing this earlier as it may have avoided this small tangent the thread took, but it was an ungodly hour at my end, I was tired, and meh....
The other big reason for wanting to have an earlier release of the mod is for another reason too. There can also be mod interaction issues due to which people might want to revert back to an earlier version in order to confirm this. In this case, specifically, the minimap loses colour when using V22. On the MCF threads, people mentioning that V21 doesn't give them this problem. So, there's that reason for wanting an earlier release. To keep the mods playing nicely with each other until a few releases when interactivity bugs get ironed out peacefully.
P.S: Monster ships with V19.
when I'm upgrading mods inside of a pack I'm using, I make a backup copy of the entire instance to revert to just in case something like this happens.
I do not even keep old copies of the mod, so even if I wanted to offer old versions - which I do not, for the reasons given above - I cannot.
[first, goes through the obligatory five stages]
[then edits the thread title]
Can anyone please offer me a link to V21 of dye trees? I want to try something out at my end.
Thanks in advance.
You did not read my last post? It is not just the ID conflict why I started this thread.
My minimap colours and GUI are shot. And it is V22. V21 is supposed to be behaving well with the map mods. I want to see if that's so, and confirm from my end.