fix: isolate PortMaster controller exit handling

scripts/portmaster/NETfishing.sh

@@ -29,6 +29,7 @@ fi
 
 CONFDIR="$GAMEDIR/conf"
 GAME_EXECUTABLE="$GAMEDIR/NETfishing.aarch64"
+GPTOKEYB_CONFIG="$GAMEDIR/netfishing.gptk"
 WESTON_DIR="/tmp/netfishing-weston"
 WESTON_RUNTIME="weston_pkg_0.2"
 HARBOURMASTER="$controlfolder/harbourmaster"
@@ -118,9 +119,10 @@ case "$PERFORMANCE_PROFILE" in
 esac
 
 # Keep NETfishing's native controller input separate from PortMaster's exit
-# handling. Without a -c mapping file, GPTOKEYB only watches for the
-# device-specific force-quit chord and does not inject gameplay inputs.
-$GPTOKEYB "NETfishing.aarch64" &
+# handling. Legacy GPTOKEYB builds can load their default keyboard map when no
+# config is supplied, so the explicit no-op map preserves only the
+# device-specific force-quit chord.
+$GPTOKEYB "NETfishing.aarch64" -c "$GPTOKEYB_CONFIG" &
 pm_platform_helper "$GAME_EXECUTABLE"
 
 $ESUDO env \

scripts/portmaster/netfishing.gptk

@@ -0,0 +1,40 @@
+# NETfishing reads the controller directly. GPTOKEYB is retained only for the
+# PortMaster force-quit chord, so every keyboard and mouse binding is disabled.
+
+back = \"
+guide = \"
+start = \"
+
+a = \"
+a_hk = \"
+b = \"
+b_hk = \"
+x = \"
+x_hk = \"
+y = \"
+y_hk = \"
+
+l1 = \"
+l1_hk = \"
+l2 = \"
+l2_hk = \"
+l3 = \"
+r1 = \"
+r1_hk = \"
+r2 = \"
+r2_hk = \"
+r3 = \"
+
+up = \"
+down = \"
+left = \"
+right = \"
+
+left_analog_up = \"
+left_analog_down = \"
+left_analog_left = \"
+left_analog_right = \"
+right_analog_up = \"
+right_analog_down = \"
+right_analog_left = \"
+right_analog_right = \"