Official references
Use the links below for PUBG API assets, documentation, terms, key handling, rate limits and caching guidance.
PUBG resources
Resource References
Public production pages link to the official PUBG API resources instead of rendering a browsable asset folder.
How Scrima uses PUBG resources
Scrima uses PUBG API resources only as contextual UI for match data, telemetry and player statistics. The public site does not expose a standalone downloadable or browsable third-party asset library.
Product context
Maps, weapons and killfeed icons belong next to data they explain, not as generic page decoration.
Internal review
The full asset browser is gated to test/development environments for QA and implementation checks.
Official references
6 links
Use the source docs for asset and API rules.
These references replace the public asset gallery in live environments.
PUBG API assets
Official API developer resource repository for mapping telemetry values to art and dictionaries.
PUBG API docs
Primary documentation for API concepts, endpoints, telemetry and app structure.
Developer terms
Terms for API data, trademarks, monetization and permitted developer use.
API key rules
Security guidance for keeping API keys server-side.
Rate limits
Request-budget guidance for production integrations.
Caching guide
Recommended API response caching and intended data use guidance.
Asset semantics
7 rules
Use images when they explain the data.
This guide keeps Scrima's resources consistent: maps show match context, weapons show weapon data, killfeed icons show combat events, and insignias show ranking/performance signals.
Match and map context
Use map art for lobbies, match cards, map rotation and replay backgrounds.
- Use for
- Scrim list cardsMatch analyzerMap rotation
- Avoid
- Do not use map art for player skill or weapon stats.
Combat events
Use killfeed icons only when the information is actually about combat or death state.
- Use for
- KillsDBNOsDeath type
- Avoid
- Do not use combat icons for lobby metadata or team registration.
Weapon statistics
Use item weapon art for weapon telemetry, damage sources and player weapon cards.
- Use for
- Weapon damageDamage dealtCombat score
- Avoid
- Do not use weapon art as generic decoration on unrelated cards.
Utility and support
Use throwable, heal and boost items for support, survival and team-play stats.
- Use for
- Utility scoreRevivesSurvival
- Avoid
- Do not imply exact item usage unless telemetry confirms it.
Rank and performance
Use insignias for placement, SPR and leaderboard/publish signals.
- Use for
- RankSPRPublished results
- Avoid
- Do not use PUBG rank icons as a fake official player rank.
Brand and platform
Use Scrima brand assets for Scrima identity. Use plain text for third-party platform context unless there is a documented brand-rights reason to show a third-party logo.
- Use for
- HeaderFooterPUBG data badge
- Avoid
- Do not render PUBG, Steam or Discord logos in product chrome unless the current brand rules clearly allow that exact use.
Compliance guardrails
Keep third-party resources inside the product context: server-side PUBG API calls, cached match responses where reasonable, no logo-led endorsement cues, and no separate resale or redistribution of API data or assets.
- Use for
- Internal resource reviewAdmin QAPolicy checks
- Avoid
- Do not expose API keys, scrape around rate limits or package third-party assets as Scrima-owned files.