From 195e9e749e17ac8b4227a0e772f560f8dd85ae95 Mon Sep 17 00:00:00 2001
From: Alex Laslavic <alexlaslavic@rubedolife.com>
Date: Sat, 29 Aug 2026 17:12:13 -0700
Subject: [PATCH] fix DOORSTOP_TARGET_ASSEMBLY in run.sh

I had to remove
```DOORSTOP_TARGET_ASSEMBLY="$additional_path/$DOORSTOP_TARGET_ASSEMBLY"```
from run.sh to get unity doorstop to properly inject ModTek.  Not sure why, but the injection of $additional_path was not necessary, and prevented doorstop from finding the assembly.

Apple M5 Pro
Tahoe 26.5.2

More details:
* Running native BT through GOG
* installed BTA using wine
* doorstop did not hook in ModTek
* I did some fussing around
* splashed the latest ModTek release on top of the BTA install
* altered run.sh as described
* now everything works
---
 ModTek.Preloader/run.sh | 1 -
 1 file changed, 1 deletion(-)

diff --git a/ModTek.Preloader/run.sh b/ModTek.Preloader/run.sh
index a6ebd26..80286fd 100755
--- a/ModTek.Preloader/run.sh
+++ b/ModTek.Preloader/run.sh
@@ -94,7 +94,6 @@ case ${os_type} in
     contents_path="$(dirname "$BASEDIR")"
     app_dir="$(basename "$(dirname "$contents_path")")"
     additional_path="$app_dir/Contents/Resources"
-    DOORSTOP_TARGET_ASSEMBLY="$additional_path/$DOORSTOP_TARGET_ASSEMBLY"
     DOORSTOP_MONO_DLL_SEARCH_PATH_OVERRIDE="$additional_path/$DOORSTOP_MONO_DLL_SEARCH_PATH_OVERRIDE"
 
     # guess executable path if launched without specifying an executable