Skip to content

SCARS v1.2-stable (November, 29 2025)

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Nov 00:16
· 3 commits to main since this release
v1.2-stable
e12c408
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

🚀 What's Changed?

✨ Major Improvements

  • Fully rewritten connection monitoring logic for faster and more accurate detection.
  • UDP traffic checks are now significantly faster and more reliable on both Windows and Linux.
  • Grace period logic redesigned to avoid false failures during slow GMod startup or heavy addon loading.
  • More consistent handling when the server is offline, preventing unnecessary patch cycles.

🛠 Patch Tool Enhancements

  • Windows now uses a subprocess-based runner with live console output instead of pexpect.
  • Linux patch execution improved with better stale-PID cleanup and more robust error handling.
  • Auto-update logic for GModPatchTool is now more accurate and resilient.
  • Smarter detection and cleanup of leftover or zombie patcher instances.

🔧 Improved Recovery Logic

  • Clearer differentiation between:
    • Server offline
    • GMod running but disconnected
    • GMod not running
  • Better detection of scenarios where GMod launches but closes before connecting.
  • Longer launch grace window (45 seconds) prevents premature relaunch attempts during heavy loading.
  • Reduced unnecessary validation cycles by tracking post-patch success states more precisely.

🧹 Code Quality & Maintenance

  • Replaced the single DEBUG flag with a new multi-level debug system (DEBUG_LEVEL = 0–3).
  • Cleaned and standardized all log messages for readability.
  • Simplified internal state tracking and flow control.
  • Improved folder detection, archive extraction, and patch-tool auto-locating behavior.

🧩 Safety Improvements

  • Added a lightweight, non-intrusive cooldown to avoid repeated validation attempts during extreme external outages.
  • This safeguard rarely triggers and does not affect normal reconnect behavior.
  • Example: During a Steam or VAC outage where validation cannot complete, the script pauses recovery attempts briefly to avoid hammering Steam.

Thanks for using the Swamp Reconnect Script!
If you encounter issues or want to suggest features, feel free to open an issue or pull request.

Assets 5
Loading