![[Making an MMO] Episode 1 - Opening Windows and Drawing Sprites @UnitOfTimeYT](https://i.ytimg.com/vi/dsabHK_TspA/maxresdefault.jpg)
Uploaded July 2021 | Updated September 2026, 1 week ago
⁍ Wishlist: store.steampowered.com/app/3475620/Mythfall
If you're interested in learning what it takes to make an MMO then you're in the right place. The goal of this series is to investigate all of the common software problems that you might face when building your own MMO. In that sense, the goal of this series is to be educational. We will explore a variety of topics in a reasonable amount of depth: Rendering, Networking, Deployments, Organization, Algorithms and much more.
When people say MMO, they typically mean a massive game. We might not be able to reach that scale, but we will design our systems with scale in mind. A more precise name for what we will build is a "persistent, distributed online game". That's kind of long to say, so I'll just stick with 'MMO'. Because MMOs require several different domains of knowledge, I will definitely need to learn a few things along the way. I'll try to give each subject the explanation it deserves, but in case I miss anything - feel free to let me know.
The language we are going to use for this project is "Go" (Also known as "Golang"). Go is a relatively simple language, but packs an enormous punch when it comes to features and libraries. In my opinion, these characteristics make Go a great choice for teaching software and software architectures.
Well that's all I have now, I hope you'll stick around and let me know what you think.
Credit to asciiquarium for the introduction ASCII aquarium.
// Repository: github.com/unitoftime/mmo
// Play: mythfall.com
⁍ Wishlist: store.steampowered.com/app/3475620/Mythfall
If you're interested in learning what it takes to make an MMO then you're in the right place. The goal of this series is to investigate all of the common software problems that you might face when building your own MMO. In that sense, the goal of this series is to be educational. We will explore a variety of topics in a reasonable amount of depth: Rendering, Networking, Deployments, Organization, Algorithms and much more.
When people say MMO, they typically mean a massive game. We might not be able to reach that scale, but we will design our systems with scale in mind. A more precise name for what we will build is a "persistent, distributed online game". That's kind of long to say, so I'll just stick with 'MMO'. Because MMOs require several different domains of knowledge, I will definitely need to learn a few things along the way. I'll try to give each subject the explanation it deserves, but in case I miss anything - feel free to let me know.
The language we are going to use for this project is "Go" (Also known as "Golang"). Go is a relatively simple language, but packs an enormous punch when it comes to features and libraries. In my opinion, these characteristics make Go a great choice for teaching software and software architectures.
Well that's all I have now, I hope you'll stick around and let me know what you think.
Credit to asciiquarium for the introduction ASCII aquarium.
// Repository: github.com/unitoftime/mmo
// Play: mythfall.com
![[Making an MMO] Episode 1 - Opening Windows and Drawing Sprites](https://i.ytimg.com/vi/dsabHK_TspA/mqdefault.jpg "[Making an MMO] Episode 1 - Opening Windows and Drawing Sprites
⁍ Wishlist: https://store.steampowered.com/app/3475620/Mythfall/
If youre interested in learning what it takes to make an MMO then youre in the right place. The goal of this series is to investigate all of the common software problems that you might face when building your own MMO. In that sense, the goal of this series is to be educational. We will explore a variety of topics in a reasonable amount of depth: Rendering, Networking, Deployments, Organization, Algorithms and much more.
When people say MMO, they typically mean a massive game. We might not be able to reach that scale, but we will design our systems with scale in mind. A more precise name for what we will build is a persistent, distributed online game. Thats kind of long to say, so Ill just stick with MMO. Because MMOs require several different domains of knowledge, I will definitely need to learn a few things along the way. Ill try to give each subject the explanation it deserves, but in case I miss anything - feel free to let me know.
The language we are going to use for this project is Go (Also known as Golang). Go is a relatively simple language, but packs an enormous punch when it comes to features and libraries. In my opinion, these characteristics make Go a great choice for teaching software and software architectures.
Well thats all I have now, I hope youll stick around and let me know what you think.
Credit to asciiquarium for the introduction ASCII aquarium.
// Repository: https://github.com/unitoftime/mmo
// Play: https://mythfall.com")
![[Making an MMO] Episode 9 - Client/Server Rearchitecture](https://i.ytimg.com/vi/jx2qsTLxMXc/mqdefault.jpg "[Making an MMO] Episode 9 - Client/Server Rearchitecture
⁍ Wishlist: https://store.steampowered.com/app/3475620/Mythfall/
There are some organizational challenges when building client server architectures. Namely, we will often be asking the question, Will this code be accessed from the client, the server, or both? So today we will perform some initial organizations to remove opengl dependencies in our server binary, we will also start moving our game logic code out of the clients main.go file and into a common location.
This tutorial series is about creating an MMO from (almost) scratch. We will be coding in Golang and we will use libraries where appropriate. I will stay at a fairly high level for most things, but let me know if you want a more intensive study on any individual topic and Ill try to make an episode where possible.
Thanks for watching! Let me know if you have any questions!
// Repository: https://github.com/unitoftime/mmo
// Play: https://mythfall.com")
