From 04f10a8f515c508788fef0612ad93c3e53b48f7d Mon Sep 17 00:00:00 2001
From: Reece Mackie <20544390+Rover656@users.noreply.github.com>
Date: Wed, 15 Apr 2026 21:43:48 +0100
Subject: [PATCH 1/2] chore: Update directory watcher and tell ProGuard to
 leave it alone

---
 gradle.properties | 2 +-
 proguard.conf     | 4 ++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/gradle.properties b/gradle.properties
index 329821a9..3b83546f 100644
--- a/gradle.properties
+++ b/gradle.properties
@@ -16,7 +16,7 @@ neoforge_version_range=[26.1.2.10-beta,26.2-)
 # Third party dependencies
 #########################################################
 snakeyaml_version=1.33
-directory_watcher_version=0.17.1
+directory_watcher_version=0.19.1
 junit_version=5.13.4
 flatbuffers_version=23.5.26
 ffmpeg_version=6.0-1.5.9
diff --git a/proguard.conf b/proguard.conf
index ee5d9127..911d5ef9 100644
--- a/proguard.conf
+++ b/proguard.conf
@@ -25,3 +25,7 @@
 -keepclassmembers class guideme.internal.hooks.mixins.* {
     *;
 }
+
+-keep class guideme.internal.shaded.methvin.** {
+    *;
+}

From f28b1a232e7ec1cc71d8049c76448a80df7f033b Mon Sep 17 00:00:00 2001
From: Reece Mackie <20544390+Rover656@users.noreply.github.com>
Date: Tue, 28 Apr 2026 23:50:56 +0100
Subject: [PATCH 2/2] chore: Specifically only keep the JNI package members
 untouched by ProGuard

I attempted just constructors, but further funky errors were caused as a result - seems safest to just prevent the JNI package from being trimmed
---
 proguard.conf | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/proguard.conf b/proguard.conf
index 911d5ef9..f4ea8272 100644
--- a/proguard.conf
+++ b/proguard.conf
@@ -26,6 +26,7 @@
     *;
 }
 
--keep class guideme.internal.shaded.methvin.** {
+# Ensure all JNI classes for DirectoryWatcher are kept to ensure hot reload works on MacOS
+-keep class guideme.internal.shaded.methvin.watchservice.jna.* {
     *;
-}
+}
\ No newline at end of file