Simple top-down multiplayer game in Godot. It is a pure hobby project written just to find out how difficult is to write a server-governed multi-player game in Godot.
It's not a complete game, it only has a few essential features and can be used as an inspiration on how to deal with server-client communication in your Godot projects.
The project features a multiplayer game where each player controls a single character by issuing commands rather than controlling the character movement directly. This was a design choice as such a control scheme is more suitable to slower-paced RPGs (or RTSs) which I'm more interested in than FPSs. The code can be easily modified to allow for controlling of multiple units (RTS style)
- game features
- character movement around a map
- inventory & usable items
- scanline weapons
- basic health & damage logic
- multi-player code
- lobby & chat
- full server autority sync scheme
- fast unreliable updates for the world state
- slower reliable updates for events (e.g. player join, item pickup, effects, etc.)
- tile sets
- all tile types used (autotiles, atlas tiles, single tiles)
- working YSort for large single tiles (with correct origin at the bottom)
- AI
- collision-based sensors for hearing and sight
- A* navigation with preferred paths (roads) and obstacles working with tilesets collision & navigation shapes
- rudimentary AI for NPCs (walk around and say lines)
The main principle I followed was make it as simple as possible. There are some really detailed tutorials but often covers too many non-essential features. I tried to put just bare minumum to make it playable and to showcase essential features in the multiplayer game use-case. Currently the whole project has ~1200 loc.
I also tried to follow best practices recommended by the Godot team (like aggregation over inheritance, encapsulating scripts to nodes they affect etc.) but to keep it simple, there are some tradeoffs. Many things can be (and should be) done diferently for the bigger project. Anyway, I believe in short iterations and adding stuff only when necessary.
For the net code, I used Godot's high-level multiplayer framework which works perfectly for my use-case.
I've mixed the server and the client code together and extensively use remotesync keyword where any udpate to both server/client was needed, occasionally adding master/puppet to indicate special cases.
I've separated the server section and the remote section in the code so it can be seen what runs on server only and whats propagated to clients. The code isn't fully commented but should be self-explanatory. I tried to explain myself when the code started to look hairy.
The project isn't by any mean feature complete and I do not guarantee or plan to add new features in near future. I might continue with the development and put more stuff in (especially around NPCs AI support) but it really depends on my free time.
Anyway, I welcome comments, suggestions or bug reports but cannot guarantee I'll intergate it. Feel free to fork it for yourself.
Published under MIT license but there are some files (tilesets) that are for non-commercial uses only!
Many, many thanks to:
- Magiscarf for amazingly detailed tilesets
- DoubleLeggy for a beautiful set of character animations