From 084cae679ef2e98c8513baafff1e76f39d30d2f2 Mon Sep 17 00:00:00 2001
From: zx <109937991+asdfzxcvbn@users.noreply.github.com>
Date: Sat, 22 Mar 2025 13:08:48 -0400
Subject: [PATCH] docs: clarify offline.bnk patching

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0bf7b85..acf2de6 100644
--- a/README.md
+++ b/README.md
@@ -39,7 +39,7 @@ If the tweak is unable to find a song or process the lyrics, you'll see a "Could
 
 ## How It Works
 
-**Starting with version 4.0, EeveeSpotify intercepts Spotify requests to load user data, deserializes it, and modifies the parameters in real-time. This method is the best so far and works incredibly stable.**
+**Starting with version 4.0, EeveeSpotify intercepts Spotify requests to load user data, deserializes it, and modifies the parameters in real-time. This method is the best so far and works incredibly stable, so the below explanation is no longer valid for v4.0 and later.**
 
 Upon login, Spotify fetches user data and caches it in the `offline.bnk` file in the `/Library/Application Support/PersistentCache` directory. It uses its proprietary binary format to store data, incorporating a length byte before each value, among other conventions. Certain keys, such as `player-license`, `financial-product`, `streaming-rules`, and others, determine the user abilities.