Re: OpenSauce Halo CE SDK Update #2 (RC)
No specific content but an overview of OpenSauce and what it is (and isn't). It seems like people never really caught on or felt the urge to automatically assume it was too advance for them, so I figured breaking it down and applying examples to their current modder state of mind would work the best. Without a Primer, going into specific topics would be fruitless. An internet thread can only deliver information in so few ways and lacks acceptable persistance methods (fuck HTML files) for offline viewing.
Re: OpenSauce Halo CE SDK Update #2 (RC)
Ok. As an example, I think it would help a lot of the people who want to do things with open sauce if you did an example tag and showed how to add it into Open Sauce. Something simple... like a custom tag for text strings perhaps, just to show how to access them from OS?
Re: OpenSauce Halo CE SDK Update #2 (RC)
Check out how he did the yelo_globals tags, he has sample code for those and it's fairly straightforward.
Re: OpenSauce Halo CE SDK Update #2 (RC)
I'm going to need the assistance of some beta testers tomorrow/saturday for some things. You think you'll be able to assist Fire?
Choking, will you be able to test the animation importer?
Re: OpenSauce Halo CE SDK Update #2 (RC)
Yea, I should be around. I'd be happy to test.
Re: OpenSauce Halo CE SDK Update #2 (RC)
For the next update in OS, are you changing the Project_Yellow Tags at all? I'm designing my tag set up and want to know if you were going to make adding custom tags to the project_yellow stuff more version compliant, ie more places to add tag refs than the scenario and the global explicit references.
Re: OpenSauce Halo CE SDK Update #2 (RC)
tag_collection. It solves any problems you just mentioned and both py tags support them.
The project_yellow tags are already as version compliant as the Halo1 engine allows them to be. No one should be changing the py tag structures except for me. If you're going to require new fields to support your code, make your own project's special tag. PY tags are for the operation of official OpenSauce releases.
Re: OpenSauce Halo CE SDK Update #2 (RC)
Oh I know, i'm not trying to modify the original tags and all, and am going to make my own tags. I mean I just wanted to know if you were adding any other explicit references... (like the bsp and lightmap section of the tag)
Also, I don't know where you got the idea of me editing them....
Re: OpenSauce Halo CE SDK Update #2 (RC)
If any new tag fields were to be added, they would be for a feature or something I was looking to stub or implement.
I was just saying in general: no one should ever change those tags or at least release anything which changes in them. That would be breaking versioning and they're not on the standards itty bitty titty committee for OpenSauce's core.
Re: OpenSauce Halo CE SDK Update #2 (RC)
I'll be available from around 6:00 pm GMT tomorrow and over the weekend.