1. Open a private installation
Extract the complete download, then open Game/Wildhaven.rbxl in Roblox Studio. Publish a new experience under the account or group that will operate your game. Keep this copy private while you configure it.
The archive contains the editable place, sources, setup instructions, licence, third-party notices and a checksum manifest. If an advertised file is missing, contact us through Patreon with your order reference and the file name.
2. Set characters to R6
This release's character movement scripts expect an R6 character. In Studio, open Avatar > Settings, open the three-dot menu, choose R6 Only, save and restart the playtest. The place file alone does not establish this experience-wide setting.
If the character is not animating and Output mentions waiting for Torso or RootJoint, check R6 first. Creature native pose animations are separate from player movement animations.
See Roblox's Avatar Settings documentation for the current interface.
3. Configure your IDs and test data
- Set a unique
DataStorePrefixinReplicatedStorage.TemplateConfig. Keep test and production prefixes separate. - Set your
GroupIDand administrator UserIds inReplicatedStorage.Configuration.General. GroupID zero leaves the group reward disabled. - Use your own monetisation IDs in
ReplicatedStorage.Configuration.ProductsandConfiguration.Passes. The supplied commercial IDs are zeroed, so purchases remain disabled until you configure them.
Keep a record of production settings. Changing the data prefix later means your game will look in a different set of saved records.
4. Check assets under the actual owner
Play the published private experience and inspect its output. Check creatures, meshes, images, audio and animations. An asset working in our account does not establish permission for a different experience.
Where necessary, upload the supplied source under your ownership and replace the relevant ID, or use a replacement that you have permission to use. Check each asset type's permission controls; an image or mesh privacy setting is not a universal fix for audio or animation access.
Roblox explains restricted assets and game permissions in its asset privacy documentation. Do not make your source package publicly redistributable just to resolve an asset-loading error.
5. Test a real leave and rejoin
- Join the private published experience using Roblox Player.
- Earn some Speed and money, then obtain a creature. Note the values and the creature's size.
- Leave the server completely and rejoin. Compare your progress.
- Check an equipped trail and an upgrade, then repeat with another test player before opening the game.
A Studio session using mock storage does not prove live persistence. A StudioAccessToApisNotAllowed message identifies the Studio API limitation. If you enable Studio API access for testing, use an isolated test experience and test data rather than your live players' records.
See the official Roblox data stores documentation. Our release checks confirmed live saved Speed, money and a creature with its size; additional progression passed an isolated save/reload check.
6. Run the player-facing checks
- Steal and carry an egg, escape a guardian, return to your pen and hatch it.
- Check training, upgrades, trails and the Pet Index.
- With two players, test bat and trap interactions outside the safe zone.
- Check your own purchase IDs and group reward settings.
- Test on your target phones, screen sizes and input devices.
The video demo uses showcase progress and shorter recording timers. Those demo balances and recording scripts are not included in the buyer package. Physical-phone gameplay and a paid checkout/download test remain unverified by us.
Before buying
This is a development template for Roblox Studio, with editable source files and a one-experience commercial licence. You supply your own account setup and test the result. Review the gameplay, included formats, licence and support terms before checkout.