RedM / FiveM documentation

Murphy’s Platform

Start here

Quick start

Connect a server, connect Discord, invite staff, and verify the first data.

Use this sequence for a new workspace. Complete the connection before configuring optional modules so each later page has real data to work with.

Bring the workspace online

  1. Create the workspaceSign in with Webba ID and choose FiveM or RedM.
  2. Install the resourceAdd `murphy_platform` to FXServer with the generated token.
  3. Confirm the first syncCheck the heartbeat, a player session, and Server Health.
  4. Connect DiscordAuthorize the bot and map the guild, channels, and roles.
  5. Invite staffAssign roles before giving the team access to live data.
  6. Open the daily queuesVerify Players, Tickets, Inventory, and Whitelist with real data.

Create the workspace. The selected platform type controls the compatible map and in-game integrations. The slug becomes part of the dashboard URL; the display name, logo, favicon, accent color, and language remain editable in Settings > General.

Install the server resource. Open Settings > Server Connection, copy the generated configuration into the murphy_platform resource, add it to server.cfg, then restart FXServer.

config.lua
Config = {}
Config.ResourceToken = "YOUR_RESOURCE_TOKEN"
Config.HeartbeatInterval = 60
Config.PositionSyncInterval = 3
Config.HealthSyncInterval = 60
Config.Debug = false
server.cfg
ensure murphy_platform

Never publish the real resource token. Treat it like a password for the server connection.

Connect Discord and staff. In Settings > Bot, authorize Murphy Bot and select the Discord server before deploying ticket or whitelist panels. In Settings > Staff and Settings > Roles, invite the team and start each person with the smallest permission set required for their work.

Know when setup is complete

The Dashboard should report the server as connected, Players should receive a session after someone joins, Server Health should update, and the Discord bot should resolve the configured guild and channels. Only then continue with monitoring, analytics, Tebex, the public site, API keys, webhooks, or connected Murphy plugins.

If one signal is missing, inspect that connection only: resource name and token for server data, bot permissions for Discord, or the assigned Platform role for a staff visibility problem.

Last updated: September 11, 2026