From 1976377235e2dd8ca850fc2980c7a5221424192e Mon Sep 17 00:00:00 2001
From: legop3 <minecratfd8@gmail.com>
Date: Sat, 31 Oct 2026 13:45:12 -0400
Subject: [PATCH] allow admins to always leave rover canleaverover always
 admins

---
 server/src/services/roverManager/roverLifecycle.js | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/server/src/services/roverManager/roverLifecycle.js b/server/src/services/roverManager/roverLifecycle.js
index 59fe9608..4249c250 100644
--- a/server/src/services/roverManager/roverLifecycle.js
+++ b/server/src/services/roverManager/roverLifecycle.js
@@ -174,6 +174,8 @@ function createRoverLifecycle(deps) {
 
   function canLeaveCurrentRover(socket, options = {}) {
     const currentId = getPrimaryRoverForSocket(socket.id);
+    // Admins, including lockdown admins, can always leave their current rover.
+    if (isAdmin(socket)) return { ok: true, currentId };
     /*
       Leaving a rover is only risky when this socket is the last person attached
       to an undocked rover. The same rule is used for rover-to-rover switching