Hey all. v7 has been pushed.
After many months of planning, implementing, and fixing (oh, the fixing), I performed the great merge of 320 commits into the master branch. I hope you enjoy the:
- 1.7.10 update, which involved a complete rewrite of the networking code.
- Efficiency improvements, which should allow Mekanism to perform much faster on both clients and servers.
- Portable Tanks, which I will (hopefully) be making a video on tomorrow.
- Filter Cards, which let you save and swap filter data of Logistical Sorters and Digital Miners.
- Seismic Vibrator and Seismic Reader, which let you explore layers under the surface without the hassle of picking up a pickaxe.
- Salt Blocks, which make higher-tier ore processing slightly easier (and spawn kinda like clay does).
- Fluidic Plenisher, which is the ever-hyped “opposite of a pump.”
- Pressurized Reaction Chamber, which will be easier to use if you have installed NEI.
- Glow Panels, which will, quite simply, brighten (and colorize!) your day.
- Material and Mod ID Filters, which give Digital Mining and Logistical Sorting entirely new experiences.
- Plastic Decoration Blocks, which I promise won’t pollute your oceans!
There’s a lot more to this update as well, but I’ll let you see it for yourself. In the meantime, I’m busy coding flamethrowers for Mekanism v8.
This week has been a week of fixes (and a little content as well).
Last week I mentioned that there were two main caveats of the current Mekanism 1.7 build – the first being the strange rendering of cables, and the second being the temporary removal of NEI. Both of these issues ended up turning into hours of troubleshooting for me, which I will detail below.
Strange Rendering of Cables
Look at this.
That doesn’t look right, does it? Something is…off. Like the entire model is inside out. Or like the textures are all flipped. Yeah, it turns out this is a known issue in 1.7.2, and was fixed in 1.7.4 (like I mentioned before).
Anyway, I spoke to ChickenBones about this, and we ended up finding a workaround that involved using his library to take a two faced copy of the model and render both at the same time. Not very efficient, but it works for now.
Removal of NEI
There’s a bit more too this than “it wasn’t ready yet.” I wasn’t able to get the build script to run properly with the latest Forge and NEI installed, so I was putting this off until I updated.
Well, upon updating Forge, the script failed, stating that it was unable to reference some classes that were added with the new simpleimpl Netty wrapper system. After troubleshooting on the #ForgeGradle IRC channel for a solid two hours or so, I was about ready to give up. That’s when I realized that the log only was spitting out this error for 8 out of my 26 packet classes, and I found that there was a pattern – the error only occurred on my packet classes that had enums nested inside. In other words, I found a bug with the javac compiler. Probably the strangest issue I’ve ever encountered, and I’m going to report it to Oracle as soon as I get a chance. I fixed the issue by taking the enums out of the nested classes.
With the fixes of these two issues, 1.7 is now technically more stable than the current 1.6 branch – this means that a release will be pretty soon. I also have a few new features in the works :)
Hope you all are enjoying the summer, I sure am.
It’s been almost four months since my last post here. I’m actually kind of disappointed in myself.
As most of you all know, Forge has been updated to 1.7.2 for quite some time now, and ChickenBones managed to update NEI, Forge Multipart and his other libraries as well. Apparently 1.7.10 is already on the way, however, which means quite a bit of work is still to be done. I seriously am debating whether or not it’s worth it to update to 1.7 at all.
Well, debated. I decided to update anyway.
I just fixed the Jenkins server, so a working Mekanism build for 1.7.2 has been pushed to all premium users. There are currently two major issues with the version – the first being strange rendering of cables (which is actually fixed in Minecraft 1.7.4), and the second being the temporary removal of the NEI module until I fix it. I plan on having a recommended 1.7 build pushed out once Forge decides to update to the latest Minecraft version (which may be 1.7.11 pretty soon).
Aside from 1.7 news, I have also just pushed the final release for 1.6.4 – Mekanism v6.0.5 – which includes all the fixes present in the development branch (as well as a few additional performance enhancements). It is the new recommended build and is available now on the download page.
Thanks to all of you for a successful release – I’ve had record download counts over the past few days.
There have been quite a few issues with this update, though, some being transition issues and others being outright bugs. I’m working my best to clear out the brunt of the issues on my end, but there’s really not much I can do in terms of transitioning. I thought I’d make a blog post that goes over all the primary changes.
- All transmitters – Universal Cables, Mechanical Pipes, Logistical Transporters and Pressurized Tubes – will disappear. This is due to the recoding of the transmitter system to work with Forge Multipart (FMP).
- Electrolytic Separators will disappear. This has needed to happen for a while – they have been merged into the core Mekanism module.
- Clumps, Ingots, Dirty Dusts, and Dusts will screw up. As pointed out by Hephinator, all of these items had unnecessary -256 shifts on their IDs. The v6 update removes this shift, meaning any of these items you had will suddenly have different IDs. This can be fixed by bumping up the IDs of the items in the config file by 256.
- FMP is now required, and will auto-download.
- MekanismInduction has been removed and is no longer supported. If you used any of the induction features, you may download Calclavia’s version.
Aside from this, make sure you’ve cleared out any conflicts with the other items v6 introduces. I hope this is helpful to some of you, and I’m sorry I didn’t make this sooner!
…has been released.
Yes, it’s true. After months and months of development, testing, and stressing of new features, the day has come. Those on the #mekanism IRC channel got to witness the great cluster of over 500 commits stream over the chat log.
With the update, Mekanism now has an official wiki which is being hosted through IndieWikis. This website and the build server is also now being generously hosted through Mastergalen, IndieWikis’ founder.
Some of you have probably experienced issues with the build server over the past day or two. This is completely my fault and is due to the great move to the new host. Clearing up a few confusions:
- Mekanism is, and will remain, free. Several of you thought I was going to begin charging for new releases since the main download links led to a login page on the build server. This was due to an issue with permissions, and has since been fixed.
- Mekanism’s primary build server is going to remain open. I was considering locking down the main Jenkins build server and requiring users to go through this site’s download page, but I changed my mind. If you prefer Jenkins, you can use Jenkins :)
- Development builds will be closed in the next few days. This is for several reasons, specifically that I do not want bug reports to pop up from non-testers who encounter issues with knowingly unstable builds. After all, without restricted beta access there would be no hype with the coming of new features! However, once it goes private, primary testers (you know who you are) will be given access. Users with premium memberships will still be able to access the dev builds.
- Mekanism v7 is already in the works. Yes, you heard me right.
If you have any questions or concerns regarding this release, feel free to leave me a PM over IRC or pass me an email. All bug reports go straight to GitHub.
Enjoy, and let me know what contraptions you come up with :)
As many of you know, I am in the process of overhauling and adding new content to Mekanism for the v6 release. I am really happy to say that the content is coming together very smoothly, and a release is looking pretty imminent.
One major question I’ve been asked is my plan for it’s release in 1.6.4 or in 1.7.4. I’ll go ahead and say that I originally planned on a 1.6 debut, but a few things are making me reconsider. Believe it or not, it really comes up to you all whether or not you want a release. I’ll go ahead and list the drawbacks I’ve been considering.
1. New Content
Mekanism v6 already features a ton of new features, including new Digital Miner additions, overhauled transmitter mechanics, tiered Universal Cables, 4x ore processing, scuba gear and general stability improvements and enhancements. Believe it or not, however, we still have some content in planning. We could certainly release now and add the new content later, but I have to say that the stuff we’re working on would work very well with the content already added in the new update.
2. World Transitioning
With the new content we’ve added, we’ve had to make several necessary core changes that will make some content inaccessible in the next version. As there will be a necessary world reboot when transitioning Minecraft version 1.7, it makes me want to wait until the port until I release the content. Below is a list of the content that will be changed in the next release.
- Electrolytic Separators have been merged into the Core module, and this means that all Electrolytic Separators previously existent in your world will no longer exist. We’ve added in a bunch of checks so that there will be no chunk corruption or any world damage as a result, but the fact is that all your separators will be gone :(
- Transmitters have been completely, COMPLETELY overhauled by this update. I mean it – everything has been rewritten from scratch to both be extremely efficient and work seamlessly with FMP. The FMP transition, however, means that all old transmitters that you have in your world will no longer exist. This means that Universal Cables, Mechanical Pipes, Logistical Transporters and Pressurized Tubes will disappear once you update. Once again, there won’t be any corruption, but you’re gonna lose a lot of stuff if you grew fond of Mekanism’s transmitters.
I’m sure this news won’t be too pleasant to those of you who were previously eager to update. Let me know what you think, though, if enough of you are willing to sacrifice a few resources to remake the changed content, I may begin finalizing for a 1.6.4 release. Leave a comment here or let me know on IRC (#mekanism, irc.esper.net)!
As many of you already know, Mekanism is no longer hosted on universalelectricity.com (as it has been for the past year now). Since I have decided to drop UE support for the next primary release of Mekanism, Calclavia thought it would be best that I purchase my own host. So far, I’m really happy he suggested that – I’m loving my new site! :)
I’ve purchased GoDaddy hosting and installed WordPress to start; so far it has been a very smooth process of getting it set up. Jenkins hosting will soon be moved, and before long everything will be completely transitioned over. I’m hoping I can get a wiki started at some point as I think the lack of documentation has been what holds Mekanism down the most. My hope is that this website will be a public repository of all my software, as well as somewhere that I can make a blog post now and then.
Since I have this blog now, I guess I should publicly clarify a few things, specifically all the confusion surrounding Mekanism’s drop of UE. As a user, this will not matter at all to you. You will literally not experience any change with UE not in use, as Mekanism uses it’s own universal framework 100% of the time when it is processing foreign energy transfer. The only difference is that I now have to worry about integration with one less API, which is a very good thing. Don’t worry!
Aside from all this, my brilliant co-developer (unpairedbracket) and I have some awesome stuff in development for the release of Mekanism v6, which is just around the corner. Can’t wait to see some people messing around with it once it’s ready.
Happy new years, everyone!