Important announcement regarding the 2017 Fall Event

[mrmin123]

Attention!

After reading up on some of the announced feature additions and changes to Kantai Collection for the 2017 Fall Event, I am making the decision to halt development of kancolle-auto and retire it in order to focus development of kcauto-kai. Unfortunately, due to real-life circumstances I will not be able to get kcauto-kai to a beta-testable state for another two or three days.

It is highly likely that there will be updates this Event that will break kancolle-auto beyond what updating assets will be able to fix. Development focus, however, is on kcauto-kai.

So, until the kcauto-kai beta is ready, please use this thread to upload Event assets. A separate branch with 2017 Fall Event assets will not be maintained for kancolle-auto. 2017 Fall Event assets will not be merged to master post-event. For all intents and purposes, kancolle-auto is now under a code freeze!

So how will I know when the kcauto-kai beta is ready?

I've created a placeholder kcauto-kai repository for now, and the code will be launched deployed to it when ready. Watch it, Star it, whatever. You can also join the kcauto-kai Discord for up to date information, discussion, and help regarding kcauto-kai (note that this Discord is separate from the official unofficial kancolle-auto Discord, which is where you should go for kancolle-auto and general Kantai Collection discussion).

When it launches, as kcauto-kai will be in beta, please keep in mind the following:

• It will not be at feature-parity with kancolle-auto - kcauto-kai currently has features that kancolle-auto does not, but it also does not have features that kancolle-auto did
• It might not be as stable as kancolle-auto - I've done very passive stress testing, but many edge-cases have not been encountered or debugged
• It might have some superfluous actions - they shouldn't be anything that spams game state changes, but there are some mouse rejiggering that have not been fully optimized yet

That said, I will tell you the following about kcauto-kai:

• It will be more efficient - multithreading, optimized region searches, and logic improvements have made for a faster-operating tool (disclaimer: incredibly vague and untested statement; do not take at face value)
• It will be easier to maintain - while kancolle-auto was built piecemeal over the course of two-plus years, kcauto-kai was developed from the ground up with a more lucid project vision in mind
• kcauto-kai will be at feature-parity with kancolle-auto when it comes out of beta
• kcauto-kai will be maintained going forward for the foreseeable future, while kancolle-auto will be retired after (or during) this event

Whether or not you decide to switch over to kcauto-kai when it's ready, I apologize for the inopportune time this code/development freeze is coming in at. If you have any questions or comments please message me on the kcauto-kai Discord or DM me on Discord (mrmin123).

[waicool20]

Have some minor coordinate updates to fix formation choosing while sortieing in the latest update in my branch, doesn't add support for the new formation which is at (650, 319, 119, 50). Don't know if you want to merge it into a sub branch or master so I'll just tell you first here.