Skip to main content

What This Guide Covers

This guide is a future-contract example for a persistent multiplayer game loop:
  • express player-data loads and saves,
  • model inventory, quest progress, and level,
  • issue periodic contract-level save calls,
  • model awards and spends through Summer.economy.
There is no production gameplay runtime, persistence backend, economy rail, autosave, or backend flush for uploaded games today. This example is not executable proof of those services. See platform capability status.

Input Actions Used

Configure actions in your project/manifest:
  • quest_complete
  • buy_potion

Complete Game Script (quest_arena.gd)

Suggested manifest.json