Quote Originally Posted by Patrickssj6 View Post
So your version changing actually works correctly now? Is there a way I could fix it in my exe in the mean time before OS gets released?
I haven't integrated the rolling-version-changer stuff into production code yet. I'd recommend writing a simple C# app that applies the changes you make so you're not releasing dedi.exe after dedi.exe...(and that allows you to change the app's build info too, so people know when it's old or new)
Quote Originally Posted by Dwood View Post
I'd like to know if in BlamLib there's a way to check if a map is protected before opening them. I just added a test class for cache extraction, and am seeing what can be done about that particular thing.
I've never dealt with protected maps using BlamLib (other than Reach) so there's no support for it in Halo1. I know I asked Steelix to make the first tag instance's (so, the scenario) group tag to be 'prot' but that was only for OS's sake. If he flags the map as protected somewhere in the cache header then I can see about adding support for them. If the only "flag" is that 'prot' thing I asked for way-back, then it will take some tweaking/hacking to the tag header/instances loading code.