Thank you for the rest of your feedback as well! We do want users to be able to customize as much of the packages as they want – with the packages being a great starting point if you want to add/replace/customize anything (especially if your experience has its own UI)
If you could re-insert the latest version of the package it should work as expected!
In your video, the MissionsExample script had some extra code to show how the SeasonPasses package can award season XP on mission completion. This code has been removed and is instead only included as part of the SeasonPass documentation.
It did indeed work also does this package come with some basic missions? Because i tried play-testing and ui wouldn’t update and i couldn’t get mission completed
After stopping the play-test in the studio i also found this error
On the Bundle package at least, it shows a lot of weird quirks that, from the actual UI in studio, seem to be issues from misuse of layouts and padding. I briefly annotated some of the issues I can see from a glance in the UI. Bit messy and not very readable since I was in a rush.
A settings menu that supports bools, strings, ranges, numbers, keybinds, enums, etc. That would be awesome, because settings can drastically improve the experience for players, which leads to more playtime and engagement. Built-in GRANULAR audio controls would be especially great, since Roblox games generally have awful audio balancing (with unimportant sounds often drowning out important sounds.)
Apologies for the confusion, @mlnitoon2. The documentation has been updated to reflect the recent name change to Feature Packages and should be easier to follow now.
Could we also get like premade scripts? that would be cool. Like scripts that would commonly be used in a game like for example, datastores and leaderstats.
I’m encountering an issue-
Once the player purchases the bundle, it doesn’t go away and will still show up for the rest of the session and any other sessions.
Hey! Did you set the config value in Bundles.lua “singleUse” to true? In the default example, it is set to false so it will keep showing up even after purchased.