Probably OP meant that rubber trees are quite rare even in swamp-like biomes. Just tested it and could not find one anywhere except swamps.
>IC2 is evolving faster than most other mods
Oh, ok, I got it.
Quoted from "bones"
You need a decent power supply almost right after you got your first generator, however, solar panels are too expensive, so the only viable option is nuclear reactor which again requires tons of metal to get at least 20 eu/t.
What about semifluid or geothermal generators? You can always have more than one running in parallel for higher output.
There comes another problem: to cope with reduced storage blocks' intake capacity you'll now have to get a lot of transformers to keep things from exploding. As far as I remember, earlier blocks could withstand a bit more current than they are capable of giving. You could chain several storage blocks _and_ attach other power sources to them without risk of exploding. Maybe I am wrong and that was back in 1.0.
Quoted from "bones"
All this scares off new users who have a lot of other mods as an alternative.
If players want creative in disguise of easymode mods then they can feel free to use those other mods that give it to them.
True, however, lack of new users means slow decrease in mod popularity and, eventually, death.
I'll try to state things more clear. The problem with the new IC2 is that it takes much, much more time to get started. The main reason for this is that demand for resources has rocketed. For instance, now you have to waste 32 diamonds to get MFE opposed to 8 or so (and CESU won't help here). You need a decent power supply almost right after you got your first generator, however, solar panels are too expensive, so the only viable option is nuclear reactor which again requires tons of metal to get at least 20 eu/t. All this scares off new users who have a lot of other mods as an alternative.
tl;dr: the development curve at early stages is too slopping.
Nope, OP has a good point. I have been lurking many communities since last official update and a lot of people claimed they have decided not to use IC2 because its visual side haven't changed much during the last three years.
Still, are there any good map converters? The last one I used to convert from 1.2.5 to 1.4.7 just corrupted the world (I forgot the name but it was some command line based tool).
Optifine doesn't support 4096BlockID's
This. I tried changing IC ore IDs to numbers lower than 255 and it worked! Thank you very much. (It's unclear why Optifine doesn't support high values, though)
I have been modifying DocuCraft texture pack for a while now and noticed what might be a bug.
The colors of certain blocks in Minecraft with Optifine are controlled by colormaps depending on the biome these blocks reside in.
Ore block colors are controlled by stonecolor.png and can be registered in texturepacks in color.properties file.
Here is an extract from it that is supposed to apply stone colormap to vanilla ores and ones generated by Redpower and IC2:
Where, according to NEI dump, 242 is a block holding all RP ores, 688 is Monazit Ore from MFFS IC2 addon and 4093-4095 are ores generated by IC2.
RP blocks seem to work fine, however while minecraft tries to apply these settings to IC2 ores, the following errors appear:Code
- Loading custom colors: /misc/stonecolor.png
- Invalid block index: 688 in palette: palette.block./misc/stonecolor.png
- Invalid block index: 4093 in palette: palette.block./misc/stonecolor.png
- Invalid block index: 4094 in palette: palette.block./misc/stonecolor.png
- Invalid block index: 4095 in palette: palette.block./misc/stonecolor.png
Obviously all ores related to IC2 are only registered _after_ this part, so colormaps do not apply to them (see attached screenshot).
Since RP does not have these problems, there must be some way to register blocks prior to colormap registering.
So my question is if there is a way to solve it (in case my setup is wrong) or include a fix in future updates (in case this is a bug)?
P.S. Of course this can be "fixed" by either disabling custom colors or removing the config line completely, however, such radical measures
don't seem to be a reasonable solution.