使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/tabooharmony/roblox-brain --skill roblox-monetization開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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
ProcessReceiptorBindReceiptHandlerwithEnum.ReceiptType.DeveloperProduct.PromptProductPurchaseFinishedis 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
PolicyServiceand 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.
