Game mechanics
Kill Feed
It sits in the top right corner of your HUD and updates instantly when an enemy dies or you help secure a kill. This information stream allows you to track remaining opponents without relying solely on sound cues or minimap pings. You can identify which weapons are being used against you and determine if teammates are trading effectively during engagements. Ignoring this log means playing blind to the current state of the round, as it reveals enemy positions, loadouts, and survival status immediately after a fight concludes.
Interpreting Weapon Icons and Kill Types
The feed distinguishes between body shots, headshots, and special kills with specific visual markers that appear next to player names. A skull icon indicates a headshot, while a standard crosshair denotes a body kill from firearms. Knife kills and grenade eliminations show their respective weapon symbols instead of rifles or pistols. This distinction matters because a headshot notification confirms an enemy is down without needing confirmation from teammates. You can also identify if an opponent was killed by a specific gun type, such as a sniper rifle versus a rifle, which informs your next movement decision. If you see a teammate eliminated by a knife icon, you know to expect close-quarters combat in that sector rather than holding long angles. The feed does not display damage numbers or health remaining, so you must infer survival based on the kill type and known weapon capabilities. Recognizing these symbols quickly allows you to assess threat levels before entering a new area. Familiarity with weapon icons speeds up this recognition process significantly during high-pressure situations where split-second decisions determine survival.
Tracking Enemy Positions During Round Phases
Every elimination updates the log continuously throughout the entire round, including during bomb plants and defuse attempts. This constant flow of information helps you count down surviving enemies accurately as the timer ticks. When a teammate dies while holding an angle, their name in the feed confirms that position is now open for the enemy team to push. You can use this data to rotate early if you see multiple kills on one site, knowing your teammates cannot hold it alone. Conversely, seeing no updates during a prolonged silence suggests enemies are holding power positions or waiting for utility usage before engaging. During the bomb plant sequence, the feed continues to update with eliminations and assists, allowing defenders to track attackers even while the timer counts down. This ensures you never lose situational awareness simply because the objective has started ticking. If an attacker dies during a defuse attempt, the feed confirms they are removed from the equation before the round ends.
Using Feed Data for Trades and Rotations
Successful trading relies on knowing exactly when a teammate dies so you can peek immediately after their elimination appears in your log. If you delay too long, the enemy will have time to reload or reposition before you enter the fight. You should also monitor assists to understand which teammates are contributing damage without securing the final blow. This helps identify who is holding aggressive positions versus who is playing support roles. When rotating between sites, listen for audio cues alongside visual updates from the feed to confirm enemy locations. If you see a kill on the opposite site, you know the map control has shifted and can adjust your utility usage accordingly. Understanding these patterns allows you to predict enemy movements based on who remains alive. For example, if the feed shows only one attacker left after a retake, you know they cannot hold multiple angles simultaneously. This knowledge dictates whether you play aggressively or hold back to secure the round win without unnecessary risk. Communication with your team becomes easier when everyone references the same visual data regarding enemy survival status and weapon types used in previous engagements.
Related
All articles ▸Written for CS2 Codex. Every weapon and map figure on this page was checked against the same data that powers /weapons and /maps, then fact-checked by an independent qwen3.5:122b pass at confidence 9/10.