Volaris UGC Catalog

Volaris UGC Catalog was a Roblox catalog and economy experience developed for Volaris UGC, a community with approximately 300,000 members.

The gameplay loop was intentionally straightforward: players earned in-game currency and used it to purchase available UGC items. My role was to build the scripting layer connecting currency progression, catalog availability, purchases, and persistent player data.

I worked as the systems scripter responsible for the core functionality behind the catalog experience. The project required the economy and purchasing flow to remain predictable, secure, and easy for players to understand.

• -In-game currency earning systems
• -Persistent player currency
• -Limited UGC earning mechanics
• -UGC purchase handling
• -Catalog availability checks
• -Server-side purchase validation
• -Player reward and ownership tracking

The central loop was built around earning currency and converting that progress into UGC rewards. While the player-facing idea was simple, the server still needed to verify every meaningful action.

The client handled the interface and purchase request, while the server remained responsible for checking the player’s real balance, validating the requested item, and applying the result.

Limited UGC rewards introduce additional constraints beyond a standard shop. Availability may change, rewards may have restricted quantities, and purchases must not succeed using outdated client information.

• -Validated whether a reward was still available
• -Checked the player’s authoritative currency balance
• -Prevented repeated or invalid purchase requests
• -Updated player data only after successful validation
• -Kept catalog state and player-facing UI consistent

The client was never allowed to decide the price of an item or confirm that a purchase had succeeded. Each request was resolved against server-owned catalog data and the player’s saved profile.

This protected the catalog from modified clients attempting to submit fake prices, purchase unavailable items, or spend currency they did not own.

Building for a group of approximately 300,000 members meant the project was attached to an existing audience rather than being developed in isolation. The experience needed a clear onboarding flow and reliable systems that could support players arriving specifically for UGC opportunities.

The project strengthened my experience with reward-focused Roblox experiences, especially where progression, purchases, and limited item availability all intersect.

The original experience is no longer publicly available, so there is no active game link or gameplay video included with this case study.

This write-up documents my technical contribution and the production systems I implemented while the project was active.