RandomPatches (Forge)

RandomPatches (Forge)

56M Downloads

Doesn't work / failed to patch class / conflict with other mod?

ZXQWAS opened this issue ยท 2 comments

commented

Hello. This mod doesn't seem to help us. My friend keeps disconnecting when logging in, either with "timed out" or "disconnected". I have a powerful new Xeon W-2125 with 32G of RAM, he has a weak PC. We're trying to play over "LAN", without a dedicated server. We can sometimes connect on some days (unstable) but on other days not at all. I'm attaching my debug log for the latest session, could you perhaps identify any mods that could be conflicting with yours? http://rgho.st/private/7GfKCxT55/5771e9fb3550ae3db929154bb6c3796e

Our options are:
I:keepAlivePacketInterval=30
I:loginTimeout=900
I:readTimeout=180

I think these lines are of special interest:

[17:03:54] [main/INFO] [STDOUT]: [com.therandomlabs.randompatches.RPTransformer:transform:38]: Patching class: net.minecraft.network.NetHandlerPlayServer
[17:03:54] [main/INFO] [STDOUT]: [com.therandomlabs.randompatches.RPTransformer:findUpdateMethod:308]: Patching method: e
[17:03:54] [main/INFO] [STDERR]: [com.therandomlabs.randompatches.RPTransformer:transform:52]: Failed to patch class: net.minecraft.network.NetHandlerPlayServer
[17:03:54] [main/INFO] [Gotta Go Fast]: patching net.minecraft.network.NetHandlerPlayServer.processVehicleMove(CPacketVehicleMove)
[17:03:54] [main/INFO] [Gotta Go Fast]: patching net.minecraft.network.NetHandlerPlayServer.processPlayer(CPacketPlayer)

UPD: I did a forced modpack update (legacy FTB launcher), updated to latest version of randompatches, disabled gotta go fast, and this started to work. It applies the patch, lets us connect.

commented

The update to the latest version probably solved it as I fixed this issue in 1.12.2-1.2.1.1, but try adding Gotta Go Fast back again to ensure that it works.

commented

Hm, yeah, I did that. Judging by the log, it worked fine this time. I didn't have the friend online to test it with though. There's no "Failed to patch class" anywhere in the log. I suppose you can close this.