s0urce

s0urce: a profile with enough logged history to stop pretending anything here is accidental.

The kill feed is doing a lot of talking here: 16 CTF kills backing up the profile. Inconsistent CTF: not useless, not scary. The profile is giving mixed signals and one of them is probably a dropped flag.

Gameplay read: some attack, some recovery, some combat. The stats page is squinting but not panicking.

Lifetime CTF file: 1 CTF matches, 14 objective events, 16 CTF kills, and 47 MVP score. Per match that is 14.0 objective events, 16.0 kills, and 47.0 MVP score, which is enough maths to make voice chat go quiet for half a second. Small sample warning: 1 CTF matches is enough for a read, but not enough to start carving statues.

Flag crime report: 9 grabs, 0 pickups, 0 caps, and 0 solos. Finish rate is 0% from touches and - of caps were solo, so this is where we decide whether the player is a runner, a thief, or just repeatedly lost in enemy base.

Recovery department: 1 returns, 1 mid returns, 0 clutch returns, and 1 flag kills. That is 2.00 returns per CTF match, with 0% coming in the close-save panic window where everyone suddenly develops opinions.

Team value: 0 assists, 2 covers, and 0 seals, running at 2.00 support actions per CTF match. Role shape says Kill Pressure, with Kills holding 42% of the model, so the stats are pointing at the job they actually do, not the job they claim in Discord.

Recent tape says 0% wins from 1 games, enough for the server jury to call it cold run. The map file keeps circling back to CTF-1on1-Midle-v2: 1 appearances with a 0% win rate.

Draft setup read: no useful client setup profile is available yet.

Connection read: no UHNet telemetry has landed for this player in the last 3 months yet.

The CTF footprint is 14 objective actions: 9 grabs, 0 caps, 2 returns, 1 flag kills, and 2 support actions. CTF-1on1-Midle-v2 is the warning label map here; ignore that at your own scoreboard risk.