Shop packs
Sell perks for tokens using Single or Collection packs. Shop packs come with various customizable purchase limits.
Shop Pack Types
There are two types of Shop packs:
Single
A Single Shop pack involves a single package, as the name suggests. There are no sub-packages within a Single Shop pack.
You can add existing Single packs to a Collection.
Collection
Group packages from the same category or with different quantities in Collections. Collections allow you to create sub-packages that can be purchased separately.
Create a Shop Pack
1. Click + Add Shop Pack
In the top-right corner of the Shop Pack Overview page, click + Add Shop Pack.
Enter a name in the popup, select the Type of Shop pack, and choose the game. Click Create to proceed.
2. Configure Settings
In the description field, summarize what is in the Shop pack. This description will be visible on the Community website.
If the selected game supports the in-game shop, you can also choose an in-game image. Learn more about all the Shop pack settings >.
3. Add Actions
Adding actions differs slightly between Shop pack types. The actions are similar to Task actions. Learn more about available actions >.
Single
The actions added here will execute when players purchase the Shop pack.
Collection
When creating a Collection, you must add actions to all sub-packages. Refer to Sub packages Collection for more information about managing sub-packages for Collections.
Sub-packages Collection
Add to Collection
Add New Sub-package
To add a new sub-package to your existing Collection, click Add Sub-package at the bottom of the Sub-packages page.
Convert Single to Collection Sub-package
Add an existing Single Shop pack to a Collection, such as when merging similar items into one Collection.
Click the icon on the Shop pack you want to add to a Collection, and then click Add to Collection.
Select the Collection to which the Single item should be added.
Settings, Pricing & Delivery
You can modify settings for each sub-package individually.
Click the icon on the right of each sub-package and select Settings or Pricing & Delivery to edit sub-package settings.
You can also click the title or badges for a shortcut to Settings or Pricing & Delivery.
Manage
To change the order of sub-packages, drag the icon up or down on the left side of each sub-package. Click the icon on the right to clone or delete a sub-package.
Shop Pack Settings
Pricing
Set the token price for each Shop pack or sub-package.
Set the token price to 0 to make the item free.
Labels / Filters
Labels can be used to highlight certain items and also serve as filters within the shop.
Label Example:
Purchase Limits
You can limit how often players can buy certain Shop packs or sub-packages from a Collection.
Options include:
- Allow unlimited purchases.
- Limit to once a year.
- Limit to one purchase per [X] day(s).
- Limit to [X] sub-packages per [X] day(s).
- Disable the package after it's been purchased by someone (single purchase limit).
Select Disable package when bought by someone (single purchase limit) to disable the Shop pack or sub-package for all players immediately after someone buys it.
Learn how to reset purchase limits >
Visibility
Control who can see the Shop pack or sub-package. This feature is useful for creating Shop packs that are visible only to players with a specific Custom Role (e.g., VIPs).
Hiding packages is useful when you need to create packages for specific purposes, like recovering in-game items or sending items to admins using manual delivery, without letting players buy them.
Offline Delivery
With offline delivery, actions will execute regardless of whether the buyer is online or not.
This is helpful for Shop packs or sub-packages that grant whitelist access. For example, players can't join the server until they are whitelisted.
Most in-game commands require the player to be online. Be sure to test Shop packs thoroughly when using Support offline delivery.
Character Level (Min/Max)
Require the buyer's character to be above or below a specific in-game level.
Setting a min/max level is useful for starter packs or advanced packs that should only be available for characters at higher levels.
Delivery Restrictions
Limit Shop packs or sub-packages to specific clusters or game servers.
You can also prohibit delivery on certain game servers, allowing you to restrict packages to specific clusters while excluding specific servers within those clusters.
Images
Set an image for the Shop pack or sub-package.
Website Image
Example:
In-game Image
In-game images are only supported for games that use the GSA Integration mod. In-game images reference image paths within the game files and do not support uploaded images.
Example:
Manage Shop Packs
To change the order of Shop packs, drag the icon up or down.
Click the icon on the right of each Shop pack to clone, delete or send it to a player.
Use the Visit shop button at the top-right to preview how your changes affect the shop.
Deliveries
When players buy Shop packs, the deliveries appear on the Deliveries page.
Manual Delivery
Test or manually send Shop packs to players by clicking + Create Delivery on the Deliveries page.
CSV tools
With the CSV tools, you can export Shop packs, modify them in programs like Excel, or edit them with an AI tool, and then re-import them.
The CSV export provides access to almost every Shop pack setting, which you can also manage on the dashboard
The CSV tools are only available on dashboards with any paid add-on.
Export
The export tool allows you to export one or multiple Shop packs (Single & Collection types) to a CSV file. You can then edit the CSV file using Excel or an AI tool.
On the Shop pack overview page on your dashboard, you can find the CSV export button in the top-right corner of the screen (see screenshot above).
Import
When you’re finished editing the CSV export, you can upload the CSV file again. While GSA is processing your CSV file, no changes can be made to Shop packs. This prevents any issues from overlapping.
On the Shop pack overview page on your dashboard, you can find the CSV import button in the top-right corner of the screen (see screenshot above).
CSV file details
Below is an example of a CSV export. Further down, you can read about the purpose of each column and how you can use it.
ID
Update existing items
When a number is entered in the ID field, it means an existing Shop pack should be modified. The number/ID refers to the existing Shop pack ID. When generating an export, the correct number is automatically filled in here.
Creating new items
When no number is entered in the ID field, a new Shop pack will be created upon import. You don’t need to provide a number for new Shop packs.
Parent ID
The Parent ID is used to indicate which Shop packs are part of a Collection. The Parent ID refers to the ID of the main item.
If you want to add new sub-items to an existing Collection using the CSV tool, you can enter the existing Collection’s ID in the Parent ID field for the new sub-items (see the top example in the screenshot below).
When creating a new Collection, it’s not possible to specify an existing Collection ID in the Parent ID field. In this case, you can use so-called "fake IDs". You can choose a number yourself, as long as it starts with fake-, and use it to link sub-items to the new Collection (see the bottom example in the screenshot below).
The "fake IDs" are only used during the import process. After import, these "fake IDs" are no longer stored. In a subsequent import, you cannot refer to a "fake ID" used in an earlier import. In that case, you can use the ID since the item has already been created.
APP ID
The APP ID column indicates which game the specific Shop pack is for. You can enter a STEAM ID here, but for non-STEAM games, alternative IDs are available. You can view these when exporting a Shop pack for the respective game.
Name
Enter the name of the Shop pack in the Name column. A Shop pack name must be at least 3 characters long.
Description
Depending on whether the specific Shop pack is a Collection or not, there are different requirements for the description.
Single
You can provide a description that uses Markdown styling.
Collection
For the main item of the Collection (also known as the parent), only plain text is allowed in the description. Additionally, the description can be a maximum of 245 characters long.
Label
The Label field is optional and can be used to assign a label to a Shop pack. Labels are used for filtering in the shop. You can specify only one label per Shop pack. The maximum length of the label is 25 characters.
Token price
In this column, you set the price of the Shop pack. Should the Shop pack be free? Then enter 0.
You can only enter numbers above 0.
Support offline delivery
If the specific Shop pack should also be delivered when the player is offline in-game, you can set that in this column.
0 = does not support offline delivery
1 = deliver even when the player is offline
Published
Shop packs are only visible to players in the shop if the specific Shop pack is published.
0 = not published / hidden
1 = published / visible
Order ID
The shop uses the Order ID to determine the order in which Shop packs are displayed. An Order ID of 0 will place a Shop pack at the beginning, and an Order ID of 9999 will place a Shop pack at the end.
The Order ID also determines the order of sub-items in a Collection.
Delivery Content
The data in the Delivery content column is used to define what the Shop pack should actually do when it is delivered to a player.
The data in this field is sensitive to errors, so it's important to work carefully in this column. You can use a JSON beautifier to format the data into a layout that is easier to read. Always ensure you enter "minified" JSON in this field.
The easiest way to work with this field is to first set up the various actions you want to use via the dashboard. Then, you can run an export and modify the data as needed.
An example of how the data (JSON) looks when formatted / beautified (JSON beautifier). After making changes to the JSON, you should minify it again before posting it to GSA.
Restrict to Custom Role ID
If a Shop pack should only be available/visible to players with a specific Custom role, you can specify that in this column.
You can find the ID for the respective Custom role on the Custom role page.
Restrict to Cluster ID
If you want a Shop pack to be orderable only by players with a character in a specific cluster, you can set that in this column. When the field is left empty, the Shop pack can be ordered from any cluster.
This field accepts only one ID.
You need to enter the Internal Cluster ID in the CSV. You can find the Internal Cluster ID on the Cluster page.
Restrict to Game server ID
If you want a Shop pack to be orderable only by players with a character in a specific game server, you can set that in this column. When the field is left empty, the Shop pack can be ordered from any game server.
This field accepts only one ID.
You need to enter the Game server ID in the CSV. You can find the Game server ID on the Game server settings page.
Make sure to enter only the numeric ID.
Block for Game server ID's
Using this column, you can prevent a Shop pack from being ordered from specific game servers. Enter the IDs of the game servers from which you want to restrict access to the Shop pack.
When the column is left empty, it means there are no restrictions, and the Shop pack can be ordered from any server (unless you are using one of the above "restrict" options).
If you want to specify one or more game servers, you need to use JSON format. See the examples below:
With three IDs: ["123", "456", "789"]
With one ID: ["123"]
See Restrict to Game server ID for info how to find the Game server ID.
Character level restrictions
Use this column to determine whether a player is allowed to order a Shop pack. You can set whether the in-game level should be below or above a certain number. If the field is left empty, there are no restrictions.
Above
For restrictions where the player's level must be above a certain number, use the following format:
Above level 1: a_1
Above level 25: a_25
Above level 123: a_123
Below
For restrictions where the player's level must be below a certain number, use the following format:
Below level 1: b_1
Below level 25: b_25
Below level 123: b_123
Single purchase
If you want a Shop pack to be ordered only once, by anyone, you can use Single purchase. If you enter a 1 here, the Shop pack will be removed from the shop as soon as someone has purchased it. Only 1 player will be able to buy it when this is active.
Purchase limit (count & days)
With the purchase limit columns, you can determine how many times players can order certain packs.
Purchase limit count
Determines the quantity of times a pack can be purchased.
Purchase limit period (days)
Determines the number of days for which the purchase limit applies.
In the example below, a purchase limit of 5 packs for a period of 30 days means that players can order the pack a maximum of 5 times within a 30-day period.
