Posts by Chocohead

With it set to the following it should all work correctly.

; Maximum amount of chunks to check for retrogen viability each tick.
; Retrogen is the retroactive generation of terrain features, e.g. ores and trees.
; Set it to 0 to disable retrogen.
; When enabling this the recommended value is 16
retrogenCheckLimit = 16




; Maximum amount of chunks to process for retrogen each tick.
; Values exceeding retrogenCheckLimit are being truncated.
retrogenUpdateLimit = 2

You can leave it on too, it will only regenerate a chunk once.

It should be all fixed now.

I read them a few hours after you first posted them, but was too busy at the time to look any further. Bugs reports will always be read by at least one person, and strictly they should be changed to go orange and be acknowledged, or yellow if it's confirmed. It can be a hassle to do that though, so often they'll stay red until someone gets around to fix them.

How hard they are to fix is often connected to how long they go unfixed, if it's not an immediate game breaking bug (like crashing placing down a macerator for example), annoying/complicated bugs will be left longer as it's much harder to fix them. In your cases though, I think most of them should be fairly simple to fix, unless the scanner mapping is all broken, in which case it might take a bit longer.

I'll take another look at fixing them after lunch.

The log message would suggest that it can't calculate the route for the energy flow, but how it managed to get into that situation I have no idea. Does it happen if you create a new world too, or is it just one? Do you have anything else connected other than just the test setups you tried?

Quite an expensive cannon too, each shot takes a lot of uranium (and plutonium if you're using MOX). It would probably be more effective to invent a nuke TNT launcher.

Nearly everything works fine and should have a recipe. Cables being black is a lighting bug that likes to happen, and if they're pink and black you need to update as that was fixed about a week ago. Anything that is broken you can just ask about, occasionally things can be missed/forgotten.

All the cables will be fine, as gold is HV, as is the MFE output. All your machines that are tier 1 or 2 that don't have transformer upgrades and are connected will explode, no matter the power they might demand due to overclocking.

I'd say 1.8.9 isn't especially better in terms of bugs, enet explosions are back for 1.9+, JEI support is substantially better, and there's all sorts of little things like energy storage blocks ignoring redstone, energy splitter+detector cables not working and trade/energy-o-mats not working with personal safe. There isn't a version of Thaumcraft 5 or Buildcraft for 1.9+ though.

If you do move, your world should be fine, I've not tried doing it with particularly large worlds but nothing should break. Apart from bad wiring though, that could cause your machines to explode

Having water around a reactor no longer affects how hot it is too.

The crash is from Mystcraft, it has (or at the very least used to have) issues with Cauldron.

Super tiny mod that allows NEI to dump a bigger array of texture sizes, because Greg makes textures too detailed for poor Retep to cope with.

Doesn't have nice diamond ones though Greg

I don't know, I think some of them might have. Either way, with the way the pound fell today, prime time to book a holiday here

Quote from Aroma1997

Personal chest currently being broken is a bug. (I think, Chocohead can tell you more about it..)

It is, the trade-o-mat's inventory searcher doesn't account that personal blocks have the chance to access each other, so when it tries looking for slots it can use, it's blocked because it attemps accessing them like a normal block would. I've fixed it for 1.9, but never bothered to back port it.

Quote from GregoriusT

Wait, the fixed enet isnt a config but a JAVA PARAMETER!?! what the actual fuck, I hope this isnt true.

It's the inverse, the fixed one is default and the Java parameter is for Player to still be able to work on the experimental one. It's not a config because it isn't the kind of thing that people would typically want to re-enable.

The bug itself is a strange one but I've seen it reported before, the enet still has edge case unloading/loading issues.

Having to make reflectors makes automating the reactor much more complicated, as mixing up where the uranium and the reflectors go is not a good idea.

The iridium reflector is in IC2 1.8.9+ and component heat exchanges should be allowed in fluid reactors if they're not damaged. But the detection for components allowed and not allowed in fluid reactors is a little wonky anyway.

Normally you'd just recycle the water from the turbines into the steam generator, as it should be able to be a closed loop. Distilled Water also avoids the steam generator from calcifying.

The Steam Generator will always output if it's set to more than 0mb/t, no matter how hot it is (which is probably a little silly of it), so your best bet is to wait for it to heat up to 374 C at 0mb/t then increase it to 1 mb/t. The other issue I can see is that the distilled water that the second steam turbine and the condenser will collect doesn't have anywhere to go, you're going to want some way to get it back into the steam generator or their internal tanks will fill and break the system.

Whilst adding the coolant injectors, estebes managed to emit something incredible like 16,000 HU/t from very hot quad MOX rods, but I don't have the screenshot lying around of that.