Why does BattleEye need to enumerate all of my drive mappings on start, including network maps over VPNs? You can watch the process and see that after the enumeration, it doesn't attempt to scan or get a file list or anything - it just wants to see what drives I have mapped. Is there some sort of anti-cheat method that needs to know that I have a drive mapped to a folder VPN's in another state or something? For all I know, there may be some other set of criteria that might trigger additional actions over these connections. Enumerating all of the drives on a box, including mapped drives, seems fairly inapplicable to continually confirming the integrity of an executable in memory and checksumming some network traffic. Can anyone shed any light?