MatchmakingPRO

Overview

One Game Instance subsystem (UMMProSubsystem) drives the entire loop: group players → get them on a server → rate the result → progress the account. Every method is BlueprintCallable; every milestone fires a Blueprint-assignable event.

Module layout

Core Matchmaking

Tickets enter named queues; each queue runs a greedy oldest-first matcher driven by a data-asset of rules. Parties are atomic — everyone on a ticket lands on the same team.

The matching pass

1. Stale tickets expand: every ExpansionIntervalSeconds their tolerances widen one level (up to MaxExpansionLevel).
2. The oldest ticket anchors a candidate group; every other ticket must pass all enabled rules against every group member.
3. When the group fills the match (or reaches MinPlayersToStart with backfill/bots allowed), teams are built — snake draft to the weakest team with room, parties whole; FFA modes make each ticket its own team.
4. Missing seats are padded with rating-matched bots when bAllowBots is set.
5. The assembled proposal is scored 0–1 by all rules; below MinMatchQuality it is discarded. The native OnValidateProposal hook can veto it (anti-cheat / connection probes) — vetoed tickets re-queue.

Rules — instanced inside a UMMProRuleSet asset

Rules are EditInlineNew UObjects — subclass UMMProMatchRule in C++ or Blueprint for game-specific rules (role balance, vehicle class, crossplay pools…). Each rule set also carries: bRankedQueue, RequiredMinLevel (queue gating), ExperimentTag (A/B testing hook), and the FMMProMatchParams match shape.

Ready check, backfill, penalties

Server Travel & Sessions

A unified travel layer: the game calls one API whether the match runs on a dedicated fleet, a listen host, or a LAN box.

Getting into the match

UMMProTravelManager — the unified layer

Offline Mode — LAN, Hotspot & Invite Codes

Full multiplayer with zero internet and zero backend. Host on one machine; friends on the same Wi-Fi join by short code or pick from an auto-discovered list. Progress keeps counting and syncs later.

The invite-code flow

Experience, Levels & Competitive Ranks

XP & leveling — UMMProXPCurve asset

Ranks — UMMProRankSystem + UMMProRankTierData asset

Only queues flagged bRankedQueue (or results with bRanked) move the ladder — casual play never costs RP. UMMProProgressionComponent (replicated) carries level/prestige/rank to all clients for nameplates and scoreboards.

Player Stats, History & Leaderboards

Tracked stats — FMMProStatBlock

Kills / Deaths / AssistsK/D · KDA ScoreDamage dealt / taken / healed Shots fired / hit / headshotsAccuracy · HS% Objective captures / defends / scoreW / L / D · win rate Matches playedPlaytime (hours) Kill streak (best)Win streak (current / best) Avg kills · avg score

Every stat is addressable by key (GetStatByKey("KD")) — the same keys drive achievements and per-stat leaderboards.

Leaderboards — UMMProLeaderboardService

• Scopes: global, regional, friends (client-side filter on your friend-id list).
• Boards: per-stat by name — rating, wins, kills, level out of the box, any stat key extensible.
• Seasonal vs all-time via composed ids: <stat>.<season>.<region>.
• Percentile ranking ("top X%") computed from the cached board; cache keeps boards working offline.
• Auto-submission after every match; REST endpoints GET/POST /leaderboards/{board}.

Profile & display

GetPlayerCard() returns the complete profile card: level, prestige, rating, rank display + badge icon, highest rank, career stat block, unlocked achievement badges, player-chosen showcase slots (SetShowcaseSlots), most-played mode/map/character, and both currencies. CompareCareerStat(Key, OtherBlock) diffs any stat against a friend or a global average.

Progression Rewards & Achievements

Genre-Agnostic Design & Presets

Matchmaking, travel and sessions never care about gameplay — they group players and get them on a server. UMMProGameModeProfile bundles match shape + rule set + travel playlist; pick a Preset in the editor and the asset fills itself, then tweak freely.

