Skip to main content
The connector is a server-only Roblox integration. It currently sends heartbeats, attendance intervals, and in-game report submissions.

​
Files

​
Credential scope

Credentials are scoped to a Roblox universe ID. Ingress rejects:
  • A different universe ID.
  • A revoked credential.
  • An invalid HMAC signature.
  • A timestamp more than 120 seconds from the server window.
  • A malformed or replayed event outside the idempotent contract.

​
Signature contract

HMAC covers the exact JSON request bytes. Do not parse and re-serialize the payload between signing and sending. Each event includes a unique event ID and timestamp. Retries preserve the same event ID. This lets ingress acknowledge a repeat without creating duplicate attendance or reports.

​
Attendance contract

  • EVENT_ID is the Rodyne event UUID.
  • The event’s configured universe must match the credential.
  • Player.UserId observed by the server is authoritative.
  • Overlapping intervals are merged.
  • Presence and duration do not encode a pass result.

​
Report contract

Requirements:
  • Both arguments are current server Player objects.
  • The reporter comes from Roblox’s server-side event context, never a client-provided numeric ID.
  • Title and description use the connector’s bounded input contract.
  • One submission per reporter is accepted every 30 seconds.
  • true acknowledges ingestion, not completion of asynchronous record creation.

​
Compatibility

Cmdr, Adonis, and HD Admin compatibility is not claimed until a version-specific installation has passed live verification. The connector does not execute those systems’ commands.

​
Rotation

Create a replacement credential, publish it, observe a recent heartbeat, then revoke the old one. Reversing that order can leave still-running servers unable to deliver.

​
Guided walkthrough

Rodyne Studio integration capability and credential status

The integration view is the operational counterpart to the connector protocol reference.

The screenshot above is from the live Rodyne product. Use it to orient yourself, but rely on the current record state and live provider checks when operating the workspace.

​
Operating procedure

1

Create a credential

Bind it to the intended universe and capture the one-time secret securely.
2

Build the canonical request

Use the exact method, path, timestamp, event ID, and raw body required by the signature contract.
3

Sign server-side

Calculate HMAC with the credential secret only in trusted server code.
4

Retry idempotently

Reuse the same event ID and payload for the same logical event.
5

Confirm heartbeat and events

Use Integrations and Activity to verify accepted, rejected, and replayed requests.

​
Acceptance checks

​
Failure recovery

A signature failure should be diagnosed from method, path, raw bytes, timestamp, and credential scope. Never log the secret or a reusable authorization header.

​
Continue the workflow

Install the connector

Architecture