Seeing as how OS 2 is still currently in development, I don't expect many people to be using it right now. Just like how there are two sides to HaloCE, the game and the editor, there are two sides to OS for HaloCE. Most people are only concerned about the side which has to deal mainly with the game (eg, what Battery did).
Below the game's message delta system, sits a data packet system (and below that, the engine's actual networking interface) that was also used for the Xbox days (the message delta system was developed to support the more distributed nature of the PC gaming). It is here where most of the low level (relative to the engine) networking is done in the engine's code. I wasn't talking about manipulating physical packets. The handshakes are defined though the data packet system so any changes or additions would need to be done there, and as I said earlier, I was only interested in building off the message delta system.
FS developed an installer for OS for CE a while back (the WiX project for it is in the source repo too). When an official release is produced, it will use the installer.
OS already supports 1.09. I don't have the time to develop an anti-cheat component for OS on top of everything else I'm working on (nor do I consider it worth my time). I will never remove the cd key check (1.09 doesn't even require you to have the CD in). I'm not interested in "uniting" pirates into the latest game version.
E @ Codebrain: It's been on Google Code for a while now. Thought I posted that in this thread earlier (guess it was in one of the more recent individual update threads).





Bookmarks