[Beta] New Feature Packages: Season Pass & Engagement Rewards

[UHT_milkX (UHT_milk)]

I want to try Engagement Rewards Package. I put both packages [FeaturePackagesCore] and [EngagementRewards] in the ReplicatedStorage as recommended. I run it with your sample data and it seems to work but have a lot of warnings in ScriptAnalysis Window. there are 88 Type Errors in the scripts of these packages. can I do something to fix it?

[Nightriff]

You can disable the analysis warnings by changing the first line of the file from --!strict to --!nonstrict.

One way to do this for all affected files is do a search all ctrl/cmd + shift + f, click the dropdown, and enter the replacement strings.

You can Replace All for a nuclear approach, or you can click through each result and check for orange analysis warnings on the scroll bar in the file and do a single replacement for each file with warnings.

[yan3321]

Hi devs,

We recently encountered an issue in our production game Lebuhraya while using the official Season Pass Package (Beta) . We found that players were sometimes unable to claim season pass rewards in public servers, although it worked correctly in private servers and during solo testing.

The issue

After investigation, we discovered that the in-script cache for claimedRewardIdsState (and potentially trackState which caches premium pass ownership) appeared to be global rather than per-player. This meant that once a reward was claimed by any player in a server, or a premium status was cached, it could affect the state for all other players in that same server instance. This behaviour isn’t easily noticeable during private testing due to the low player count.

Our solution

We modified the server-side SeasonPasses script to make these caches player-specific. This typically involves changing the cache tables from: local claimedRewardIdsState = {} :: { [Types.RewardId]: boolean } to something like: local claimedRewardIdsState = {} :: { [number]: { [Types.RewardId]: boolean } } (where the number is player.UserId )

And then updating all logic that reads from or writes to these caches to use the player.UserId as the primary key. We also ensured these player-specific cache entries are cleared when a player leaves the game to prevent memory leaks.

This kind of issue can be tricky to debug because it often only manifests in live, multi-player environments.

We wanted to share this finding in case other developers using the package might encounter similar problems or to help the team refine the package for future updates. The Season Pass Package is a great resource, and hopefully, this information can help make it even more robust.

Thanks!

[yieldlua]

The bundles feature package download link is not working: https://create.roblox.com/store/asset/72975253516300/Bundles-Feature-Package

---

---

Creator Documentation page for the Bundles feature package:

Bundles package | Documentation - Roblox Creator Hub

[Nightriff]

There was an issue where this page was referencing the wrong asset ID, but it was fixed in March. Thanks for letting us know!

[yieldlua]

The link/asset ID on the Creator Documentation has not changed, it’s still: https://create.roblox.com/store/asset/72975253516300

The asset is not visible, Distribution on the Creator Store being disabled may be the issue. If the issue comes from it referencing the wrong asset ID, can you send the right one?

[Nightriff]

Looks like this is a new issue, separate from the previously incorrect ID. We’re working on fixing the visibility of the packages, I’ll post again here once it’s fixed!

Update Jul 2 2025: All the packages are now restored again now.

Thanks again @yieldlua for reporting!