Mike at BrashMonkey Posted November 10, 2013 Report Posted November 10, 2013 Hi everyone, We're in final internal testing now, but there are still several important bugs to fix before we can release it for community wide testing. Best guess is 3 days for community release for testing (likely Windows only at frist), then however long it takes to fix any bugs you all find before we replace b5 as the official latest version. Sorry this build has taken so long, but it represents the addition of all "major" remaining features for the initial release of 1.0. All subsequent releases will be drastically more frequent, and focussed on workflow improvement and overall stability. cheers, Mike at BrashMonkey
tombmonkey Posted November 11, 2013 Report Posted November 11, 2013 Are there any changes in the sclm file format that could make a b5 implementation stop working? Or I'm safe just by not using any of the new features? If there are then I will have to sit several upcoming versions.
Mike at BrashMonkey Posted November 12, 2013 Report Posted November 12, 2013 Great question tombmonkey. Don't worry...the new features add stuff, but shouldn't break anything IF you avoid using the new features OR if the plug-in (Spriter implimentation) you are using is programmed carefully as to ignore data it can't use. cheers, Mike at BrashMonkey
Recommended Posts