Write Better Netcode

Multiplayer Project for Production

Have you eagerly started a Unity multiplayer project after working through Netcode tutorials that made you feel like this is easy-peasy?

But then you run into inexplicable, random issues all the time?

Write Better Netcode introduces you to writing production-ready Multiplayer game code!

We’re going to re-create my MultiPal project with Statemachines:

Write Better Netcode Articles

MultiPal DevLog Oct ’24

It’s been a while since the last article on Write Better Netcode. 😟 The reason for this is, the project…

Bonus Articles (Appendix)

I tend to deep-dive into specific topics while writing an article, only to find out that it would be too distracting or off-topic. I publish those articles separately from the series.

These articles explain related networking topics:

These are articles I’ve written before I started the Write Better Netcode series. They are not quite as high quality as what I’m writing currently but they do contain valuable info:

Don’t Miss An Article!

Join my Patreon to get notified! New articles appear twice a month, with occassional devlogs for Patreons.

Following are more details about the Write Better Netcode series:

Not A Beginner’s Tutorial

Anyone can GameObject.Find(“Player”) and get going. That tutorial was easy enough, so the rest can’t be that hard either. Right?

Well, no …

We game developers do not spend enough time to create a solid foundation. So the more we build on top of our game, the more it starts to crumble and fall apart.

Instead, Write Better Netcode is about building a foundation designed to support a wide variety of both networked multiplayer, splitscreen and singleplayer games.

I prefer to be very thorough, thoughtful, weigh and explain intricate details, apply discipline. As game developers, we are rarely afforded the luxury to do so.

That’s why we’re crunching so much! Among other things …

GitHub Repository

The WriteBetterNetcode GitHub repository contains the current state of the project. Tags are used to mark progress.

Please mind the project’s GNU GPL3 license. It’s a copyleft license which means the project can be used as follows:

Privately, to study and learn.
Publicly, provided you also publish your entire work in working form to the public under the same GPL3. (*)
Unrestricted, by becoming a patron.

I trust you and I hope you value my work! 🙂

^{(*) Note: Most digital store’s terms are in violation of the GPL3 license terms, thus forbidding apps that include GPL3 software.}

Project Plan

I use PivotalTracker to manage tasks and bugs and lay down a roadmap (Epics).

The MultiPal board is publicly accessible here.

PT has been my preferred tool for over ten years now, and I’ve evaluated and worked with many, many others (Jira, Bugzilla, Shotgun, Hansoft, Monday, GitHub, etc). I love PT for its simplicity and directness.