The abstractions that make it work: FMMProMatchParams (team count, players per team, bFreeForAll, MaxPlayersOverride, bAllowBots, rating-type label), UMMProRuleSet (which rules, how strict), a rating value that means whatever the game wants, and a travel playlist the session rotates through. A racing game and a football game run the same core.

Backend Integration

One async interface — IMMProBackend — behind auth, tickets, allocation, profiles, results, stats, leaderboards and invite codes. Every method has a safe no-op default, so custom adapters implement only what their service supports.

Settings Reference

Project Settings → Game → MatchmakingPRO (UMMProSettings, saved to DefaultGame.ini).

Events & Delegates

All Blueprint-assignable on UMMProSubsystem unless noted.

Class Map

Quick Start

1 · Find a match (online or local)

// C++ — identical Blueprint nodes exist for everything
auto* MM = UMMProSubsystem::Get(this);
MM->OnMatchFound.AddDynamic(this, &UMyMenu::HandleMatchFound);
MM->OnMatchReady.AddDynamic(this, &UMyMenu::HandleMatchReady); // travel happens automatically after this
MM->StartMatchmaking("Ranked1v1");            // or StartPartyMatchmaking(Queue, PartyProfiles)
// during the ready check:
MM->AcceptMatch();   // or DeclineMatch()

2 · Offline LAN party

// HOST — returns a shareable code like PRO-7H2K9C3FA0
FString Code = MM->GetOfflineSession()->HostOfflineMatch(this,
    "/Game/Maps/Arena", "", "Garage Party", /*MaxPlayers=*/8);

// FRIEND — join by code (same box works online; the resolver decides the route)
auto* Codes = MM->GetInviteCodeService();
Codes->OnInviteResolved.AddDynamic(this, &UMyMenu::HandleInvite);
Codes->ResolveCode(EnteredCode);
// in HandleInvite: GetOfflineSession()->JoinLANSession(this, Invite.Server.Address, Invite.Server.Port)

// or browse instead of typing:
MM->GetLANDiscovery()->StartListening();      // → OnSessionsUpdated → "Local Games" list

3 · Track stats during the match

// UMMProStatsComponent on your PlayerState:
Stats->AddKill();  Stats->AddShots(12, 9, /*headshots=*/2);  Stats->AddObjectiveCapture();
Stats->ModeId = "Ranked1v1";  Stats->CharacterId = "Ryu";
Stats->CommitToSubsystem(this);               // stage before SubmitMatchResult

4 · Report the result — one call drives everything

FMMProMatchResult Result;
Result.MatchId   = ActiveMatchId;
Result.QueueName = "Ranked1v1";
Result.bRanked   = true;
Result.DurationSeconds = 540.f;
Result.Teams.Add(UMMProBlueprintLibrary::MakeTeamResult({MyId},  EMMProMatchOutcome::Win,  3));
Result.Teams.Add(UMMProBlueprintLibrary::MakeTeamResult({OppId}, EMMProMatchOutcome::Loss, 1));
MM->SubmitMatchResult(Result);
// → Glicko-2 rating → XP (+first-win bonus) → RP/promos → career stats + history
// → currency → achievements → leaderboards → save → backend (or deferred sync)

5 · Rotate rounds / tracks on the server

MM->GetTravelManager()->SetPlaylist(TrackPlaylist);
MM->GetTravelManager()->TravelToNextInPlaylist(this, /*bSeamless=*/true);

// destination GameMode::InitNewPlayer — restore each player's context:
FMMProTravelToken Token;
if (UMMProTravelManager::ParseTravelToken(Options, Token))
{
    AssignTeam(NewPlayer, Token.TeamIndex);
    LoadLoadout(NewPlayer, Token.CustomData["Loadout"]);
}

Blueprint Node Catalog BP_MatchmakingPRO_Catalog

BP_MatchmakingPRO_Catalog is the reference Blueprint that exercises every node the plugin exposes — one demo graph per category. Drop it in a level (or just browse below) to learn the whole API. Every node here is real and callable from Blueprint: blue = Callable, green = Pure, purple = Event, gold = Component. Filter by category, search, and page through the gallery.