Due to popular demand I am going to continue develop Anti-Bounce 3 but I want to make sure to make it as best a possible. For this reason I have assembled a Google Form with some questions I would like all of you to answer. By doing so I can make sure that Anti-Bounce 3 fulfills everyone's needs.
I personally never used anti-bounce. Mainly because most of the nowadays maps are filled with "tricky" parts where you have to bounce to pass it. This is why I keep it most of time off.
Thank you for participating in my survey in regards of Anti-Bounce 3. It has taught me a lot about why people like and don't like Anti-Bounce. This, together with the other important questions you answered will definitely be used to make Anti-Bounce 3 the best version yet.
Anyhow, based on the results I will release a version 2.6.0 of Anti-Bounce already containing recording tools that allow you to record a bounce that happened but went undetected and glitches that you expect to be caused by Anti-Bounce. This will help me a lot in investigating the reason behind these and solving them for Anti-Bounce 3 and the versions afterwards.
For server owners it is very clear that the customization possibilities are still heavily wanted and therefore they'll be kept in, this version will automatically convert your old 'config.xml' file into the new format and will have backwards compatibility for all exported functions and events (although some of them will be marked as deprecated, so update them eventually).
Development of Anti-Bounce version 2.6.0 and Anti-Bounce 3 can be followed on Github.
