Sunday, February 19, 2017

Change Log: 2.4.259

Other than a couple of bug fixes based on errors that showed up in the logs from last week, this tiny release contains all API enhancements related to the first/alpha features of The Watcher.

Just a heads up, while break/fix and bug support will not slow down at all in the near term, feature work (including refactoring and redesign) for the legacy app is going to slow down quite a bit over the next few months: between work on the The Watcher and the fact that I'm moving this spring/summer, I don't feel like I will have the free time to keep up with the kind of insane release schedule that I kept up during November/December/January 2016.

That said, we're still full steam ahead on The Watcher and should have some real news on that very soon!

Thanks again for using the Manager!

Wednesday, February 8, 2017

Change Log: 2.4.254

Release 2.4.254 is primarily focused on API enhancements required by The Watcher and laying some groundwork for some future enhancements/optimizations to the Manager.

(Speaking of The Watcher, if you're not doing it already, follow The Watcher on Twitter: once user-facing stuff starts to become available, that will be the major channel for updates/statuses, etc.)

2.4.254 also contains a few bug fixes, and most of them either came directly from users or were the indirect result of other user feedback. Thanks to everyone who has written in over the last week!

And thanks again for using the Manager!

Saturday, February 4, 2017

Change Log: 2.4.245

Normally, I depend on users to report issues with the Manager.

I will definitely concede that it's not a great system, but I'm a one-man-show here, after all, and it's a system that works well enough.

Except when it doesn't. 

Release 2.4.245 very specifically targets a bug introduced in release 2.4.243 that affected weapon mastery innovations. No one reported the issue, though a number of users would have been disrupted by it, and I was working on some new feature development when I just randomly noticed it happening 20 or 30 some odd times during the last week.

At any rate, release 2.4.245 should a.) fix all settlements broken by the bug and b.) prevent the bug from affecting future settlements. And, in the meantime, I'll be working on a better schedule for reviewing the logs and errors, etc. to hopefully catch some of these things sooner.

Thanks for using the Manager!