Roblox
Start and end shifts, optional Roblox checks, and shift records.
Shifts record when a staff member is on duty. They can optionally require a linked Roblox account and run verification or movement checks while the shift is open. Check timing is defined by the implementation — this page does not invent an interval.
/shiftStart, end, and review shifts./robloxLink the account used for verification./settingsShift module configuration.Run /shift and start a shift. If the server requires Roblox verification, Oxy will refuse to start until a verified link exists. Starting writes a shift record for the current member.
End the shift through /shift when you go off duty. The record should close with an end time. If a shift is left open, your server’s configuration decides whether it stays open, auto-closes, or flags staff — that behaviour is version-specific.
When enabled, Oxy uses the linked Roblox account as part of the shift. That can include confirming the account is in a required experience or passing a movement/verification check. Members without a verified link cannot start a shift in servers that require one.
Verification checks can run periodically while a shift is active. The exact interval, the definition of movement, and the failure behaviour (warn, log, auto-end) are not documented as fixed values here because they belong to the installed configuration. Review /settings → Shifts for the controls your version exposes.
Each shift is a record: who started it, when it started, when it ended, and any verification outcomes the module stores. Staff with permission can review records through /shift. Do not export records containing personal data to public channels.