agentleFS
rodrigo-guerraarodrigo-guerraa/roblox-hub/skills/vendored/roblox-monetization/SKILL.md

roblox-monetization

Skill2 starsChanged 30 days agoMITView on GitHub

Roblox purchase correctness: Game Passes, Developer Products, receipts (ProcessReceipt / BindReceiptHandler), subscriptions, private servers, Robux transfers, PolicyService and paid-random-item odds disclosure. Use when adding, changing, debugging or auditing purchases: a purchase not granting or double-granting, receipt bugs, pricing, shop offers, Robux prompts, refunds or make-goods, and paid random item policy.

4 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test failed/duplicate grants, absent players and interrupted saves.

    line 21
  2. Distinctive:

    If currency can be bought with Robux, every roll paid with that currency is a paid random item, as are Robux shortcuts into a roll and …

    line 26
  3. Very specific:

    Read PolicyService:GetPolicyInfoForPlayerAsync(player).ArePaidRandomItemsRestricted on join (retry.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Roblox monetization

Where this conflicts with the roblox-lessons skill, roblox-lessons wins (see its references/monetization.md).

When to use

Adding a Game Pass, Developer Product, subscription, private server, Robux transfer, Creator Rewards-related product decision, or purchase eligibility check.

Quick reference

  • Prompt purchases from the client; grant value only from server-owned code.
  • Passes: one server-owned ID-to-benefit registry; join and in-session purchase run the same idempotent benefit path. A failed ownership query is "unknown", never "does not own". Full.md §2a.
  • Developer Products: repeatable consumables. Exactly one receipt owner per server. ProcessReceipt still works; BindReceiptHandler (with Enum.ReceiptType.DeveloperProduct) is a newer alternative. PromptProductPurchaseFinished is not purchase confirmation.
  • Dedupe by PurchaseId stored in the player's own session-locked save, written together with the grant. Return NotProcessedYet whenever the grant cannot happen (player gone, data not loaded, nothing to grant, policy-blocked).
  • Creator Rewards is a platform program, not a grant API.
  • Test failed/duplicate grants, absent players and interrupted saves. Transfers, subscriptions and dynamic pricing: full.md.
  • A receipt handler's presence is not proof of correctness; inspect ownership, durable idempotent grant, and retry paths.

Paid random items

  • If currency can be bought with Robux, every roll paid with that currency is a paid random item, as are Robux shortcuts into a roll and odds-changing passes.
  • Disclose every outcome with its exact odds before purchase, computed by the same code the server rolls with, summing to 100%.
  • Read PolicyService:GetPolicyInfoForPlayerAsync(player).ArePaidRandomItemsRestricted on join (retry; a failed lookup counts as restricted).
  • Our default for restricted players (from roblox-lessons monetization.md): block Robux-to-currency products and Robux-to-roll shortcuts (UI notice plus the server refuses the receipt), do not sell odds-changing passes, and leave pass-only outcomes out of their rolls, so their currency is earned-only. Upstream instead suggests presenting Roblox's full list of treatments and avoiding blocking by default; consider those alternatives only when the owner asks for a different trade-off.

Purchase flows, receipts, subscriptions and failure tests: references/full.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.