loot tabe is not shared.
loot for bonus, stronghold and village are different sets.
gone working on redstone machines
loot tabe is not shared.
loot for bonus, stronghold and village are different sets.
gone working on redstone machines
referencing memory otside of application heap cause access violation runtime error without any chance to fix, windows will shutdown application.
for java, something "random" may happen for volatile+weak referenced objects, since they may be garbaged and may be still alive at same time Schrödinger's object hayo, all other options not actually random.
great job.
NEI issue, remove NEI + core and try again.
QuoteUse GIT differently from how you're using it right now (~Alb). It has the wonderful option to create as many branches
are you kidding?
everything you stated valid for github (and any other public source tracker, ever for google docs).
multiple fields and methods are changed in forge 299, addons will work fine with 107 as long as they can work under forge 300+
for one who dont know how to get latest forge:
http://files.minecraftforge.net/
for expected bugs related to "failed to read red text", it will throw nosuchfield errors on load.
QuoteThis didn't really happen, he seemed against your bug fix posting, but that was only because it was done without permission on a closed source project, and I wouldn't consider it at the "DON'T MAKE MODS" all caps level you claim it was done at.
Main argument was "it's not open source you cant edit it", well, i have no time and money for english gramma (and wont use google translate), my entire post was about "closed source does not mean that you can't edit".
And open source does not mean that everyone will steal code.
Quotebut if the source was just handed out to random people with little coding experience, how many quality addons or improvements would honestly result from this?
cant find any reimplementation of BC, NEI or FORGE, reason is simple - nobody cares, ever with source none will attempt to change author and upload mod somewhere (actually there are idiots that do it, but this can't harm popular mod).
Other side - wave of super fast bug fixing at moment of source publishment WONT HAPPEN, it wont happen at all, one with proper skills to fix *obfuscated* 3rd party mod wont waste his time on 3rd party mod and will make his own.
One without skills to run MCP wont have a chance to fix anything ever with fully documented source.
Quoteallow any kind of flithy paws into their code
QuoteBecause alblaka isn't mojang? and Ic2 isn't minecraft either.
you just like ic2 devs in general - ignoring whatever posted on forum, taking only your own opinion in account there is nothing to duscuss with you.
but ok, i will still discuss, lets talk about:
I dont see comments like "IT'S NOT OPEN SOURCE GTFO BITCH DONT MAKE MODS" on www.minecraftforum.net, OMG WHY THEY EDIT MINECRAFT??? THEY NOT ALLOWED, IT'S NOT OPENSOURCE!!!
I dont see similar posts on forge forums.
I dont see anything similar on bukkit forum (ofc *you* dont know, but bukkit team distribute SOURCE of minecraft from github) (in case of ButtHurt take this https://github.com/Bukkit/mc-dev)
well, conclude, you failed and by flithy paws are ok.
for everyone else, it's not RP2 discussion.
Just post untested buggy version *somewhere* and community will polish it well.
post fixes classes somewhere
@ Alblaka
Rejecting community help as you doing over manymany versions is not good, actually ifs FUCKING FRUSTRATING when *you* ignore community bugreport or fixes and release mod with SAME FUCKING BUGS.
After some instances of this your wont have any community fixes, just like decompilation patches died.
No source? ah yes, it cost me 40 minutes per version to manually setup everything, not too much, but still i can use this time on blackjack and hookers or fixing another bug or my own hobby.
Also dont expect any "passing around guru" who will fix random bugs inside your code without posting source on github.
no hotfixes - !!!ITS DAMN HAYO FUN TO KEEP CRASHING QUANTUM HELMET IN CODE AND GRAVEYARDING THREAD WITH FIX TO IT HAYO!!!
or LETS NINJA FIX MOD WITHOUT TELLING ANYONE
or LETS DEFINE BUG AS FEATURE AND FIX NEXT VERSION ANYWAY
or LETS TELL EVERYONE THAT BUG IS FIXED BUT WONT POST FIX FOR 2 MONTH
you completely dont understant what opensource is, this is not option for unlimited amount of users to steal your precious;
this is option for you to use unlimited workforce to develop your mod, and only you will have power to choose what fixes to accept
BUT if you continue what you doing currently opernsource platform will cause mod highjack, rejecting community fixes will lead to situation, when forks are better then base and users will switch from slow updating buggy base version to some fork, that accept community input, dont ignore bug reports and provide hotfixes.
you shoudnot ignore deprecation warnings, it's for a reason.
http://stackoverflow.com/quest…tring-and-return-a-number
such way is much more better, also some constant override operators to overrive cost of item-armor-stuff will allow full control over calculation.
drag files into jar and replace, this is not addon or separate mod.
custom smelting work fine in 106, atleast this. recipe displayed correctly.
NEI plugin already included into IC2.