Do not leak any informations provided on this page to the Minecraft-Forum website!
Discuss everything in this regard either here or, even better, in the official IC-Forum.
Please ignore everyone discussing/ranting/flaming about this issue in the IC thread withint the Minecraft Forum!
Yes, due to an upcoming project, i will stop the developement of IC, fully and final.
- No more updates
- No bugfixes
- No new content
- No porting to 1.8 or beyond
- Only verbal support for problems until i get bored off it
That was the bad-news part of this blogpost. Now the good one:
I hereby officially announce the developement begin of IC²!
Yes, i’m terribly mean and ignorant to fool you in that way 😛 Don’t worry, Modding Minecraft is a great hobby and i won’t drop IC. However, as noted above, i will stop developing IC and instead create IC².
Anyone with the slightest knowledge of Java+Minecraft-Coding can tell my code sucks. Exspecially the first (chronological) 70% of the mod. This is mainly related to 2 facts: When i startet developing IC, my Java knowledge was quite basic. Now, ~half a year later, i have a (i hope so) better knowledge of Java, can access a much wider array of CPU-green algorythms and got a MUCH better knowing of how Minecraft works. Exspecially beneficial for latter one were my sideprojects MeC (SMP, Client-Server-Communication, Advanced Base-File Modification, Damage/Speed Mechanisms) and M4D (Time Manipulation, Advancd Block Updates, Mobs, SMP-Entitys, AI).
As a result, i’ve decided to completely restructure/recode and review IC’s code, adding more functionality, easier porting/fixing, a couple of APIs, a few new concepts and the already mentioned new sprite-system (limitless). Since a few weeks, a fellow modder is already reworking the Energy-Current-Code. This, combined with a few ideas how to make IC much more advanced, made up my decision.
A list of intended features for IC²:
- Using Scoke’s ItemSprite API and his TerrainHack (or SpaceToads new project API) to reduce/remove the amount of sprite overrides currently setting IC’s bounds.
- Advanced usage of Metadata to reduce the amount of BlockIDs uses (as well as resolving this goddamn MemoryHogger Notch probably isn’t going to fix before 1.9)
- API’s for other modders to integrate IC’s machine operations and Electric Network, by using the ZZuperICElectricAlBI
- New generalized Classes for the machines, making the code much less redundant and easier to alter.
- (Already mentioned,) new Electric Current distribution algorythm
- Rework of many game concepts, f.e. Ore abdundancy, eventually new ores, Fuel mechanics (i will probably try myself on coiding real OIL), and stuff.
- If all above is done and it’s proven to be possible, programmable (within a certain degree) robots and CPUs. Rather, CPUs to program robots. F.e. ones which can construct WindMill farms on certain locations automatically.
- New Policy/Copyrights regarding mods referring to IC, AdFly guidelines and similar stuff.
- A IC-intern banlist preventing users, who previously bugged me too often or plainly pissed me off, from playing IC at all.
- Eventually recruitment of a small coder team to increase IC’s developement speed.
- Some sprite reworks
- A hell-big ton of bugfixes.
You’re free to C&C now.
Again, please do not leak anything of this into the Minecraft forum. If people are too lazy to get over my blog to read this, their bad 😛 Don’t ruin the fun for those people aware of the gag. Even if it’s extremely evil.
Just couldn’t wait until April 1st :/
My new Eternal-IC-BanList already includes 2 persons. I’m of course not going to post a public banlist, but if you want to play IC² somewhen, seriously, don’t rant about it on MCF. As well, bugging me about updating MeC can have same results.
62 Comments and counting XD
We should probably move this discussions into the forum ^^
Recruitment thread : forum.industrial-craft.net