fix reading pre 1.4 status response strings if the server MOTD contai…

…ns §
aternosorg · Nov 7, 2024 · 0dbb895 · 0dbb895
1 parent f39bccf
commit 0dbb895
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 5 deletions.
diff --git a/package.json b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "craftping",
   "type": "module",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "main": "index.js",
   "repository": "github:aternosorg/craftping",
   "scripts": {

diff --git a/src/JavaPing/Status/LegacyStatus.js b/src/JavaPing/Status/LegacyStatus.js
@@ -104,13 +104,16 @@ export default class LegacyStatus {
      */
     fromPre14String(string) {
         let parts = string.split("§");
-        if (parts.length !== 3) {
+        if (parts.length < 3) {
             throw new ProtocolError("Invalid legacy status string");
         }
 
-        this.motd = parts[0];
-        this.setPlayerCount(parseInt(parts[1]))
-            .setMaxPlayers(parseInt(parts[2]));
+        let maxPlayers = parseInt(parts.pop());
+        let playerCount = parseInt(parts.pop());
+        this.motd = parts.join("§");
+
+        this.setPlayerCount(playerCount)
+            .setMaxPlayers(maxPlayers);
         return this;
     }