// the find
ylmbtm/GameProject3
游戏服务器框架，网络层分别用SocketAPI、Boost Asio、Libuv三种方式实现， 框架内使用共享内存，无锁队列，对象池，内存池来提高服务器性能。还包含一个不断完善的Unity 3D客户端，客户端含大量完整资源，坐骑，宠物，伙伴，装备, 这些均己实现上阵和穿戴, 并可进入副本战斗，多人玩法也己实现, 持续开发中。
A multi-process MMORPG server framework in C++ with three network backend options (raw sockets, Boost.Asio, libuv) and a paired Unity client demo. It covers the full stack you'd expect for a Chinese-style mobile RPG — login, logic, game, DB proxy, gateway, and log servers — plus shared memory, lock-free queues, object pools, and memory pools for performance. The audience is C++ game server developers who want a working reference architecture to study or fork.
The choice of three network backends (SocketAPI, Boost.Asio, libuv) in one codebase is genuinely useful for comparing approaches side by side. The multi-process architecture with dedicated roles (DBServer as a write-behind proxy, ProxyServer as a message router) reflects how production MMORPG backends actually work, not toy examples. The lock-free queue and shared memory usage shows the author understands where C++ game servers actually lose time. The Unity client pairing means you can trace a feature end-to-end rather than guessing at the protocol.
The codebase is almost entirely undocumented in English, and the Chinese comments are sparse — reading the server internals requires patience and guesswork. MySQL 5.7 is hardcoded in the setup docs and is EOL; there's no hint of how to swap it or run the schema on anything newer. The project appears to be a solo learning project that stalled in 2025 with no issue tracker activity, so expect bugs with nobody to escalate to. The networking layer trio is a strength architecturally but also means three times the maintenance surface, and the implementations aren't abstracted behind a common interface — switching backends requires code changes, not config.