GoWorld is an Apache-2.0 licensed, scalable distributed game server engine written in Go, with hot swapping of game logic, aimed at developers and studios that run persistent multiplayer game worlds.

What it is

GoWorld is a game server engine written in the Go programming language and released under the Apache-2.0 licence. It adopts an entity framework, in which entities represent all players, monsters and NPCs. Entities in the same space can visit each other directly by calling methods or accessing attributes, while entities in different spaces call each other using RPC. A running server consists of one dispatcher, one or more games and one or more gates: the gates handle client connections and receive and send packets from and to clients, the games manage all entities and run all game logic, and the dispatcher redirects packets among games and between games and gates.

The concrete problem it solves is twofold. Capacity is addressed by distribution, since server capacity is increased by using more machines instead of scaling one process. Deployment is addressed by hot swapping: the game processes are hot-swappable, and a game can be swapped by sending SIGHUP to the process and restarting it with the -restore parameter to bring the game back to work with the latest executable image. That replaces stopping a game server, shipping a new build and reconnecting players, because server-side logic can be updated and server bugs fixed transparently without significant interference of online players.

Key capabilities

• Spaces and entities are managed by the engine with AOI (area of interest) support.
• The architecture is distributed, so capacity grows by using more machines.
• Game processes are hot-swappable through SIGHUP and a restart with the -restore parameter.
• Clients can connect over TCP, KCP or WebSocket.
• Traffic between clients and servers can be compressed and encrypted.
• Entities within one space are reached by direct method calls and attribute access; entities in different spaces use RPC.
• A chatroom demo and a Unity demo (GoWorldUnityDemo.zip) are included.

Who uses it and how

• Teams building persistent multiplayer worlds with shared spaces, where AOI and space/entity management matter; the tutorial series covers movement synchronization and AOI alongside login, registration and storage.
• Live-service teams that need to ship logic changes to running games, using the documented SIGHUP plus -restore swap rather than taking the game down.
• Chat applications, covered by the chatroom demo and a walkthrough for building a distributed chat server, including a multi-channel chatroom.
• Unity client projects, supported by the Unity demo download and a tutorial on dual-end debugging of the Unity example.
• Chinese-speaking developers, served by Chinese documentation on GoDoc, a directory structure wiki page, a ten-part Zhihu tutorial series and a QQ group for Go server development exchange.

Getting started

GoWorld is obtained and run as a Go project at the package path github.com/xiaonanln/goworld, with the README's "Get GoWorld" and "Manage GoWorld Servers" sections covering installation, running and management. Chatroom and Unity demos are provided as starting points.

How it compares

The facts supplied here name neither paid products that GoWorld replaces nor comparable game server engines to measure it against, so in this registry it stands alone. What can be said is confined to its own terms: it is Apache-2.0 licensed, self-hosted Go software that scales by running one dispatcher with one or more game processes and one or more gates across more machines.

When to use it — and when not to

A self-hoster must operate a cluster of cooperating processes rather than a single binary: one dispatcher, one or more games and one or more gates, spread across machines as capacity grows, with updates delivered by restarting a game process with -restore rather than by patching it in memory. It is a poor fit for teams that want a managed backend, or whose server-side logic is not written in Go, since game logic runs inside the engine's Go processes. The clearest weakness is documentation: the README excerpt is sparse and much of the substantive material is in Chinese, and while 2,718 stars, 474 forks and a last push on 14 November 2025 indicate an active project, its English-language material is thin relative to its scope.

go install github.com/xiaonanln/goworld/cmd/...

$ goworld build examples/chatroom_demo

$ goworld start examples/chatroom_demo

$ goworld stop examples/chatroom_demo

$ goworld reload examples/chatroom_demo

$ goworld status examples/chatroom_demo
> 1 dispatcher running, 1/1 gates running, 1/1 games (examples/chatroom_demo) running
> 	2763      dispatcher      /home/ubuntu/go/src/github.com/xiaonanln/goworld/components/dispatcher/dispatcher -dispid 1
> 	2770      chatroom_demo   /home/ubuntu/go/src/github.com/xiaonanln/goworld/examples/chatroom_demo/chatroom_demo -gid 1
> 	2779      gate            /home/ubuntu/go/src/github.com/xiaonanln/goworld/components/gate/gate -gid 1

goworld build examples/chatroom_demo

goworld start examples/chatroom_demo

goworld build examples/unity_demo

goworld start examples/unity_demo