TheSunIsLeaking/recflare
3
0
Fork 0
mirror of https://github.com/djdevin/recflare.git synced 2026-09-08 14:41:28 -07:00
Code Issues Packages Projects Releases Wiki Activity

Refine reasons for creating multiplayer clone

Browse Source 
Removed redundant points about crashes and exploits in the README.
This commit is contained in:
devin
2026-06-30 16:23:19 -04:00
committed by GitHub
parent 31fdf52722
commit 8a40be4391
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -3
View File
@@ -14,10 +14,9 @@ each as an independent Worker on its own subdomain.
There are already so many multiplayer clones, why? There are already so many multiplayer clones, why?
1. None of them are fully open source (some had leaks of old code). 1. None of them are fully open source (some had leaks of old code).
2. None of them run on microservice architecture, and crash constantly. 2. None of them run on microservice architecture.
3. "Upgrading the server" is not a lasting fix. 3. "Upgrading the server" is not a lasting fix.
4. Exploits were rampant due to bad code. 4. This was fun (sort of).
5. This was fun (sort of).
RecFlare uses a true microservice architecture which, if developed correctly, is RecFlare uses a true microservice architecture which, if developed correctly, is
near infinitely scalable and could support the same number of concurrent users near infinitely scalable and could support the same number of concurrent users