Release Notes - August 2024

General

• Improvements to the OpenAPI Documentation continue to be made and this release has focused on documentation accuracy on the Standard Wallet API protocol, ThrillConnect and ThrillPots Gateway. This is an ongoing effort.

New Features

ThrillPots

• Recurring Raffles

  • In previous releases, raffles were limited to being once-off scheduled jackpots. In this release, we have extended the scheduling capabilities of the system to allow granular control of jackpot and raffle schedules.
    • More information about scheduling can be found here

• Raffle Ticket Enhancements

  • As of this release, raffle tickets can be configured based on a player's base_wager or contribution. Previous releases only supported ticket costs based on contribution.
  • It is now possible to retrieve all of a player's raffle tickets for all active raffles (instead of retrieving them one raffle instance at a time).
    • ThrillPots Gateway:
      • GET /jackpots/instances/raffle/tickets/brand/:brand_id/:player_id

• Advanced Scheduling

  • As mentioned in the Recurring Raffles feature above, we have introduced a more advanced scheduling subsystem to the platform.
  • In ThrillPots, schedules are bound to a Jackpot Instance and a brand

• Seed Boosts

  • The seed boosts feature allows operators to add additional funds to a Jackpot which will act as additional seed buffers when a jackpot is won.
  • Seed Boosts can be applied to specific pots within a Jackpot. For example, if you wished to add a Seed Boost to your top tier only, you could do so.

Changes/Improvements

ThrillPots

• Async Contribution Errors now carry metadata

  • For integrations that make use of asynchronous contributions, you may have noticed that the metadata supplied on the contribution call was not propogated on errors reported to the webhook.
  • This issue has now been addressed and the webhook will receive the original metadata on all errors under the metadata field.

• JackpotEventUpdate event changes

  • Added the following new fields to the event:
    • jackpot_type - Indicates where the instance is a Jackpot or a Raffle (these are the two valid values for this field)
    • timestamp_start - If the instance has a schedule, this field will contain the UTC timestamp for the starting time of the active jackpot instance
    • timestamp_end - If the instance has a schedule and an end time for the instance, this field will contain the UTC timestamp for the end
  • An example of the new structure looks like this:

  {
  	"event_type": "JackpotUpdateEvent",
  	"data": {
  		"id": "ab775921-0743-47d4-8ad2-cd60aae27b39",
  		"jackpot_type": "Raffle",
  		"currency": "EUR",
  		"pots": [
  			{
  				"id": "main",
  				"is_progressive": false,
  				"current_value": 100.0
  			}
  		],
  		"allowed_brands": [
  			"thrilltech:brand1",
  			"thrilltech:brand2",
  			"thrilltech:my-new-brand"
  		],
  		"allowed_sources": [
  			"raffle-test"
  		],
  		"status": "Active",
  		"timestamp_start": 1728604800000,
  		"timestamp_end": 1728691199000,
  		"last_updated": 1728604800000
  	}
  }
  

  • Resolve Raffles not actively updating to Active state based on scheduling

• Zero value contributions are allowed

  • Up until now, Jackpot Templates did not allow contribution values to be specified as ZERO.
  • As of this release, this restriction as been lifted (with certain caveats - explained below)
  • Reasons to allow zero-value contributions:
    • Promotional Jackpots: Promotional jackpots should allow zero value contributions if they are non-progressive and/or do not have value based tipping points
  • Caveats:
    • Zero value contributions can only be made to jackpots that are fully operator funded AND have all their pots defined as probability or time based tipping points.
    • For zero value contributions, there is no RTP to be calculated for wins

• WinEvent changes

  • In previous versions, the WinEvent was only broadcast to players of the brand on which the win occurred. In this release, the WinEvent is also broadcast to all brands that are participating in the jackpot.

• Improved Handling for Limited Jackpot Tiers

  • We have improved the handling of limited jackpot tiers. Limited Jackpot Tiers are tiers that are configured to only drop a certain amount of times. With this release, if the last available tier of a jackpot is a limited tier and the drop limit has been reached, the jackpot itself will automatically end (status == Ended) and the frontend will stop receiving JackpotUpdateEvents for the jackpot.

ThrillConnect

• Updated payload for Get Instance By Source endpoint
  • Affected endpoint:
    • GET /v1/thrillpots/instances/source/:source_id/brand/:brand_id
  • The response now contains three additional fields:
    • status - The status of the instance
    • timestamp_start - The UTC timestamp containing when the jackpot starts/started
    • timestamp_end - The UTC timestamp containing when the jackpot will end
  • These additions allow frontends to:
    • determine whether a jackpot is active for contributions
      • if status == Active, the jackpot is active within the schedule
      • if status == Pending, the jackpot is scheduled to start at a future time
    • determine if a raffle is currently active or not
      • if status == Active, the raffle is active and accepting contributions
      • if status == Pending, the raffle is scheduled to start at a future time (timestamp_start).