What Goes Where

Your Explorer after installing. Don’t rename anything.

Installation

Follow the steps in order.

1. Join the Prova Group

   You must be in the Prova group when you buy and when you sign in to your dashboard. Players in your game don’t need to join.

2. Buy the Game Pass

   One payment in Robux, from the Daily Quests page. The Game Pass is your proof of purchase.

   Then open your dashboard and create your licence key. It is shown once, so copy it somewhere safe. One key covers every system you own, in up to six of your experiences.

3. Download the Daily Quests File

   The Daily Quests arrives as one file, from the Prova Discord server. Save it somewhere you can find it.

4. Install Prova Core

   Once per experience, however many Prova systems you own. Core is free. Open View → Explorer and click the arrow beside ReplicatedStorage. If PROVA | Core is already there, skip this step.

   1. Download Prova Core from the Prova Discord server.
   2. In Explorer, right-click Workspace and choose Insert from File. Pick the Prova Core file.
   3. Among what it adds are two folders named PROVA | Core.
   4. Drag the one holding Constants, Core, Ed25519 and Log into ReplicatedStorage.
   5. Drag the one holding CoreServer and LicenseProvider into ServerScriptService.
   6. Delete anything left over, such as an empty model.

   Explorer

   ReplicatedStorage

   └─ PROVA | Core

   ServerScriptService

   └─ PROVA | Core

   Only one copy of Core. A second PROVA | Core stops every system with PC-002.

5. Add the Daily Quests Folders

   In Explorer, right-click Workspace and choose Insert from File. Pick the Daily Quests file. Among what it adds are three objects named PROVA | Daily Quests. Drag each one into its service.

   Add the Daily Quests Folders

   Drag this	Into
   The Folder holding README and Remotes	ReplicatedStorage
   The Folder holding QuestConfig	ServerScriptService
   The ScreenGui holding Quests and OpenButton	StarterGui

   Keep the names exactly as they are, and delete anything left over, such as an empty model.

6. Add Your Visit Areas

   Five standard quests ask players to visit a place. Each needs an invisible part covering that place. Add them, or delete those five quests from QuestConfig.

   1. Home → Part. Move and resize it to cover the place.
   2. In Properties: Anchored ticked, CanCollide unticked, Transparency 1.
   3. Right-click it → Rename, to exactly ShopArea, CafeArea, BrokenBridgeArea, RestockArea or StaffArea.

7. Choose Your Rewards

   Open ServerScriptService → PROVA | Daily Quests → QuestConfig. The standard quests reward Bananas and Hypes, which the system creates and saves for you. Rename them, or point rewards at your game’s own money.

   Your game already has money on the leaderboard, such as Cash? Don’t add it to CreateCurrencies. Use its exact name as a quest’s RewardCurrency instead.

   ServerScriptService/PROVA | Daily Quests/QuestConfig

8. Turn On Allow HTTP Requests

   Turn on Allow HTTP Requests and click Save. Without it the licence can’t be checked and Core stops with PC-004. Already on if another Prova system works in this game.

   File/Experience Settings/Security

9. Add Your Licence Key as a Secret

   Publish your game first: File → Publish to Roblox. Then, in a web browser, open create.roblox.com, click your experience, and in the left menu choose Secrets → Create Secret. Fill in all three fields exactly.

   Already done for another Prova system? Skip this step. Lost your key? Rotate it on your dashboard and paste the new one here.

   Creator Dashboard/Your Experience/Secrets/Create Secret

   Add Your Licence Key as a Secret

   Field	Type
   Name	prova_licence
   Secret	Your licence key
   Domain	api.withprova.app

10. Publish and Check the Output

    Publish and join your game. Press F9 to open the Developer Console and choose the Server log. When the Daily Quests works, you see these lines.

    In the game, a square quest button appears on the left of the screen. Click it: the Daily Quests window opens with three quests and a countdown.

    Testing in Studio instead? Open View → Output. A normal Play can’t read the published secret, so add a Local Secret named prova_licence with your key under File → Experience Settings → Security, or use a Team Test.

    Output

    [PROVA | Core] v0.2.0 starting.

    [PROVA | Core] Daily Quests v1.0.1 registered.

    [PROVA | Daily Quests] v1.0.1 ready. 26 quests loaded.

    [PROVA | Core] Licence confirmed.

Quest Types.

Each quest in the Quests list has a Type. Some types need one extra field.

Settings

All settings are in one file. Change a value, then publish.

Daily Quests

Rewards

The Window

Saving

Purchases and Output

Quests

Each quest is one line in curly brackets, followed by a comma. Every Title must be different.

Troubleshooting

Open Output and look for lines starting with [PROVA |. All PC- codes are also on Error Codes.

Notes