From 8a40be43910f16cee83014465b128d44456d29c1 Mon Sep 17 00:00:00 2001 From: devin Date: Tue, 30 Jun 2026 16:23:19 -0400 Subject: [PATCH] Refine reasons for creating multiplayer clone Removed redundant points about crashes and exploits in the README. --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d77ca33..8319c44 100644 --- a/README.md +++ b/README.md @@ -14,10 +14,9 @@ each as an independent Worker on its own subdomain. There are already so many multiplayer clones, why? 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. -4. Exploits were rampant due to bad code. -5. This was fun (sort of). +4. This was fun (sort of). RecFlare uses a true microservice architecture which, if developed correctly, is near infinitely scalable and could support the same number of concurrent users