Scrima Stats PUBG PC
Tools

PUBG resources

Asset Library

Reference assets used by Scrima UI to explain PUBG match data.

251 assets14 categoriesContext only

How assets work

Use assets only when they explain the stat.

Source and ownership

PUBG API assets remain owned by their rights holders. Scrima is unofficial.

API data stays separate

Images label maps, weapons and events. They never replace or sell PUBG API data.

Usage rules

Use assets as contextual UI, not as a standalone downloadable asset library.

Asset semantics

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.

7 rules

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.
Resource browser

Find the right asset for the data.

Search the local PUBG/API asset set and filter by semantic use before adding images to a stats card, table or replay view.

251 / 251 shown