mcpField
R
roblox-monetization

roblox-monetization

github.com/tabooharmonyDevelopment1382.0k installsUpdated 2w ago
Repository

About roblox-monetization

roblox-monetization is a skill for developers adding purchases and monetization-related features to Roblox games. It explains server-owned grants, receipt handling, eligibility checks, and failure cases.

Key features

  1. 01Handle passes and product grants
  2. 02Use server-owned receipt handlers
  3. 03Check purchase eligibility policies
  4. 04Track Creator Rewards separately
  5. 05Test duplicate and interrupted grants

Use cases

  1. 01Adding a Game Pass benefit
  2. 02Granting repeatable Developer Products
  3. 03Handling failed or duplicate purchase receipts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tabooharmony/roblox-brain --skill roblox-monetization

After installing, type/roblox-monetizationin Claude Code to confirm it loaded.

Bundled filesreferences/full.md

Details

From the project README

roblox monetization

When to Load

Load when adding a Game Pass, Developer Product, subscription, private server, Creator Rewards-related product decision, or purchase eligibility check.

Quick Reference

  • Prompt purchases from the client, but grant value only from server-owned code.
  • Passes: one server-owned ID→benefit registry; join and purchase refresh use the same idempotent benefit path. Full.md §2a.
  • Developer Products: repeatable consumables. Grant through a server-owned receipt handler, either ProcessReceipt or BindReceiptHandler with Enum.ReceiptType.DeveloperProduct. PromptProductPurchaseFinished is not purchase confirmation.
  • Failed receipts remain NotProcessedYet; retries depend on the chosen receipt API, not an invented timer. See full.md.
  • For eligibility-sensitive purchases, check PolicyService and current Roblox guidance. If a paid-random-item restriction applies, offer the user the documented choices, including earnable rewards, a known non-random sequence, or direct purchase. Do not default to hiding or blocking the feature; handle the affected purchase path without stopping unrelated work.
  • Creator Rewards is a platform program, not a grant API. Track eligibility, attribution, engagement, and dashboard reporting separately from purchases and inventory.
  • Test failed/duplicate grants, absent players, and interrupted saves. Transfers, subscription changes, and dynamic pricing: full.md.
  • A receipt handler's presence is not proof of correctness; inspect its ownership, durable idempotent grant, and retry paths for unknown products or absent players.

Need the details? Load references/full.md for purchase flows and failure handling.

Comments

Markdown supported