Skip to content

Game backend modules

Marketplace modules are written, tested and kept up to date by Rudder. Install one on Develop → Modules of the Dashboard; the modules it requires are offered with it. Its catalogs then appear in the menu, its samples fill them in a click, and the next release takes it live.

Inventory keeps the items a player holds: stacks of one item with a limit, such as potions and keys, and unique pieces with attributes of their own, such as a sword with its power. The other modules grant and take items through it.

Stores sells offers a designer sets up: a price or a gift, what the player gets, a sale window, a limit per player and a stock all players share. A store may rotate its offers every day or week. Requires Inventory.

Auction puts tradable items up for bidding until a deadline: the highest bid wins at the end, every bid is paid at once, and the platform keeps a fee. Requires Inventory.

Market sells tradable items at a fixed price from one player to another: the buyer gets the goods at once and the seller is paid, the platform keeping a fee. Requires Inventory.

Trade swaps items and money between two players directly: each confirms what the other put in, and both collect when the two confirmations are in. Requires Inventory.

Quests gives daily, weekly and story quests a designer adds without code. A quest counts what the game reports, such as matches played or won, and gives a reward when it is done. Requires Inventory.

Leaderboards keeps the best score of each player on boards a designer adds without code, all-time or starting again every day, week or month.

Remote config holds the switches, numbers and texts the game reads at start, so a designer changes them without a release of the game.

Mailbox keeps the letters one player reads: your game server or an operator writes one, and the game shows the list with its unread count.

The page of each module, open after you sign in to the Dashboard, lists its functions. A client calls the ones marked client through the generated client; operators call every function from the Dashboard. Arguments and results are JSON; an amount of a currency is always {"asset": "gems", "amount": 10}.

The marketplace modules do not know your game. Your own module glues them to it: it requires them, calls their exported functions and handles their events. A battle pass that grants XP for every purchase handles the purchase event of Stores; a match that counts toward quests reports it to Quests. See Own modules.

A new version of a marketplace module shows Update on its card. Updating changes the draft only; the next release takes it live. A catalog row that no longer fits the new version is listed as a problem of its catalog, and publishing waits until it is fixed.