Information Clarifying different things and concerns

I'd definitely agree with that idea - more transparency about explicit bugs and TODO changes is 100% better (balance changes are understandably more complicated).

I suppose part of the problem is when coding limitations come in and they don't want to offer false promises if it turns out to be impossible. But yeah, I would prefer it that way personally.

I think you can add AFK hurricane to the known bug list, as well as SI being +4 speed unstackable instead of +2 stackable (with booster). Can't think of any more off the top of my head but there must be more!

 

The primary intent of this thread is to explain the ToS and set out precedents, more than consolidate the list of explicit bugs and TODO changes, and while I may have read the whole thing because I have no better use of my time, I think many others would prefer if there was a dedicated thread stating the finer details of the developer road map that kimmy has done before that could possibly (e.g. TODO features: pink bean, TODO bugfixes: shadow star bug, afk hurricane exploit); I won't talk about balance change proposals because I have no good idea how to implement a thread without it devolving from civil discussion into pitchforked witch hunting, as it seems 90% of balance change feedback threads do (but muh nostalgia give me back 4 lines of strafe give me back alchemist wehhhh)

I supposed with each bug there could be like a short description explaining constraints and such without going into much details, just to give the community and idea of whats happening behind the scene. Going back to the shadow star bug for instance, we could have a simple one-liner that says "current limitation: coding limitations. attention: immediate"; this way it would be possible to tell whats top on the list of fixes and sort of when we can expect these changes to kick in.