Pi||__SourCe

Pi||__SourCe: mostly communicates through kill feed entries. Not always polite, but statistically difficult to ignore.

The kill feed is doing a lot of talking here: 74 CTF kills backing up the profile. Solid CTF: there is proper CTF value here, even if the profile still has a few areas where the stats side-eyes the demo.

Gameplay read: real objective value here. The flag, the routes, and the panic moments all have their fingerprints on them.

Lifetime CTF file: 2 CTF matches, 67 objective events, 74 CTF kills, and 353 MVP score. Per match that is 33.5 objective events, 37.0 kills, and 176.5 MVP score, which is enough maths to make voice chat go quiet for half a second. Small sample warning: 2 CTF matches is enough for a read, but not enough to start carving statues.

Flag crime report: 13 grabs, 6 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: 16 returns, 3 mid returns, 1 clutch returns, and 16 flag kills. That is 10.0 returns per CTF match, with 5% coming in the close-save panic window where everyone suddenly develops opinions.

Team value: 3 assists, 9 covers, and 0 seals, running at 6.00 support actions per CTF match. Role shape says Kill Pressure, with Kills holding 35% 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 2 games, enough for the server jury to call it cold run. The map file keeps circling back to CTF-AndAction-V: 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 67 objective actions: 13 grabs, 0 caps, 20 returns, 16 flag kills, and 12 support actions. CTF-AndAction-V is the warning label map here; ignore that at your own scoreboard risk.