Posts by SirGouki

  • Problem: IC2 instructions completely unlinked. Wiki needs to die in a fire.

    Quote from RawCode

    noobs need to die in fire btw, learn to read.

    ps. i suggest to add simple and effective method to prevent such problems by adding forced exception possibly division by zero on version missmatch with addtional info displayed prior exception.

    also you may override security settings and delete something from noob's hdd for greater effect.

    Good God, is THIS really how stuff gets done around here?! Yes that's a grand idea. Just ask Microsoft how much money they lost in a lawsuit when they got sued for bricking computers that had AMD chips in them with a combination of a forced security update and a service pack release, even though it clearly states in the license agreement for Windows that they are not to be held responsible for any damage caused by using their software. That was completely UNINTENTIONAL too. There are things called laws, and even free or open sourced software has to follow them, and if you are that against IndustrialCraft 2's PROGRESS, you need to GTFO. People like you make good things go bad quick.

  • RE: Invisible nukes/nukes swapping with illuminators/etc.

    I know at least 2 of these are known bugs. However unlike most of the posts i've seen on here about them, I've found ID Conflicts (server only strangely enough) for 6 blocks in IC2. All of these blocks function normally under SSP but have a Block ID Conflict on the server with the exact same settings between server and client, with the exact same versions of mods installed appropriate to client/server. This is under Minecraft 1.2.3/Server 1.2.3. The blocks are as follows:

    Display Spoiler


    excerpt from config.yml

    blockITNT=239
    blockLuminator=226
    blockLuminatorDark=219
    blockDynamite=236
    blockDynamiteRemote=235
    blockNuke=237


    From log.txt:

    [IC2] Config loaded from C:\Users\28032012\Desktop\Games\Minecraft\server\config\IC2.cfg
    Adding Material: 249:X249
    Adding Material: 248:X248
    Adding Material: 247:X247
    Adding Material: 243:X243
    Adding Material: 242:X242
    Adding Material: 241:X241
    Adding Material: 240:X240
    Adding Material: 234:X234
    Adding Material: 232:X232
    Adding Material: 231:X231
    Adding Material: 230:X230
    Adding Material: 229:X229
    Adding Material: 222:X222
    Adding Material: 221:X221
    Adding Material: 220:X220
    Adding Material: 224:X224
    Adding Material: 228:X228
    Adding Material: 246:X246
    Adding Material: 233:X233
    Adding Material: 227:X227
    Adding Material: 250:X250
    Adding Material: 223:X223
    Adding Material: 219:X219
    CONFLICT @ -37
    Adding Material: 226:X226
    CONFLICT @ -30
    Adding Material: 245:X245
    Adding Material: 244:X244
    Adding Material: 225:X225
    Adding Material: 239:X239
    CONFLICT @ -17
    Adding Material: 237:X237
    CONFLICT @ -19
    Adding Material: 236:X236
    CONFLICT @ -20
    Adding Material: 235:X235
    CONFLICT @ -21
    Adding Material: 218:X218

    To get a log file of this info, run your server through a batch file. at the end of the line that runs your minecraft server put >>log.txt and it will output everything up until when mods start loading into a text file, and then any commands entered when the server is up.

    I edited out my user name (obviously) and left out none conflicting block ids. Finally, again, these only conflict for the server, and I believe this is either the cause of the problems, or are closely related since everything works fine on SSP with the exact same config files.


    EDIT: Note: I've been encountering invisible nukes, nukes crafted swapping into luminators, etc. for at least since 1.8.1, dunno if its been happening longer than that or not though.