• Forums

Navigation

  • Home
  • Style Guide
  • Getting Started
    • Home
    • Structuring Your Mod
    • Forge Update Checker
    • Debug Profiler
  • Concepts
    • Sides
    • Resources
    • Data
    • Registries
    • Mod Lifecycle
    • Internationalization and Localization
  • Blocks
    • Home
    • BlockStates
    • Interaction
  • Block Entities
    • Home
    • Renderer
  • Items
    • Home
    • Loot Modification
  • Models
    • Intro to Models
    • Model Files
    • BlockStates
      • Intro to BlockState JSON
    • Coloring Textures
    • Item Properties
    • Advanced Models
      • BakedModel
      • Perspective
      • Item Overrides
  • Rendering
    • BlockEntityWithoutLevelRenderer
  • Data Generation
    • Introduction
    • Model Providers
  • Events
    • Basic Usage
  • Networking
    • Home
    • Overview
    • SimpleImpl
    • Entities
  • Data Storage
    • Capabilities
    • Saved Data
  • Utilities
    • Recipes
    • Tags
  • Effects
    • Particles
    • Sounds
  • Conventions
    • Versioning
    • Locations
  • Advanced Topics
    • Access Transformers
  • Contributing to Forge
    • Getting Started
    • PR Guidelines
  • Legacy Versions
    • Home
    • Porting to 1.17

Overview

There are two primary goals in network communication:

  1. Making sure the client view is “in sync” with the server view
    • The flower at coordinates (X, Y, Z) just grew
  2. Giving the client a way to tell the server that something has changed about the player
    • the player pressed a key

The most common way to accomplish these goals is to pass messages between the client and the server. These messages will usually be structured, containing data in a particular arrangement, for easy sending and receiving.

Built with MkDocs using a custom theme. Hosted by Read the Docs.
Enable Dark Theme