Hopefully let build continue if server reobf fails, and fix derp in FMLNetworkHandler for entities
This commit is contained in:
parent
a8f69529fd
commit
6f10295936
2 changed files with 1 additions and 3 deletions
|
@ -97,8 +97,6 @@
|
|||
<condition>
|
||||
<not>
|
||||
<and>
|
||||
<available file="${mcp.home}/temp/server.md5"/>
|
||||
<available file="${mcp.home}/temp/server_reobf.md5"/>
|
||||
<available file="${mcp.home}/temp/client.md5"/>
|
||||
<available file="${mcp.home}/temp/client_reobf.md5"/>
|
||||
</and>
|
||||
|
|
|
@ -318,7 +318,7 @@ public class FMLNetworkHandler
|
|||
}
|
||||
Packet250CustomPayload pkt = new Packet250CustomPayload();
|
||||
pkt.field_73630_a = "FML";
|
||||
pkt.field_73629_c = FMLPacket.makePacket(Type.ENTITYSPAWN, er, entity);
|
||||
pkt.field_73629_c = FMLPacket.makePacket(Type.ENTITYSPAWN, er, entity, instance().findNetworkModHandler(er.getContainer()));
|
||||
pkt.field_73628_b = pkt.field_73629_c.length;
|
||||
return pkt;
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue