Spring == BA
(Spring == Gundam too, ect)
Because BA can't help spring is braking it every time it forces a new release. Enforcing all players to become unwanted beta testers.
spring version XX + game files = gundam
spring = spring.
ZK can run with only certain version of spring. BA could do the same if it was a real issue. Just saying. For example gundam currently does not have an official release that actually runs with the current spring but gundam players can play just fine singleplayer if they never update spring..
BA could be fixed to work in current spring if it's devs were more active. Instead there is ZERO testing during these release candidates. Gundam? It was patched the morning after I found out about the next spring engine release candidate. I was even nice enough to make a thread so that OTHER content devs(including the BA team) could have time to make the adjustment.
So no, ba not being up to date and patched IS NOT spring's fault but BA's fault. Now some stuff like the issues with the pathfollower, yeah you guys could be running old spring if you wanted. Is it possible the new release has bugs? yep, is it likely that none of the ba players wanted to help test the next engine release but cry like babies when it breaks something, MOST DEFINITELY.
No BA players testing build before RC.
No BA people fixing little tag changes and shit durring the RC.
BA players crying about frustration AFTER the RC goes live, oh most of them.
Just saying, it is amazing how easy some of this is to prevent by I don't know helping the devs or picking up notepad, because lets face it, notepad and 7zip are all most of you need to tweak BA. Seriously wrong to put the stagnant state of BA on the devs when it has all these players who could make a patch for BA OR help the devs test.. but instead a project like mine, with 1 dev has to devote it's developer to testing, yet BA has none testing shit for the devs? COME ON! that is such bullshit!