Cube Scripts

Cube Monitoring

Watch several players' screens at once in resizable windows, over WebRTC.

Live screen monitoring for FiveM staff. Open a player list, pick as many players as you want, and watch them all at once in draggable, resizable windows.

Media travels peer to peer. Your server relays the handshake and never sees a single frame, so bandwidth cost stays on the two clients involved.

Note

Any connected player can be watched without having the interface open. Frames come from the game backbuffer through a WebGL canvas, so nothing outside the game window is ever captured.

Features#

  • Multi-window watching - several live streams at once, each in its own

    window with drag, resize, minimize, maximize and edge snapping.

  • Player panel - searchable, sortable list of everyone online with live ping

    and a badge showing who is already being watched.

  • Screenshot - a single frame from a player's screen, saved locally or

    posted to Discord.

  • Framework aware - standalone with ace permissions, ESX and QBCore bridges

    included, detected automatically.

  • Localised - every string lives in locales/, English and French included.
  • Idle by default - the capture pipeline renders only while something is

    watching, so an idle client pays no framerate cost.

Escrow#

The resource is escrow protected. Several files are left open so you can adapt it to your server:

PathEditable
config.luaYes
shared/*.luaYes
locales/*.luaYes
client/function.luaYes
server/config.luaYes
server/bridge/*.luaYes
server/function.luaYes
web/No (compiled interface)
Tip

Need a change inside the interface? Open a ticket on our Discord - we take feature requests and can often ship them in the next update.

Security#

Webhooks and API keys live in server/config.lua, which is a server script. It is never sent to a client, so nothing in it can be extracted from a player's game files.

Danger

Never move a webhook or an API token into config.lua. That file is shared, which means every connected player receives a copy of it.

Requirements#

  • A FiveM server on a recent artifact
  • No dependencies - the resource is fully standalone
  • A TURN server is strongly recommended. See WebRTC.

Next steps#