Skip to main content

SDK

The VS Plus Software Development Kit (SDK) allows game developers to embed tournament features, matchmaking, and reward tracking directly into their games. By using the SDK, studios can focus on core gameplay while VS Plus handles competitive infrastructure.

Overview​

Purpose and benefits of SDK integration​

Integrating the SDK removes the need to build a custom tournament backend. Developers gain access to leaderboards, ranking logic, and player identity services out of the box. This accelerates development time and ensures all games on the platform follow consistent rules for scoring and rewards.

Target users​

  • Game developers

Core Tournament System​

Leaderboards, ladders, and elimination brackets​

The SDK provides multiple tournament formats including simple leaderboards for ongoing ranking, ladders for long-term progression, and single or double elimination brackets for scheduled competitions. Organizers can switch between formats with minimal configuration.

Matchmaking (ELO, basic) and ranking logic​

Basic skill-based matchmaking uses an ELO-inspired rating. Games submit match results, and the SDK adjusts player ratings accordingly. Developers can also define custom weighting factors to tune matchmaking to their genre.

Core Integration Requirements​

Required data points​

  • Game ID
  • Player actions
  • Match outcomes

Data submission methods and frequency​

Data can be submitted server-to-server using REST endpoints or directly from the game client through authenticated SDK calls. Matches should report results as soon as they conclude to keep leaderboards accurate. For games with unstable connections, batched submissions are supported.

Blueprints & Templates​

Genre-specific templates​

Reference templates cover common genres such as first-person shooters, puzzle games, and battle royales. These blueprints demonstrate recommended settings for tournament structures and reward calculations.

Best practices for SDK adoption​

Include the SDK early in development to avoid refactoring game logic later. Validate player IDs before submitting match data, and use the provided testing tools to simulate tournaments during QA.