It's a shame this was an April Fools joke. I stopped using IC2 after MC 1.4.7. This would have made me consider using it again. Oh well.
No Asie. Buildcraft should have simply changed their EnergyAPI a bit and everyone would have supported it still..
The main reason why people left was because the API was simply: You have to do it our way and thats it...
If you wanted to make a converter you had to constantly drain the Energy out of the custom battery in the old system to make it work.
A simply IC2 API like thing: Receiver and Sender would have been enough... Switching to RF was the same solution but you got ride of what BC was worth for. Its own uniqe power system with Explosions...
This was a common misconception about the MJ power system (that there always had to be loss and there was no way to avoid it). Yes, the API did have loss built in, and yes you couldn't eliminate that loss entirely on the API part of it, but what you did with the power after receiving it was not something that the MJ API dictated and you could configure the loss at the receiving end to be virtually negligible. It was entirely possible to have a machine that would store massive amounts of MJ, shut off its power requesting, and lose only a small amount of MJ in the transfer buffer.
Very large resource packs like this are a problem in general unless you have 8 or better 16 GB of RAM.
please do not enter players in misleading!
with fastcraft i have 17 fps and freeze every second, without -117+ fps
all good with pack and RAM - only 1800 mb memory usage with 100+ mods
If you are having stellar performance without FastCraft, why are you even trying to use FastPack?
On a related note, is the code in GregTech that invalidates ore dictionary entries (by replacing it with IC2 scrap) that GregTech doesn't use and isn't affected by, but has been deemed invalid going to be removed as well?
In TConstruct's case, the problem was a simple annoyance from excessive logging. Other mods are deliberately broken by GregTech for no good reason other than to force compliance to Greg's standards.
I would use the more logical one that requires less Laggy and tricky code.
The ore dictionary is just a one-to-many map of strings to items. There is no extra lag or tricky code involved. It's just a string.
I just wonder what will happen if a third mod enters the play and decides to add Iron Rods and want to make it oredict compatible. I bet it will follow the standard convention of forge.
I guess it depends on the mod... If they want compatibility with both, it would add both names to the oredict. Personally, I'd use the one that had been in use the longest.
At the end of the day, it boils down to this: GT doesn't care about compatibility with TConstruct, TConstruct doesn't care about compatibility with GT, and mDiyo doesn't particularly care to change the names that he has used for the past 2 years.
Sidenote: As for mDiyo being an unknown developer... You can thank him for block IDs not being limited to 256. He did the 4096 expansion.
Then, Fix it Greg! time.
Chickenbones didn't follow the precedent of forge, which is older than WRCBE or any of his mods, going over with the mistake is just stupidity.
He is not the one that has the right to set any convention, forge does.
Ultimately, these are the names that have been in use by mDiyo since 2011. If GT wants to be compatible, the onus is on Greg.
Follow ONE! ONLY ONE mod... That's not big list of mods which using it... Sorry. 2 mods. even Translocators for his diamondNugget ;D
How about the predecessor to TConstruct, Infitools? That naming convention goes back to beta 1.8. LONG before GT.
BEFORE HIM? Tinkers is how old NOOOOB! Greg - Tech is here idk... 1.2.5?!
This makes me LOT rude!
And Greg dont follow conventions? SO OTHER hundreds and hundreds mods dont follow it too!?
Please dont give me ban, but... You are really STUPID. So blind for your "star TiC" -_-
You know what? If Greg - Tech name it wrong, why only few mods using reverse style...?
Calm down buddy, arguing with anger is going to end nowhere. ~SpwnX
TConstruct followed the precedent set by WRCBE (which was before GT)
I have ONE question, because instead of speculation, why you name your stuff in reverse way? Have it some practical uses? Thnx for answ me
Do you have an instance in particular? It uses ore*, ingot*, and nugget*. The only time it doesn't is with the tool parts (and especially the rods, where the precedent for the reverse order was already set by other mods)
What if i wanted to eat only half hot dog, for whatever reason? Like i want to play with the GregTech nerfs, while TC forced me to eat the whole hotdog.
No one is stopping you from throwing the rest away.
If you explicitely want an Acid Free Hotdog with Ketchup, and I give you a Hotdog with Ketchup and someone else comes and puts additional Acid on the Hotdog, corroding the Ketchup away, after I gave the result to you. And then you complain about getting too much Acid and too less Ketchup, so that I start to refuse (crash) giving Hotdogs out, while that Acid Guy is there, just because I know he puts Acid on it without you wanting that, and I can't easyly prevent that Acid Guy from doing it. That is bad?
Seriously, if you come with senseless comparisions, I answer with even more ridiculous stuff.
Actually, it's more like you explicitly want a hotdog with ketchup, and you give a hotdog with ketchup on half a bun, then someone else comes and replaces the half bun with a whole bun. But then you got angry that someone would dare do that and you take the hotdog and throw it on the ground.
Long fueled by whiners pointless war between Tinker construct and GregTech.
Sum up facts, not going to force you an opinion :
1. Greg added a wood nerf (configurable, enabled by default), reducing planks and sticks yield.
2. mDiyo added an anti-wood nerf (not configurable), returning back the planks yield back to vanilla default.
3. Greg added a code which would cause a MC crash when it detects if any other mod modifies its recipes, thus affecting TiC anti-wood nerf, crashing MC when both are installed together.
4. Many players started complaining about greg's behavior for "radically" responding TiC with a crash, saying that it is unethical, wrong, malware...
5. mDiyo proposed a cease-fire treat, removing the wood nerf, as long greg removed his crash code and anything towards Tinkers Construct.
6. Greg accepted and removed that code, some players still kept previous behavior.
7. mDiyo went a bit back on his word and re-added the anti-wood nerf (now configurable, enabled by default).
8. Greg, while defending himself, readded mDiyo back to the "pumpkin of shame" list.
9. Both Greg and mDiyo asked slowpoke (FTB creator) to make packs which doesn't have them together.
10. Situation is kinda unstable now. FTB seems to be leading to create a "GregTech visioned" pack and another completely out of it. Players are still complaining about gregs behavior.
There are several mDiyo's and Greg's posts here, scattered over 50 pages of useless opinion posts, but i'm too lazy to find them, good luck and try reading by their own words.
You forgot the step where GregTech ignored the wood nerf config if TConstruct was detected.
"people may not believe this, but we were already looking at a redesign of this pack to be closer to the vision of gregtech"
This is gonna hurt sooo many butts out there...
The GregTech oriented pack is going to be GregTech oriented? What will they think of next? Perhaps the non-GregTech oriented pack will not be GregTech oriented? Shocking! Sarcasm!
The Bukkit port of 2.4 has been updated to revision 3, resolving the issues of shift-clicking and the seed manager eating seeds in the filter slot.
Sounds like a corrupt blueprint. Check your blueprints folder for it and remove it.
The 'Circle Stone Brick' block can normally only be acquired in creative
mode, as can two variations of the sandstone block. The alternator
provides a method of obtaining these elusive blocks through normal
Actually, the sandstone variants can be crafted normally. Smooth Sandstone is made by combining 4 sandstone in a square, while Chiseled Sandstone is made by stacking two Sandstone Slabs. See http://www.minecraftwiki.net/wiki/Sandstone