Karlcloudy

Title: Signularity Compressor API error spam Version: 0.5.1 OS: Windows Server 2012 Java Version: 1.7.0_09 Description of Problem: Whenever a singularity compressor placed and powered, it fills up the server log several times a second with an IC2 API error. Interestingly, this does not happen with other IC2 Advanced Machine blocks such as the rotary macerator. Error Messages: 2013-01-11 22:23:02 [WARNING] [iC2] API ERROR: ic2.advancedmachines.common.TileE ntitySingularityCompressor@5969abca didn't implement demandsEnergy() properly, n o energy from injectEnergy accepted although demandsEnergy() returned true. 2013-01-11 22:23:02 [WARNING] [iC2] API ERROR: ic2.advancedmachines.common.TileE ntitySingularityCompressor@5969abca didn't implement demandsEnergy() properly, n o energy from injectEnergy accepted although demandsEnergy() returned true. 2013-01-11 22:23:02 [WARNING] [iC2] API ERROR: ic2.advancedmachines.common.TileE ntitySingularityCompressor@5969abca didn't implement demandsEnergy() properly, n o energy from injectEnergy accepted although demandsEnergy() returned true. 2013-01-11 22:23:02 [WARNING] [iC2] API ERROR: ic2.advancedmachines.common.TileE ntitySingularityCompressor@5969abca didn't implement demandsEnergy() properly, n o energy from injectEnergy accepted although demandsEnergy() returned true. 2013-01-11 22:23:02 [WARNING] [iC2] API ERROR: ic2.advancedmachines.common.TileE ntitySingularityCompressor@5969abca didn't implement demandsEnergy() properly, n o energy from injectEnergy accepted although demandsEnergy() returned true. 2013-01-11 22:23:02 [WARNING] [iC2] API ERROR: ic2.advancedmachines.common.TileE ntitySingularityCompressor@5969abca didn't implement demandsEnergy() properly, n o energy from injectEnergy accepted although demandsEnergy() returned true. 2013-01-11 22:23:02 [WARNING] [iC2] API ERROR: ic2.advancedmachines.common.TileE ntitySingularityCompressor@5969abca didn't implement demandsEnergy() properly, n o energy from injectEnergy accepted although demandsEnergy() returned true. 2013-01-11 22:23:02 [WARNING] [iC2] API ERROR: ic2.advancedmachines.common.TileE ntitySingularityCompressor@5969abca didn't implement demandsEnergy() properly, n You get the idea... Error Log:

This looks similar to the error I get when I try to use rotary macerators (IC2 Advanced Machines). Did the player put one of those there? IC2 in general seems pretty heavily buggy (including this extra addon) in 3.1.3.

Title: IC2 broken in multiple ways Version: 3.1.3 OS: Windows Server 2012 (server, various client OSes including Mac, Linux and Windows have been used at one time or another to connect, although I believe the client OS to be completely irrelevant) Java Version: 1.7.0_09 x64 Description of Problem: Multiple issues exist in IC2 in Tekkit 3.1.3. None of these issues exist in the previous version 3.1.2: When a circuit is made (such as a HV solar array => or MFSU => MFSU, etc), you can break one or more of the wires without the circuit being affected (e.g. the storage unit is still receiving power even though it is not connected to the source) only true way to disconnect is to actually remove one of the devices and place it back again, etc. Redstone emitted from the storage units (e.g. when they are set to 'emit when empty', etc) do not change redstone output unless a redstone signal is updated nearby. This leads to empty storage units not outputting redstone when they are set to 'Emit if empty', etc. When an explosion takes place (e.g. connecting MFSU to a furnace or something silly like that), it repeats itself until the server is restarted or another explosion (e.g. TNT) removes the offending "exploding" unit. When restarting, there does not appear to be any damage to the area around the unit like I would expect their to be (?) Somewhat related to the last point, if you are using wire that is insufficient to carry the EUP (e.g. using Ultra Low Current Cable to connect an MFSU to a HV Solar Array). The resulting smoke and shock will continue permanently (creating a nice smoke show in the process: ). Furthermore, the power will continue to transmit through the "wire" anyway allowing extremely cheap transmission of HV. Finally, the bug I have seen mentioned in these forums (I could not see any recent mentions of any of the above), is the rotary macerator/singularity compressor/centrifuge extractor server crash bug. You can crash any 3.1.3 server by simply placing any one of these and placing a redstone torch near it. Error Messages: Unfortunately, apart from the macerator bug (which I have seen other threads for), there are no visible errors indicating what is wrong, as they work, just not correctly. Error Log: