ashexplained/roblox-skills

roblox-datastore-persistence

Design, implement, and review Roblox DataStore persistence.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-datastore-persistence

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Roblox DataStore Persistence

Goal

Save player progress reliably without corrupting or losing valuable state.

Schema Rules

  • Store compact canonical state, not UI state.
  • Include schemaVersion.
  • Keep defaults centralized.
  • Validate loaded data before using it.
  • Write migrations that can handle old, missing, or partial data.
  • Keep transient match/session state separate from permanent profile state.

Save Strategy

  • Load once when the player joins.
  • Keep an in-memory authoritative profile on the server.
  • Save on meaningful intervals and player leave.
  • Save on server shutdown with a bounded timeout.
  • Debounce rapid save requests.
  • Retry transient failures with backoff.
  • Mark dirty profiles and avoid unnecessary writes.

Valuable State

Treat these carefully:

  • Currency and premium currency.
  • Inventory, pets, cosmetics, boosts, quest progress, achievements.
  • Purchases and receipt-granted items.
  • Trading or gifting results.
  • Daily streaks and time-gated rewards.

MCP Review Workflow

  1. Use script_grep for DataStore, UpdateAsync, SetAsync, GetAsync, profile, save, and load.
  2. Read all persistence scripts with script_read.
  3. Map load, mutation, save, and shutdown flow.
  4. Patch with multi_edit.
  5. Playtest join/change/leave-like paths where possible and check get_console_output.

Output

Return:

  • Profile schema.
  • Save/load flow.
  • Migration plan.
  • Failure modes handled.
  • Manual tests still needed in published or multi-server conditions.

Next

Harden the save path against exploits with roblox-security-economy, then verify saves survive rejoin and shutdown with roblox-playtest-qa.

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills