4
edits
Changes
From Forge Community Wiki
→Registering Packets: fix errors and demonstrate new builder
Line 38:
Line 38:
// A class MessagePacket+ // Write to buffer+
+ // Create packet from buffer data+public void messageConsumer(Supplier<NetworkEvent.Context>> ctx) {+ // Handle message+}+channel.registerMessage(id, MessagePacket::encoder, MessagePacket::decoder, MessagePacket::messageConsumer);+
<syntaxhighlight lang="java">
<syntaxhighlight lang="java">
−class MessagePacket {
−public void encoder(FriendlyByteBuf buffer) {
+ public void encoder(FriendlyByteBuf buffer) {
− // Write to buffer
−}
+ }
+ public static MessagePacket decoder(FriendlyByteBuf buffer) {
+ // Create packet from buffer data
+ }
−public static MessagePacket decoder(FriendlyByteBuf buffer) {
+ public void messageConsumer(Supplier<NetworkEvent.Context> ctx) {
− // Handle message
+ }
}
}
−// Original direct registration syntax
−INSTANCE.registerMessage(id, MessagePacket.class,
− MessagePacket::encoder,
+ MessagePacket::decoder,
+ MessagePacket::messageConsumer);
+ // Consumer here must use enqueueWork and setPacketHandled
−// For some SimpleChannel channel
+// New builder-based definition
−INSTANCE.messageBuilder(MessagePacket.class, id)
+ .encoder(MessagePacket::encoder)
+ .decoder(MessagePacket::decoder)
+ .consumerMainThread(MessagePacket::messageConsumer);
+// You can use consumerMainThread or consumerNetworkThread.
+// If you use consumerMainThread, the builder will take care of the enqueueWork and setPacketHandled.
+// With consumerNetworkThread, you can return a value instead of calling setPacketHandled.
</syntaxhighlight>
</syntaxhighlight>