From bfbd4ff8bc53904fd2737ec1d71e4a2bc9865b7a Mon Sep 17 00:00:00 2001 From: Joshua Goins Date: Sun, 20 Jul 2025 08:40:16 -0400 Subject: [PATCH] Remove branching policy, add documentation about tags I think I want branches to be used for new expansions - for example once Dawntrail is superseded then it will be moved to a branch called 7.0. Major/minor patch versions are now treated equally, basically every time the game version is bumped a new tag is created. I have created tags for the previously supported patches now. I also clarified that these are moreso for "historical" purposes and you shouldn't have any expectations of it building or working. If you're determined enough, I'm sure you can make it work. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0de6c50..bded8b5 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,7 @@ Also please don't use Kawari to spoil new or unreleased content, thanks. ## Supported Game Version -Kawari currently supports patch **7.25h3** (2025.06.28.0000.0000.) Kawari will never "roll back" to a previous patch. There are other servers (e.g. Sapphire) that support older versions of the game. As Kawari moves to a new major patch, the previous patch is moved to a branch (e.g. 7.1) These branches are for archival: effectively unsupported, but still useful. +Kawari currently supports patch **7.25h3** (2025.06.28.0000.0000.) Previously supported patches are provided on as tags (e.g. `2025.02.27.0000.0000`.) These may or may not function or build correctly, the tag is moreso a historical marker. Only the Global region is supported. Only the Windows client is supported. Supporting other regions or clients are currently out of scope of this project, but might work anyway.