BlueSage QoL Tweaks - Beta
ACTIVE DEVELOPMENT / EARLY TESTING
This mod is still young. Expect issues, rough edges, and frequent re-uploads while BlueSage keeps tuning it.
Install this if you are okay with an early-development QoL toolkit that may change quickly. We are testing internally first and will ask for broader feedback only if we hit a blocker.
Should I Use This?
Use this if you want one BlueSage-flavored beta patch for several common On-Together QoL needs, instead of stacking a bunch of older overlapping mods:
- memory cleanup help for long sessions;
- host-only lobby health checks every 5 minutes for long-running rooms;
- longer ID/profile, room-name, and chat-box text;
- local leave notifications;
- optional chat timestamps;
- safer reconnect behavior for players who crash or accidentally disconnect, including a small BlueSage chat phrase after it brings you back.
This is meant for players and hosts, not just lobby hosts.
If you already use older QoL mods for these features, you can try disabling them and using this instead. BlueSage QoL is meant to be a clean beta replacement lane for those common tweaks, while still trying not to fight older mods if you keep them installed.
Players should leave reconnect on. Hosts can turn it off with EnableReconnectGuard=false because the host does not need to reconnect to their own room. Most features can be tested while hosting; reconnect testing is better from a normal player client joining someone else's room.
This is not the big-lobby host patch. For larger lobbies, use BlueSagePatched PlayerLimitLift on the host.
Host Health
BlueSage includes a host-only health monitor for long-running lobbies. Clients do nothing here; they only benefit if the host's room stays joinable and names stay healthy.
Every 5 minutes, the host checks the current lobby state inspired by AndrewLin Desync's H1-H5 notes:
- H1 Lobby Metadata: refreshes a small Steam lobby heartbeat timestamp when possible.
- H2 Host Identity: detects when the host appears to own the lobby but no tracked player has a server/host flag, then warns the host.
- H3 Host Missing From Player List: detects when the Steam lobby owner is missing from the player list, then warns the host.
- H4 Persona Cache: asks Steam to refresh player persona/name info when the host name looks empty.
- H5 Long-Running Delist Risk: warns after long uptime when everything looks healthy but new joins may still fail because Steam delisted the lobby.
BlueSage does not fabricate player-list entries or patch PurrNet RPC/packet serializers for this feature. If Host Health warns about H2, H3, or H5 and new players cannot join, the safest fix is still to recreate the lobby.
Compatibility
BlueSage tries to play nicely with other community mods.
- BlueSage Sweep is on by default and runs about once an hour. If you already prefer AndrewLin Sweep, turn BlueSage Sweep off with
EnableAutoSweep=false.
- If Simple_QOL or ChatTweaks-style mods are loaded, BlueSage timestamps and leave notices disable themselves by default.
- If AndrewLin Reconnect is loaded, BlueSage uses its safer reconnect handling instead of letting both reconnect loops fight each other.
- Old
.old, .bak, .disabled, or .dll.disabled files are ignored unless BepInEx actually loads them.
- BlueSage QoL does not require AndrewLin Alpha, jaide CommandAPI, or jaide CommandTypeahead in this beta. That is intentional so the first beta stays simple and dependency-light.
- BlueSage includes its own small internal command core for
/bsqol and /qol help/status commands.
- Host Health is host-only. Client installs do not run lobby repair; clients only benefit from a healthier host lobby.
BlueSage only checks mods BepInEx actually loaded.
BlueSage does not delete, rename, edit, or disable another creator's mod files.
Reconnect Safety
BlueSage includes its own simple reconnect safety loop. This is real built-in reconnect handling, not only a detector for AndrewLin Reconnect. AndrewLin Reconnect is not required.
Reconnect is for accidental disconnects, crashes, and flaky lobby hiccups. It is not meant to bypass a host's decision to remove someone from a room.
If AndrewLin Reconnect is installed too, BlueSage steps in first and uses the safer BlueSage timing so both mods do not rapid-fire reconnect at the same time.
Hosts can turn this feature off with EnableReconnectGuard=false. The game host does not need to reconnect to their own lobby.
Host-kick style disconnects do not auto-reconnect by default. If a tester deliberately wants BlueSage to treat those like accidental disconnects, they can opt in with ManageHostKickReconnect=true, but normal public testing should leave it off.
After a BlueSage auto reconnect succeeds, it waits 3 seconds for the game to finish loading back in, then sends a short in-game chat phrase:
Auto Reconnected by BlueSage QoL Tweaks - Thank you Blue <3
If chat is not ready after that delay, BlueSage falls back to a local notification. That is how testers can tell it was BlueSage reconnect, not AndrewLin Reconnect.
Default behavior:
- retries every 60 seconds;
- stops after 300 guarded cycles;
- blocks unsafe config edits, so
1 second becomes 60 seconds and 1000 attempts becomes 300 cycles;
- only retries when the lobby shows at least
1/x players, unless you turn off RequireVisibleLobby.
During internal testing, host and client BepInEx logs help a lot. Before sharing logs anywhere public, remove anything personal such as account names, private file paths, IP addresses, tokens, or anything you would not want strangers to see.
Config
Launch once, then edit:
BepInEx/config/com.bluesage.ontogether.qoltweaks.beta.cfg
Useful settings:
EnableAutoSweepEnableHostHealthMonitorMonitorIntervalSecondsEnableLeaveNotificationsEnableChatTimestampsEnableReconnectGuardRetryIntervalSecondsMaxAttemptsRequireVisibleLobbyManageHostKickReconnectEnableReconnectAnnouncementReconnectAnnouncementMessageReconnectAnnouncementDelaySeconds
ChatLimitRemover is always on. There is no normal toggle to mess with; it raises likely in-game chat inputs and lifts the vanilla 250-character send cap to the configured MaxChatCharacters value.
For early testing safety, MaxChatCharacters defaults to 500 and is clamped to 1000. Existing config files keep their old value, so if you tested an earlier build and see MaxChatCharacters = 1000, change it to 500 or delete the config and relaunch to regenerate it.
Commands
These are local BlueSage commands. They do not require CommandAPI, CommandTypeahead, or Alpha.
/bsqol/qol/bsqol status/qol status/qol hosthealth
Unknown slash commands are left alone so the game or other command mods can handle them.
Install
Install with a mod manager, or place the DLL here:
BepInEx/plugins/BlueSage_QoL_Tweaks_Beta/BlueSage_QoL_Tweaks_Beta.dll
Credits
Made by BlueSage for the On-Together community.
Source credits and mod links are in CREDITS_AND_SOURCES.md.
