Skip to content

feat: look up players on other Tencent regions, finding the region from the Riot ID - #52

Merged
sunerpy merged 2 commits into
mainfrom
feat/cross-region
Nov 15, 2026
Merged

sunerpy merged 2 commits into
mainfrom
feat/cross-region

Conversation

@sunerpy

@sunerpy sunerpy commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

History can show players from every supported Tencent region, and a full name#tag finds the region by itself: there is no region to pick.

What changes

  • Lookup: a full Riot ID is looked for on the connected region first (the client's own lookup); only when it has nobody, Riot Client's alias lookup gives the account's PUUID and every other supported region's summoner ledger is asked at once. The region with the highest level opens (equal levels in sgp::PLATFORMS order); a region that does not answer is left out, and an error is only reported when nothing came back. A name without its #tag is looked for on the connected region only, and the not-found wording says which.
  • Also on: when the account plays on other regions too, the header lists them as buttons, from the lookup itself or, for a player found locally, from a background get_player_regions call whose answer is only taken while the page still shows that player. Switching keeps the list; any other way to a player clears it.
  • Other regions' data: profile, pages, scoreboards and recent form come from that region's match-history server; ranks say they are unavailable across regions. Regional records read up to fifty games a request from where the last page ended (a busy server gives ten at a time), a hundred places at most, keeping what came when a later page fails, so they match 0.0.21's fifty-game window.
  • The connected region: a request naming it takes the connected region's own path (caches, the server's slots, ranks). The current region falls back to the entitlements issuer when chat had not said at connection.
  • Caches stay per account and per region, the region picker of the 2026-11-07 preview is gone, strings and docs follow.

Not in this change

Checks

scripts/evidence.sh green on the final tree (stamp 20261115T021055Z, tree 7f8ed0ada90c): fmt, clippy, workspace and core tests, the Windows check, format, lint, typecheck, frontend/plugin/shared tests. The demo was checked in a browser at 1240 px (no picker, "也在:联盟一区", the cross-region note). The cross-region path itself was read live on 2026-11-07 (GZ100 session, a HN1 player); the automatic lookup has not run against the live servers yet, since the QA PC was offline.

BEGIN_COMMIT_OVERRIDE
feat: 战绩页可以查询其他腾讯大区的玩家:输入完整的 名称#编号 会自动找到玩家所在的大区,同一账号在几个大区都有号时可一键切换 (#52)
END_COMMIT_OVERRIDE

…'s regions

The History page has no region picker any more. A full name#tag is looked
for on the connected region first and, only when it has nobody, on every
other supported Tencent region at once, opening the one with the highest
level; an account on several regions lists the others as "also on"
buttons, asked in the background when the player was found locally.

A request for the connected region takes the connected region's own path
(its caches, its server's slots, its ranks), the current region falls back
to the entitlements issuer when chat has not said, and regional records
read up to fifty games a request from where the last page ended, a hundred
places at most, keeping what came when a later page fails.
@sunerpy
sunerpy merged commit 6be8bba into main Nov 15, 2026
6 checks passed
@sunerpy
sunerpy deleted the feat/cross-region branch November 15, 2026 02:22
@winer-release winer-release Bot mentioned this pull request Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant