Differences

This shows you the differences between two versions of the page.

--- tutorial:side [2019/05/08 03:22] – liach
+++ tutorial:side [2022/04/13 04:32] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Side ======
+Minecraft uses the [[https://en.wikipedia.org/wiki/Client-server_model|Client-server model]], that is users install the game client and connect to a server to play the game. Fabric allows mods to target either the Minecraft client or the Minecraft server, but also both at the same time.
-In Minecraft game and modding, there are concepts of logical and physical sides. Understanding of sides is crucial to understanding Minecraft's inner workings.
+The concept of client/server in Minecraft is ambiguous and may refer to either physical or logical sides. The terms client/server may be used to distinguish the different distributions of Minecraft (the Minecraft client vs. a dedicated Minecraft server) which are called "physical" sides. However, a Minecraft client hosts its own integrated server for singleplayer and LAN sessions, which means that a Minecraft client also contains server logic. Therefore, client/server may also be used to distinguish parts of the game logic which are called "logical" sides.
-For both types of "side"s, there are "client" and "server". However, the logical client does not equate to the physical client, and the logical server does not equate to the physical server either.
+For both types of sides, there is a 'client' and a 'server'. However, a logical client is not equivalent to a physical client, and a logical server is not equivalent to a physical server either. A logical client is instead **hosted by** a physical client, and a logical server is hosted by either a physical server or a physical client.
-Usually, the logical sides have slightly more importance over the physical sides, for they have a bigger impact to the engine and modder's understanding of Minecraft code.
+The logical sides are central in the architecture of both distributions of Minecraft. Therefore, an understanding of logical sides is vital for any mod development with Fabric.
-===== Logical Sides =====
+===== Physical Sides  =====
-Logical sides are mainly about the threads the game run on, including the Client (does rendering, sends player inputs to the server, handles resource packs, etc.) and the Server (calculates most core logic, handles data packs,  keeps the world/game data, etc.) threads.
+The physical sides or the environment refer to the two distributions (jars) of Minecraft, the client (what the vanilla launcher launches), and the server (download available on [[https://minecraft.net]] for free). A physical side refers to which code is available in the current environment.
-The packets (which [[https://wiki.vg]] documents) between minecraft sides are sent between logical clients and logical servers. Mods can add packets in order to transfer information between two logical sides.
+The client and server environment are minified distributions of the same program, containing only the required parts of the code.
-In Minecraft, in order to reduce code, the logical client and servers share some logic classes, including<code>
+In Fabric, you can often see annotations like ''@Environment(EnvType.CLIENT)''. This indicates that some code is present only in one environment; in this example, the client.
-net.minecraft.world.World
-net.minecraft.entity.Entity
-net.minecraft.block.entity.BlockEntity
-</code>
-and a few more. These shared classes allow logical clients to shadow some common game logic from the logical server for easy rendering. (block entities are shadowed to the logical client optionally)
-Usually, to identify the shadowed objects on the logical clients from the real ones on the logical server, vanilla and mod code access the World referenced in these objects and check the world's isClient field (in Fabric yarn) so that they do not possibly perform useless calculations on the logical client so as to avoid de-synchronization between the two logical sides and to reduce load on the logical client.
+In Fabric fabric.mod.json and the mixin config, the client/server refers to the environment.
-==== Client ====
+Each physical side ships classes used by its entry point and the data generator classes with entrypoint ''net.minecraft.data.Main''.
-The logical client is where most displays to the player is done. Rendering (LWJGL), resource pack, player input handling, sounds, etc. all happen on the logical client.
-The logical client runs on the main thread of the physical client exclusively. It is not present on the physical server. It is a singleton and always exists.
+===== Logical Sides =====
-In yarn, the C2S packets are sent from the logical client (which calls write method in a network thread), and the S2C packets are received by the logical client (which calls read method in a network thread).
+The logical sides are responsible for the actual game logic.
+The logical client does rendering, sends player inputs to the server, handles resource packs, and partially simulates the game world. The server handles the core game logic, data packs, and maintains the true state of the game world.
-==== Server ====
+The client maintains a partial replica of the server's world, with copies of objects such as:<yarncode>
-The logical server is where most of the game logic is going on. Data packs, world updates, block entity and entity ticks, mob AI, game/world saving, world generation, etc. all happen on the logical server.
+net.minecraft.class_1937
+net.minecraft.class_1297
+net.minecraft.class_2586
+</yarncode>
+These replicated objects allow clients and servers to perform some common game logic. The client can interact with these objects while the server is responsible for keeping them in sync. Usually, to distinguish objects on the logical clients from the ones on the logical server you would access the world of the object and check its ''isClient'' field. This can be used to perform authoritative actions on the server such as spawning entities, and to simulate actions on the client. This technique is necessary to avoid desynchronization between the two logical sides.
+===== Detailed look into all sides =====
-The logical server on the physical client is called the "Integrated Server", while the logical server on the physical server is called the "Dedicated Server" (which is also the name of the physical server itself).
+With an understanding of which sides there are and how to distinguish between them, we can now look at each side in detail.
-The logical server never runs on the thread which went through the entrypoint of a physical side, even on physical servers. Still, it has its own thread, on which it handles its logic. It is a singleton that always exists on physical servers; on the physical client, it exists one instance at a time when the player is playing a local save, and a new instance is created every time the player loads a local save.
+==== Physical Client ====
+The physical client is the minecraft jar downloaded by the vanilla launcher. It contains a logical client and a logical server (integrated server). Its entrypoint is ''net.minecraft.client.main.Main''.
-In yarn, the S2C packets are sent from the logical server (which calls write method in a network thread), and the C2S packets are received by the logical server (which calls read method in a network thread).
+A physical client can load several different worlds, each within a separate logical server, but only one at a time.
-===== Physical Sides (EnvType) =====
+Compared to the logical server of the physical server (dedicated server), the logical server of the physical client (integrated server) can be controlled by the logical client on the physical client (e.g., F3+T reloads data packs and shutting down the client also shuts down the integrated server). It can also load resource packs bundled in a world to the logical client on the physical client.
-The physical sides refer to the two distributions (jars) of Minecraft game, the client (what the vanilla launcher launches) and the server (download available on [[https://minecraft.net]] for free), which are launched in different ways.
+All the logical client content is exclusive to the physical client, therefore you see many environment annotations on rendering, sound, and other logical client code.
-In Fabric, you can often see annotations like <code>@Environment(EnvType.CLIENT)</code>This indicates that some code is present only on one physical side, in this case here, on the client.
+Some mods target physical clients exclusively, for instance, Liteloader, Optifine, and Minecraft PvP clients (Badlion, Hyperium).
-In Fabric fabric.mod.json and the mixin config, the client/server refers to the physical side.
+==== Physical Server ====
-Each physical side ships classes used by its respective entry point and the data generator classes with entrypoint<code>net.minecraft.data.Main</code>
+The physical server is the java dedicated server. Compared to a physical client, it only has a logical server (dedicated server). Its entrypoint is ''net.minecraft.server.MinecraftServer'' and the physical server can only have one world during its runtime. If a server should switch to another world, a server restart is required.
-==== Client ====
+Its logical server differs slightly from that of a physical client as only one logical server instance is ever present when the physical server is running. Moreover, the logical server of the physical server can be controlled remotely via Rcon, has a config file called server.properties, and can send server resource packs.
-The physical client is the minecraft jar downloaded by the vanilla launcher. It contains a logical client and a logical server (integrated server). Its entrypoint is <code>net.minecraft.client.main.Main</code>.
-As a physical client can load worlds (launch integrated servers/its logical server) without a limit, but a previous logical server on a physical client must be stopped for a new one to launch.
+Despite these differences, most mods are applicable without problems to the logical servers of both the physical client and the physical server as long as they do not refer to logical client content.
-Compared to the logical server of the physical server (dedicated server), the logical server of the physical client (integrated server) can be controlled by the logical client on the physical client (e.g. F3+T reloads data packs and shutting down the client shuts down the integrated server). It can also load resource packs bundled in a world to the logical client on the physical client.
+Its features of single world and resource pack sending, however, make vanilla mod (data pack and resource pack combination) installation much easier compared to on clients, as vanilla physical clients set up when connecting to the server automatically.
-All the logical client contents are exclusive to the physical client. Hence, you will see a lot of environment annotations on rendering, sound, and other logical client code.
+Some mods target physical server exclusively. For instance, Bukkit and its derivatives (Spigot, Paper, Cauldron, Xxx-Bukkit hybrids) always run on the physical server.
-Some mods target physical clients exclusively. For instance, Liteloader, Optifine, Minecraft PvP clients (Badlion, Hyperium, etc.)
+==== Logical Client ====
+The logical client is the interface to the player. Rendering (LWJGL), resource pack, player input handling, and sounds happen on the logical client. It is not present on the physical server.
-==== Server ====
+==== Logical Server ====
-The physical server is the java dedicated server. Compared to a physical client, it only has a logical server (dedicated server). Its entrypoint is <code>net.minecraft.server.MinecraftServer</code>
+The logical server is where most of the game logic is executed. Data packs, world updates, block entity and entity ticks, mob AI, game/world-saving,  and world generation, happen on the logical server.
-Compared to the physical client, the physical server can only have one world/save as its logical server is a singlton.
+The logical server on the physical client is called the "Integrated Server", while the logical server on the physical server is called the "Dedicated Server" (which is also the name of the physical server itself).
-Its logical server differs slightly from that of a physical client as only one logical server instance will be ever present when the physical server is ran. Moreover, the logical server of the physical server can be controlled remotely via Rcon, has server.properties, and can send server resource packs.
+The logical server runs in its own main thread, even on physical servers, and has a few worker threads. The lifetime of a logical server depends on the physical side it is hosted on. On a physical server, a logical server exists for as long as the process is running. On a physical client, multiple logical servers may be created, but only one logical server may exist at a time. A new logical server is created when the player loads a local save and closed when the player closes the local save.
-Despite these differences, most mods are fine and applicable to the logical servers of both the physical client and the physical server as long as they do not refer to logical client contents.
+Most universal mods target the logical server so that they can work both in single player and multi player scenarios.
+===== Communication=====
-Its features of single world and resource pack sending, however, makes vanilla mod (data pack and resource pack combination) installation much easier compared to on clients, as vanilla physical clients will be set up when connecting to the server automatically.
+The only correct way to exchange data between logical clients and servers is by exchanging packets. The packets (as documented on [[https://wiki.vg]]) are sent between logical clients and logical servers, not physical sides. Mods can add packets to transfer custom information between two logical sides. Packets are exchanged in-memory for a logical client connected to its own integrated server, and exchanged over a networking protocol otherwise.
-Some mods target physical server exclusively. For instance, Bukkit and its derivatives (Spigot, Paper, Cauldron, Xxx-Bukkit hybrids) always target the physical server.
+Logical clients send C2S (Client-To-Server) packets to the logical server.
+The logical server sends S2C (Server-To-Client) packets the logical clients.
+Packets are sent by a write method in a network thread and received by a call to a read method in a network thread.
+For more details on how to handle networking, see [[tutorial:networking|this article]].
+===== Common misconceptions about logical servers =====
+Most of the time, mods exclusively targeting the physical server also work on logical servers inside of physical clients.
+However, modders for physical servers usually have assumptions which do not apply to integrated servers, including but not limited to:
+  * Only one logical server instance exists on one game run
+  * The world and entities should always calculate the game logic (i.e., the isClient field of the world object is always false)
+  * Remote control, resource pack sending, and Favicon are present
+These assumptions need to be corrected to make mods that run on logical servers.
 ===== Conclusion =====
@@ Line 79: / Line 96: @@
 Ultimately, the main confusion comes from the fact that logical servers exist on physical clients.
-==== Logical Server in Physical Client ====
- and modders on those platforms have incorrect assumptions of logical servers in general, including but not limited to:
-  * Only one logical server instance will ever exist on one game run
-  * The world and entities should always calculate the game logic (i.e. the World.isClient field is always false)
-  * Remote control, resource pack sending, and Favicon are present