Setup & Configuration
Before editing
- Keep a backup of your place and stop Play before editing persistent assets or scripts.
- Preserve the existing folder names — several controllers find assets by exact name.
- Publish the place under the intended owner before configuring purchases.
Configuration modules
| Module | Holds |
|---|---|
ReplicatedStorage.Shared.Config | Regions, Grass, Progression, Rebirth, TrainingZones, Index, SellLoot, Upgrades, Codes, ExclusiveShop, Auras, AutoClicker |
CutterConfig | Cutter catalog and attack settings |
CraftingConfig | Materials, relics, slots and crafting purchases |
Purchases
Review ProductIds and the product/pass references used by the individual catalogs. Use products belonging to the intended experience.
- Aura cash purchases — handled by
AuraService. - Robux purchases — request a product prompt and are fulfilled through the commerce service.
Startup check
Start one Play session after editing and check:
- The server bootstrap completes
- Grass appears
- E prompts open the nearby shops
- A cutter, a Strength reward, an aura switch and a respawn all work
Verify player data persistence separately in your published test environment — a restarted Studio session is not proof of saved progress.