You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Teaches you about best practice guidance on designing starter packs.
4
+
---
5
+
6
+
Starter packs are a type of item bundle offered to new players in an experience. By enticing players with useful items at a deeply discounted price, starter packs can increase [conversion](../game-design/analytics-essentials.md#monetization-metrics), a vital monetization metric that tracks the number of players spending money in a game.
7
+
8
+
According to industry benchmarks, games that implement a starter pack may see an **increase in revenue of 2-10% on average**. However, the revenue impact could be even higher, depending on how well a game monetizes already and the details of its starter pack's implementation.
9
+
10
+
The tips below are based on industry best practices and the Developer Excellence team's experience. Feel free to follow our suggestions, or design the starter pack that best suits your own game.
11
+
12
+
<Alertseverity="info">
13
+
For out-of-the-box functionality to sell collections of items to players at a discount, see the [Bundles Feature Package](../../resources/feature-packages/bundles.md).
14
+
</Alert>
15
+
16
+
## Availability
17
+
18
+
Because the starter pack is a monetization feature, it's recommended to make the pack available as soon as new players spawn for the first time. Gating access to the pack behind completion of a tutorial or first match, time spent in the game, or other restrictions, unnecessarily reduces the number of players who will see and ultimately purchase it.
19
+
20
+
Because they are priced at a significant discount, starter packs are single-time purchases; after a player purchases the bundle, it is no longer available to them. Players who spend once are more likely to spend again, though, which is why conversion is so important for a game's monetization.
21
+
22
+
In addition to being single-time purchases, starter packs are often offered to players for a limited time – from minutes or hours to several days – after which the pack is no longer available. The purpose of the timer is twofold: it creates additional incentive for players to make the purchase, and it ensures that the bundle doesn't outlive its usefulness.
23
+
24
+
Starter packs are designed to help new players jumpstart their experience, but they do not necessarily remain relevant past a certain point of progression; for example, 500 coins might be a significant amount of currency to a Level 1 player, but a trivial amount to a Level 10 player.
25
+
26
+
The [Bundles Feature Package](../../resources/feature-packages/bundles.md) allows you to define the timer that's best for your game. In general, it is preferable to give players time to make the decision to purchase rather than aggressively limiting its availability; we recommend between 24 hours and 3 days for most experiences.
27
+
28
+
## Surfacing
29
+
30
+
Surfacing refers to the discoverability of features in a game, or how easily players can find and access them. Some common and effective ways to surface a starter pack include:
31
+
32
+
- A dedicated button on the HUD that also displays the countdown timer, visible throughout the duration of the bundle's availability.
33
+
- Prominent featuring of the starter pack in the store, with the timer and discount clearly communicated.
34
+
- A popup modal dialog advertising the bundle. Some players feel that popups are aggressive, however, so use sparingly. Potential popup opportunities include when the player spawns into the game the last day the offer is available to them, when they level up, or when they lose a match in which the starter pack's items might have been helpful.
35
+
36
+
## Content
37
+
38
+
The content of each starter pack is different, depending on the items available in an experience. In general, they should be items that enhance a new player's experience by giving them a head start in the game. Common items include:
39
+
40
+
- In-game currency
41
+
- Resources
42
+
- Experience (XP) or other form of progress boost
43
+
- Powerups
44
+
- Exclusive cosmetic items like avatar clothing or auras/trails that can only be obtained in the starter pack
45
+
46
+
Try to choose 2-5 items that help players jump into the fun quickly and allow them to feel smart and special because they made the purchase.
47
+
48
+
## Pricing
49
+
50
+
The starter pack should be one of the best offers in the game, with **outsized and obvious value** to catch players' attention. Common price points include 99 R, 199 R, and 299 R – but anything less than 399 R ($5) would be a reasonable price targeting new players. The amount will depend on the contents and quantity of items in your bundle.
51
+
52
+
Whatever price you choose, **we recommend a discount of around 90%** to make value abundantly clear. For items like XP that aren't directly monetized, consider how much time it takes players to earn them and work backward to assign a value.
53
+
54
+
Beyond your starter pack, make sure that your game has sufficient **spend depth**, or a variety of purchasable content and price points, to appeal to spenders of all levels. Along with frequent content updates, this will help encourage any new payers converted by the starter pack to continue spending in your game. You can use the [Bundles Package](../../resources/feature-packages/bundles.md) to create item offers for this purpose, from permanent content packs to limited-time event bundles.
55
+
56
+
For more information on monetizing your experience, check out [Monetization Foundation](monetization-foundations.md).
"description": "The resource path for the role of the group member."
5769
5769
}
5770
5770
},
5771
-
"description": "A membership to a group. You can use a user ID instead of a membership ID.",
5771
+
"description": "A membership to a group. A user ID can be used in place of a membership ID.",
5772
5772
"x-resource": true
5773
5773
},
5774
5774
"GroupRole": {
@@ -6570,7 +6570,7 @@
6570
6570
"description": "Present when the task execution succeeds. Contains the output of the\n execution."
6571
6571
}
6572
6572
},
6573
-
"description": "A `LuauExecutionSessionTask` (\"task\" for short) executes a given Luau script\n in the context of a specific version of a place.\n\n In a task, physics simulation does not run. Server and local scripts within\n the place also do not automatically run.\n\n The script may access and update the data model of the place, including\n invoking any module scripts. However, data model changes are local to the\n task and cannot be persisted.\n\n The script can also invoke engine APIs that read and/or modify data stored in\n the cloud, such as those for DataStores. Exercise caution when using these\n APIs.\n\n Scripts can be up to 4 MB in size and run for up to 30 seconds. Scripts that\n run for longer than 30 seconds terminate with an error.\n\n Scripts are executed as-is and do not need to be wrapped in a function.\n\n Scripts can return values (using the Luau `return` keyword). Return values\n are serialized to JSON and can be retrieved with the `Get\n LuauExecutionSessionTask` API after the task completes. The total size of the\n return values after JSON serialization must not exceed 4 MB. If the limit is\n exceeded, the task terminates with an error.\n\n If the script raises an unhandled error, the task terminates. The error\n information can be retrieved with the `GetLuauExecutionSessionTask` API.\n\n Standard output (generated by the Luau `print` function) can be retrieved\n with the `ListLuauExecutionSessionTaskLogs` method after the task completes.\n A maximum of 450 KB of logs are retained. If the amount of logs exceeds the\n limit, older logs are discarded.\n\n Information about a task is retained for 24 hours after task completion.\n\n At most ten incomplete tasks are allowed per place. Attempting to create more\n tasks while the first ten are incomplete results in a HTTP 429 response.",
6573
+
"description": "A `LuauExecutionSessionTask` (\"task\" for short) executes a given Luau script\n in the context of a specific version of a place.\n\n In a task, physics simulation does not run. Server and local scripts within\n the place also do not automatically run.\n\n The script may access and update the data model of the place, including\n invoking any module scripts. However, data model changes are local to the\n task and cannot be persisted.\n\n The script can also invoke engine APIs that read and/or modify data stored in\n the cloud, such as those for DataStores. Exercise caution when using such\n APIs.\n\n Scripts can be up to 4 MB in size and run for up to 30 seconds. Scripts that\n run for longer than 30 seconds terminate with an error.\n\n Scripts are executed as-is and do not need to be wrapped in a function.\n\n Scripts can return values (using the Luau `return` keyword). Return values\n are serialized to JSON and can be retrieved with the `Get\n LuauExecutionSessionTask` API after the task completes. The total size of the\n return values after JSON serialization must not exceed 4 MB. If the limit is\n exceeded, the task terminates with an error.\n\n If the script raises an unhandled error, the task terminates. The error\n information can be retrieved with the `GetLuauExecutionSessionTask` API.\n\n Standard output (generated by the Luau `print` function) can be retrieved\n with the `ListLuauExecutionSessionTaskLogs` method after the task completes.\n A maximum of 450 KB of logs are retained. If the amount of logs exceeds the\n limit, older logs are discarded.\n\n Information about a task is retained for 24 hours after task completion.\n\n At most ten incomplete tasks are allowed per place. Attempting to create more\n tasks while the first ten are incomplete results in a HTTP 429 response.",
![rbx-open-source-docs[bot]](https://avatars.githubusercontent.com/in/357490?v=4&size=40){kind=avatar}
0 commit comments