LiveOps Goblin
Why it exists
LiveOps Goblin turns rewards, streaks, quests, shops, events, promo codes, progression, analytics, and safety contracts into a configurable creator layer for Roblox games.
Real product evidence
From owner controls to creator-facing runtime.
Delivery pipeline
Admin to config to Rojo to Roblox.
- 01
Configure privately
Choose a real game and environment, then define only the systems and content intended to ship.
- 02
Validate contracts
Check schedules, reward shapes, economy limits, product mappings, and production readiness before export.
- 03
Build the package
Generate versioned Luau configuration, checksums, manifests, documentation, and support evidence.
- 04
Map with Rojo
Combine the reusable package with game-local server, client, and generated configuration source.
- 05
Run in Roblox
Server services validate intent and grant rewards; clients render approved state and feedback.
One product, four delivery layers
Private operating application
Laravel and Vue provide game profiles, environments, LiveOps editors, content catalogs, package exports, diagnostics, audits, and owner documentation.
Reusable runtime kit
Rojo-friendly Luau modules cover configuration, rewards, quests, shops, events, analytics hooks, datastore patterns, and server-side safety.
Configuration builder path
Validated admin configuration becomes stable generated Luau rather than hand-edited operational tables or invented live data.
Human support layer
Creator installation, troubleshooting, submission, release, and support documentation are part of the completed product package.
Configurable systems
Retention mechanics become governed infrastructure.
- 01Daily rewards and login streaks
- 02Quests and reward calendars
- 03Rotating shops and timed events
- 04Promo codes and progression tracks
- 05Economy limits and currency sinks
- 06Datastore and receipt safety
- 07Entitlement and subscription mapping
- 08Analytics event contracts
- 09Creator-facing UI templates
Reward boundary
The client asks. The server decides.
- 1
Player intent
The client requests an action, never a reward amount.
- 2
Remote boundary
Schemas, ownership, eligibility, and rate limits are checked.
- 3
Server authority
Reward, entitlement, economy, and event rules resolve on the server.
- 4
Durable state
Datastore and receipt paths use bounded, idempotent writes.
- 5
Public result
The client receives sanitized state and analytics use consistent event contracts.
Current status
Package-ready. Publishing remains external.
- Private admin application and branded production build
- Roblox package source and downloadable package export
- Stable package entry point and game-local LiveOps bridge
- Creator docs, owner docs, diagnostics, support bundle, and submission assets
- Rojo build and Roblox Studio smoke-test workflow
- Creator Store review, approval, and listing performance
- Roblox account publishing and real universe/place assignment
- Real product, pass, subscription, badge, and analytics identifiers
- Account-level final verification and live purchase testing
Flagship proof environment