A Tournament is a contest amongst players which recurs on configurable duration (e.g. daily) and delivers progression and rewards based on the outcome.
A Tournament is a contest amongst players which recurs on configurable duration (e.g. daily) and delivers progression and rewards based on the outcome. With Beamable 0.15.0, groups can compete as well, and you can control how player members get rewarded based on their group’s performance.
In addition to the existing rank-based rewards, we’ve added specifiable player rewards based on the final score.
The outcome of a tournament cycle determines whether a player will advance to the next stage, remain in the current stage, or regress to a previous stage. It is now possible to also optionally specify a non-participation stage-regression penalty. This effect compounds, meaning that if a player misses two cycles, they will suffer the regression twice.
Offers provide the ability to sell items and currencies to players for real money or virtual currency.
Cooldowns on Listings are defined on content and are the same for every player. The Commerce service has a new method, AccelerateListingCooldown, which can be invoked from a Microservice to allow a Gamemaker to reduce the cooldown temporarily, for a listing, for a single-player providing a more dynamic experience for the players.
Beamable’s inventory system has always supported items and soft currencies for players.
Three new console commands exist that let you get, set, or add currencies at runtime in your game. You can use this feature to quickly grant currencies or see what happens when a player is out of currency.
We’ve also added meta properties to currencies. You can store key-value data on individual currencies in a player’s inventory. This unlocks the ability to store the last modified date of a particular currency, a rate at which you want the currency to grow, or whatever other metadata you need.
Beamable includes a variety of editor tooling and workflow support.
The 0.15.0 release includes several bug fixes and usability improvements. You can now control Beamable’s internal log level on the Project Settings/Beamable/Verbose Logging page. This can be really helpful if you need to monitor Beamable’s web traffic, or other internal messages.
Our changelogs can be found at https://github.com/beamable/Changelogs/blob/production/com-beamable-changelog.md