Old post:
TL;DR
When the MXLS project started, we all underestimated it. It started as a dream, a project on the side. This collaboration between me and Marco started out as a joke in the staff section of the old forums. And eventually, as it began progressing, and as we were slowly seeing it's potential, it turned into something really big. And we wanted to push it so much, and the task list grew, and grew and kept growing.
Obviously, it ended up taking much more time than planned. And every deadline I've tried to give were not met. There are a few reasons for that, but the main one is we underestimated the project, more than once. Not only we were too ambitious and ended up with an impossible task list (which we broke down some time ago), but we also underestimated the fact that.... It's D2. Most tasks end up taking ten times the time it should take. Often because of bugs from blizzard, because of code that was written (by Blizzard) with no future scalability in mind, overly interlinked pieces of code (when you need to rewrite a dozen of things for one feature.... something's wrong), etc. I've also started the project with rookie modding/programming experience, and with the experience I've earned over time, a lot of what was done in the beginning of the project was rewritten. There's also the fact that, in the beginning of the project, things were messy. We had no actual task list, the project wasn't on git, and my development flow back then, basically stem down to "I want to work on x feature today".
Still, I keep working on the project. Yes it will come out. When? That's what this thread is all about: I don't know when, so stop asking.
The Median XL project keeps getting updates, and it keeps getting better with every patch, sigma or not. So stop waiting for it, and it will come out when it's ready.
We don't have any ETA. The time I have to work on this project varies a lot, and every time I work on a new task, I come across new surprises in Blizzard's code. There is no way we can properly determine a date for the completion of this project in it's current stage. Still, I've worked out something for those who may want to follow the general progress towards completion of the project.
This list here, is the complete task list. You may notice it also contains bugfix tasks. Since new bugs are bound to be found during development, and during testing phases, this task list may vary with time. But what you need to understand basically is, as long as this list isn't empty, the project is not finished.
Here you can see an overview board that lists every tasks classed under three different "task types"
And finally, here you'll be able to see the milestone overview. This features a completion percentage of the project, number of opened tasks (issues) and number of closed tasks, etc. This is a global overview of the project's progress. Of course this doesn't include all the tasks that were already completed, or it would have hundreds of tasks. I've created the task list from the remaining tasks, as of today. I will also try to consistently log the time I spent under each individual task, so that you can have an idea of how much dev time was spent on each task.