Datasetpublic

CS2CD/Context_window_256

Counter Strike 2 Cheat Detection Context Windows - Length 256 Overview The Counter Strike 2 Cheat Detection Context Windows - Length 256 (Context_window_256) is a dataset conprised of "context windows". This dataset was created using extracted data from the CS2CD dataset. For more information regarding the data see AntiCheatPT: A Transformer-Based Approach to Cheat Detection In Competitive Computer Games by Mille Mei Zhen Loo and Gert Lužkov 1/6/2025.… See the full description on the dataset page: https://huggingface.co/datasets/CS2CD/Context_window_256.

sourceHugging Facecc-by-4.0updated 1y agoView on Hugging Face

1likes69downloads

Dataset Card

Counter Strike 2 Cheat Detection Context Windows - Length 256

Overview

The Counter Strike 2 Cheat Detection Context Windows - Length 256 (Context_window_256) is a dataset conprised of "context windows". This dataset was created using extracted data from the CS2CD dataset. For more information regarding the data see AntiCheatPT: A Transformer-Based Approach to Cheat Detection In Competitive Computer Games by Mille Mei Zhen Loo and Gert Lužkov 1/6/2025.

Dataset Structure

<div style="border:1px solid #ccc; padding: 10px; border-radius: 5px; background-color: #fff3cd; color: #000;"> <p><strong style="color: #000">⚠️ Warning: </strong>Any warnings that apply to the <a style="color:#0000EE" href="https://huggingface.co/datasets/CS2CD/CS2CD.Counter-Strike2Cheat_Detection/commit/44e5129654508b22802a050a45bcdbb44b103d87"> CS2CD</a> dataset at commit <code style="background-color:#f5f5f5; color:#7a7a7a">44e5129654508b22802a050a45bcdbb44b103d87</code> also apply to this project.</p> </div>

In the context of this project a context window(CW) is a sequence of ticks containing gameplay information. The CW in this dataset are centered around kills. These CWs capture the data of two parties: The attacker(the player performing the kill) and the victim(the player being killed). Given that the attacker was a cheater, the CW would be marked as a "cheater kill". Kills not performed by a cheater were marked as not-cheater kills regardless of whether the victim was a cheater or not.

Counter-Strike 2 gameplay data is recorded in 64 ticks/second. With the CW length being 256 ticks, the CWs capture 4 seconds of gameplay.

Ticks before kill	Ticks after kill	Total Number of ticks
224 (3.5 S)	32 (0.5 S)	256 (4 S)

Tick structure

A single tick in the CW is composed of the following information:

#	Data point	Description
1	attacker\_X	X coordinate of the attacking player
2	attacker\_Y	Y coordinate of the attacking player
3	attacker\_Z	Z coordinate of the attacking player
4	attacker\_vel	Velocity of the attacking player
5	attacker\_pitch	Pitch angle of the attacking player
6	attacker\_yaw	Yaw angle of the attacking player
7	attacker\pitch\delta	Change in pitch angle of the attacking player since last tick
8	attacker\yaw\delta	Change in yaw angle of the attacking player since last tick
9	attacker\pitch\head\_delta	Pitch angle distance from the victim's head
10	attacker\yaw\head\_delta	Yaw angle distance from victim's head
11	attacker\_flashed	Is the attacker currently flashed
12	attacker\_shot	Did the attacker shoot their weapon on this specific tick
13	attacker\_kill	Did the attacker kill the victim on this specific tick
14	is\kill\headshot	Was the kill a headshot
15	is\kill\through\_smoke	Was the kill through a smoke
16	is\kill\wallbang	Was the kill through some wall or surface
17	attacker\_midair	Did the kill happen while the attacker was midair
18	attacker\weapon\knife	Is the attacker holding a knife
19	attacker\weapon\auto\_rifle	Is the attacker holding an automatic rifle
20	attacker\weapon\semi\_rifle	Is the attacker holding a semi\-automatic rifle
21	attacker\weapon\pistol	Is the attacker holding a pistol
22	attacker\weapon\grenade	Is the attacker holding a grenade
23	attacker\weapon\smg	Is the attacker holding a submachine gun
24	attacker\weapon\shotgun	Is the attacker holding a shotgun
25	victim\_X	X coordinate of the victim player
26	victim\_Y	Y coordinate of the victim player
27	victim\_Z	Z coordinate of the victim player
28	victim\_health	Health of the victim player
29	victim\_noise	Did the victim player make noise
30	map\_dust2	Is the played map de\_dust2
31	map\_mirage	Is the played map map\_mirage
32	map\_inferno	Is the played map de\_inferno
33	map\_train	Is the played map de\_train
34	map\_nuke	Is the played map de\_nuke
35	map\_ancient	Is the played map de\_ancient
36	map\_vertigo	Is the played map de\_vertigo
37	map\_anubis	Is the played map de\_anubis
38	map\_office	Is the played map cs\_office
39	map\_overpass	Is the played map de\_overpass
40	map\_basalt	Is the played map de\_basalt
41	map\_edin	Is the played map de\_edin
42	map\_italy	Is the played map cs\_italy
43	map\_thera	Is the played map de\_thera
44	map\_mills	Is the played map de\_mills

In order to capture the weapon used by the attacker without increasing the size of the tick vector too much, a weapon grouping was used as can be seen in row 18-24. The weapon groups were made based on similarity in gameplay.

#	Weapon group	Weapons
1	attacker\weapon\knife	Zeus x27, knifet, knife, Bayonet, Bowie Knife, Butterfly Knife, Classic Knife, Falchion Knife, Flip Knife, Gut Knife, Huntsman Knife, Karambit, Kukri Knife, M9 Bayonet, Navaja Knife, Nomad Knife, Paracord Knife, Shadow Daggers, Skeleton Knife, Stiletto Knife, Survival Knife, Talon Knife, Ursus Knife
2	attacker\weapon\autorifle	AK\-47, M4A1\-S, Galil AR, SG 553, M4A4, AUG, FAMAS, M249, Negev
3	attacker\weapon\semirifle	G3SG1, SSG 08, AWP, SCAR\-20
4	attacker\weapon\pistol	CZ75\-Auto, Desert Eagle, Dual Berettas, Five\-SeveN, Glock\-18, P2000, P250, R8 Revolver, Tec\-9, USP\-S
5	attacker\weapon\grenade	C4 Explosive, Decoy Grenade, Flashbang, High Explosive Grenade, Incendiary Grenade, Molotov, Smoke Grenade
6	attacker\weapon\smg	MAC\-10, MP5\-SD, MP7, MP9, P90, PP\-Bizon, UMP\-45
7	attacker\weapon\shotgun	MAG\-7, Nova, Sawed\-Off, XM1014

Usage notes

—The dataset is formated in UTF-8 encoding.
—Researchers should cite this dataset appropriately in publications.

Application

—Cheat detection

Acknowledgements

A big heartfelt thanks to Paolo Burelli for supervising the project.