@

: Thanks for the feedback
----------------------------------
I want to push an update next week that should fix most small bugs (attack errors not displaying / NullPointerEx, max train queue, proxy password saving).
I know it has been a while since the last major update, and it might seem like I stopped working. I actually did code a lot, just not for DSX but for different (paid) projects.
There is a lot of work to be done [internal refactoring (new settings, time, multi account / seperate sessions), new gui] and I only have limited time to spend.
For comparison: This project has about 6400 source code lines (excluding comments & blank lines). While this is no indicator for code quality, it should give you an idea of the project's size / time spent.
How to continue with the bot?
I thought about starting a seperate open source project focussing on normal users and hopefully working with other developers to be more productive and release features more quickly.
This does introduce more challanges like how to ensure software quality, how to fairly distribute donations etc.
If you have experience with coding in Java or Mono/C#, specifically multithreading, browser automation or HTTP packets, feel free to message me on

, Skype or here on epvp
DSX could stay premium / commercial botting oriented then. Unfortunately I am unable to make DSX open source for various reasons.
To be clear, the bot will still be continued. I just want to split commercial and advanced features for normal users (GUI, better farming, attack timing / handling) to different projects.