Just wanted to drop my 5 cents here:Originally Posted by Kornman00
So I've got some ideas on how to better some of the existing networking...however, part of the changes would make OS invalid with connecting to or from stock game builds. I'd like to at least try testing the changes in a full server this or next month just to see if such a change is worth it. The changes assume everyone is running on broadband connections...which should have been the assumption by MS from the get-go, but I digress.
I could also probably make it so that you can toggle the networking enhancements on and off, to allow you to connect to stock client/servers. However, I'd have to assume the end-user isn't a complete twat to know how to work the console to execute a script function...which is almost asking a lot, so the default would probably have to be off.
I think the original approach to OpenSauce was not really a good one and for the next step you should rethink some options.
My suggestion is that you make a exclusive dedicated client and server specifically for running OS. I don't know how far your network changes go but I think a loader would be good here.
Server sided: When starting the server a loader loads the haloded file and injects your DLL. Hooking the init parsing function you can include custom parameters which enable OS features like Multi-Team vehicles or the network enhancements inside the init.txt. Upon someone entering the server you do a handshake with the client and send requested features to be enabled on the client as well (Multi-Team Vehicles). If no callback because OS was not loaded, the connection is refused.
Client sided: You can start the loader which injects the client version of OS. In the game browser window only OS-Enabled-Severs will be shown...this could be done via a custom prefix in the server display name along the lines of a signature byte like 0x20 followed by [OS] (the server does this by changing sv_name). Upon entering once again the handshake, checking of OS versions etc.
Bookmarks