Quote: RayBenefield wrote: We had to hold some data back as they could potentially reveal exploits that people can use to grief.













Interesting. I would think that revealing exploits so they can be reported would be a bonus. ;) And discovering exploits seems like it would be quite difficult to do explicitly through the Halo API. You would have to either do a LOT of calculation off of every played game, or already know the game the exploit is in, which means it is probably known by multiple people and needs to be brought to the attention of the 343 sooner rather than later. Hell a tool could be made to help QA maps and ensure that there are no exploits and if there are they could be quickly directed to the team.Locations of Spawns, Weapon Pickups/Drops, Medals, etc... I can't imagine what sort of exploits could be found except out of bounds locations or issues in the spawn system for trapping. This is actually info that would be useful, especially for the tool I'm providing for Forgers which will allow them to analyze their custom maps. So being able to detect when there is a weird location for an event would be immensely helpful for discovering containment issues for Forgers to fix. Also with that many events it would be roughly possible to replay an entire match by using interpolation between events for players. This could also be immensely valuable for analysis purposes.I hope the team reconsiders the decision. I'd love to be able to automatically discover weapon spawn locations, spawn times, common routes, etc. for forgers for custom maps. Thanks for the heads up though Tashi. :) If you get the chance please keep bringing this up cuz I know a ton of people would love to have locations of events.