openbor Tools

Argh! Got version mixed up with log.

Forgot version change.

Disabled redefine warning. As it is, each and every #include of any #define list is being evaluated as a redefine of every single macro in said list. That’s a bit ridiculous, considering an #include is the only way to actually use a #define source file within an OpenBOR script function. End result is a TON of log spam and increased load time. Please test carefully before re-enabling this or any other warning functionality.

Re-Implemented original BOR v1.0029 'Loading...' status when no loadingbg is used. This way we don't just get a black screen.

Restored 'set' control for loadingbg for level. I investigated 3 Mods (GoldenAxeRemake, FinalFight, and NightSlasherX). While GoldenAxeRemake and FinalFight are missing the 'set' control.... NightSlashersX is not. Knowing BonusJZ and have worked with him I believe this is the correct usage of the feature. Meaning... 'loadingbg {path} {set} {bx} {by} {bsize} {tx} {ty} {tf}' is the proper usage of the command and now reflects the manual.

loadingbg[0] is for loading Models, loadingbg[1] is for loading Levels. Fixed Loading levels.

level_order() uses the first argument to set the loadingbg type. However, in load_level() the first argument is the image location for the background. This implies that if defined we are to use background + bar. This keeps us backward compatible with all existing mods. Strange that I never had the modder specify this before, Hence, this was a bug. All mods ie Contra, Final Fight, GoldenAxeRemake and more now display a background when loading a level.

loadingbg: be compatible to wrong values... i.e. golden axe.

added tracelib2, written from scratch. especially for SX. see tracelib2_test for how to use

Issue 1 fixed. In load_models() since we keep trac of total models to be loaded. The logic now reflects the user's intent. Issue 2 fixed. Loading bar never displayed 100 percent. Added quick check in update_loading if value == max to force one last draw of bar.