About the Aimbot: I am no C# programmer, but I know C and a bit of C++, and from what I can gather here I can see it uses mem values to grab all this information from halo. Halo relies greatly on memory because that is how it loads maps so fast, a quick one time load into memory and you can access it whenever. There are a few options here for possibly fixing this problem: 1. change how halo stores data in memory 2. change netcode (might work, I have honestly no idea how better netcode and less leading would affect the aimbot) 3. change the offsets that halo uses for the affected values. This is just throwing ideas out there mind you. ------------------------------------------------------------------------------------------------------------------------- An idea about the unified banlists: A toggle in the halo dedi that would allow you to query a master ban list when you start it up to specify a master ban list managed by the community or a user's own list. Have it query a text file hosted on a site and say "use this list" and have it compare the current one being used against the master list so you can update the master list and have people have the list update automatically. I also think that you should allow for the option of people choosing their own banlists incase people like to play with people that bot. A system like this would work great because it would not need a separate application or process to run behind halo to keep the list updated. I think integrating the current banlist system that was voiced before about gathering data from a community (videos and other media that prove a person is botting) before adding them to the universal banlist. Halo automatically checks for updates when you load up multiplayer, why not just add another thing in there to check for a new universal banlist? What do the rest of you think?