This is a patched version of the Mekanism mod for Minecraft 1.7.10 which was made for the Voltz Community Modpack
Fixes dupe bugs with:
- Bins
- Liquid tanks
- Personal chests
- Factories
- Chemical Washes
- Logistical Sorter
- Digital Miners (2x)
Also fixes:
- Numerous server and client crash bugs
- World protection bypass with flamethrowers
- Significantly improves performance of many mod components
MODPACK PERMISSIONS: Anyone is free to use this mod in their modpack ON CURSEFORGE provided that it is not related to Voltz, Volts, or the mod list is similar to that of the Voltz Community Modpack and credit is provided by linking to this page. Usage on any platforms other than CurseForge is strictly prohibited without prior direct written permission from me.
Can you maybe fix this ?
You cant see the water behind the Tank
https://www.dropbox.com/s/62tg0utv96r8ldm/2020-01-23_17.48.43.png?dl=0
I have discovered a crash with the induction multiblock. Basically it goes:
It will not crash again until you modify the size of the multiblock again. The crash error varies depending on which block you right clicked to place the port (casing will show the cell error, provider or the cell).
Crash Reports
PS. Using latest version kmecpp v3
My Game keep crashing when I try to create a new world with the newest version.
crash report:
https://www.dropbox.com/s/1qqklykkynp761y/crash-2019-11-04_18.17.45-client.txt?dl=0
In reply to Gandalf360one:
Could you resend the crash report?
In reply to kmecpp:
Actually never mind I think this should be fixed now
Looks like something in this version makes fluids not render in tanks or pipes.
In reply to subtlesubtitle55862:
Sounds like another mod causing the issue or some graphics settings screwed up. If you replace it with the latest official version of mekanism for 1.7.10 does it start working?
In reply to kmecpp:
I just made a test instance with nothing but this fork and the issue remained (enabling or disabling Optifine didn't change anything either), but using the official Mekanism version instead on the same map rendered fluids without issue.
In reply to subtlesubtitle:
This issue has been fixed in the latest version
What patches were added in?
In reply to Spanner_Man:
In reply to kmecpp:
In reply to Spanner_Man:
In reply to kmecpp:
So you're fixing bugs in Mekanism for 1.7.10, placing it publicly on curseforge where anyone can find it, yet you want to be the only person who can use it in a modpack?
If this is more stable than the other version on curseforge you should be encouraging people to use it in their modpacks...
I mean it's great that you're patching bugs in an unsupported version of a mod, but you don't get to change distribution rights.
If I were to add this project to a modpack, it wouldn't be me 'stealing your patches for my competing modpack', it would be me using a more stable version of mekanism.
In reply to BBoldt:
My apologies if the description was unclear. My intention was never to try and change the distribution rights of the Mekanism mod. I do however own the changes which I made to the mod and I can control how people are allowed to distribute those.
As a side note, aidancybrady is using a modified version of the MIT license which clearly excludes the clause which requires redistribution of the original code under the same license so I'm pretty sure I can do basically whatever I want with the code.
Assuming that all of what I said above is actually true, then anyone is free to use this mod in their modpack provided that it is not related to Voltz, Volts, or the mod list is extremely similar to my modpack.
If I can confirm that it is true, I will also probably upload the fully patched and performance optimized version of the mod I'm using on my server. This version only has about 1/3 of the total fixes.
Also the only reason I put this on curseforge is because I changed the mod version so players wouldn't be able to connect to my server with a normal client.
In reply to kmecpp:
I legitimately don't think you have the right (on this website) to control who uses your fork of the mod or not. It can be added to or distributed with any modpack on curseforge regardless of what you say or do with the license, that's just how curseforge works.
Just an FYI.
I mean, you can ask nicely that people don't use it if they have a similar modpack but there is no way to enforce that other than removing the mod entirely, as far as I know.
Take a look at Millenaire, they have all rights reserved and special modpack requirements, but as you can see nobody cares:
https://minecraft.curseforge.com/projects/millenaire/relations/dependents
You're right that you can pretty much do anything with the code and future licensing. It's just that you've given curseforge blanket permission to distribute by uploading it here.
In reply to BBoldt:
It's quite possible curse's user agreement overrides whatever claims I made in my previous comment on their platform. However, I find it hard to believe curse has rules against strict mod licenses considering they allow you to chose "All Rights Reserved" and such for your projects.
For your Millenaire example, I would make the argument that all the requirements they have specified are satisfied immediately simply by using the mod on the curse platform. Links to the Millenaire mod and the mod authors are created automatically in the dependencies section so the credit I think is given here. The other requirements are somewhat more vague but I think if anyone was had a modpack and was falsely claiming have to created the Millenaire mod then curse would take it down specifically because it violated the mod license.
In reply to BBoldt:
In reply to kmecpp:
Hmm, not quite sure what a sublicensee is referring to in this excerpt but it seems like Twitch might just let people do whatever the hell they want.
Although I know curse has their own rules but I'm not quite sure where that would be.
In reply to BBoldt:
Note quite,
The MIT license is not copyleft. So the source does not need to be distributed, any requests for the source can be ignored. https://opensource.org/licenses/MIT
While "technically" you are correct BBoldt, stating all rights reserved isn't correct as the project must state that parts of the project are MIT - for which is covered in the project description. That part is a failure on Curse itself, not allowing for proper license attribution options.
"Generally" mod devs want people to use their code (mod), to enjoy the changes and so forth. Otherwise they just wouldn't do it to start with. I've seen projects state an all rights reserved with a modpack allowance clause right in the project description too.
Mod devs in general only want the following;
And sometimes - let them know so they can see how your using it - I've had a couple of mod devs even play with my pack and enjoyed the config & minetweaked changes made.