https://forge.gemwire.uk/index.php?action=history&feed=atom&title=Networking%2F1.17Networking/1.17 - Revision history2026-05-01T18:42:41ZRevision history for this page on the wikiMediaWiki 1.35.0https://forge.gemwire.uk/index.php?title=Networking/1.17&diff=3044&oldid=prevShrimpBot: Copy Networking to MC1.17 archive2021-12-06T05:51:06Z<p>Copy <a href="/wiki/Networking" title="Networking">Networking</a> to MC1.17 archive</p>
<p><b>New page</b></p><div>Communication between servers and clients is the backbone of a successful mod implementation.<br />
<br />
Read an [[Understanding Networking#overview/1.17|overview]] of why networking matters and the basic strategies in thinking about networking.<br />
<br />
There are a variety of techniques provided by Forge to facilitate communication - mostly built on top of [https://netty.io netty].<br />
<br />
The simplest, for a new mod, would be [[Using SimpleChannel/1.17|SimpleImpl]], where most of the complexity of the netty system is<br />
abstracted away. It uses a message and handler style system.<br />
<br />
== Overview ==<br />
<br />
There are two primary goals in network communication:<br />
<br />
# Making sure the client view is "in sync" with the server view<br />
#* The flower at coordinates X, Y, Z just grew<br />
# Giving the client a way to tell the server that something has changed about the player<br />
#* the player pressed a key<br />
<br />
The most common way to accomplish these goals is to pass messages between the client and the server. These messages will<br />
usually be structured, containing data in a particular arrangement, for easy sending and receiving.</div>ShrimpBot