Despite all the problems that Obsidian has heaped on our collective plates, I remain optimistic. There is a reason for this.
Despite all the toolset errors, the idiotic code that comes with it, the broken functions and everything else that's wrong with that toolset, I can still get by. The creation of Aucklorn Mill, for me, was not only enjoyable, but relatively bug free. I crashed a couple times, lost a few minutes of data, but with extensive back-ups (I actually took up about 10 GB of space backing up the Aucklorn Mill addition) I was able to start and finish it within a few weeks.
In fact, the most pain was integration and the bug fixes that followed, and that was only a few hours of frustration. When you see your creation live, however, and being enjoyed by a plethora of adventure-seeking players, all the spite, bile and frustration just seeps away. I will tell you—the positive feedback posted here is a boon to the builders. Knowing your content is appreciated and enjoyed is a great motivator to head back into that breach, once more.
Most people, however, will not encounter the evils of the toolset. It is the player-client that many will become frustrated with. To be honest, the only thing that
really pisses me off is the transition crashes. When that is resolved, I believe everything else will fall into place. And I
do believe it will be resolved. One way or another. It is comforting alone to know that Obsidian is working on it. Most of our antagonism for Obsidian is due in part to the bugs that we, the multiplayer community, have encountered. Obsidian, however, has shown that they
do want to correct their creation. We will see how long it takes them, however.
So the "stallling" of the impending campaign is partially platform related. We certainly don't want to head on into the main story with a buggy client. In the end, however, it won't be the deciding factor. The campaign will be unveiled.
Keep in mind that Dasaria 1's campaign never really was unveiled within the first year, or year and a half. DM and Developer involvement was largely limited to content generation, and minor DM events. There were large, significant pushes (The Ruins of Dasar, the emergence of Talon Hold, the return of the Monarchy) led by the DMs, but these developments occurred well after the server had been adequately established. A lot goes into establishing the community, culture and ambiance of a server. I believe the staff want a good, concrete foundation before they step forward and begin unveiling the second generation of Dasaria's story. They want a multitude of areas so the world feels a little larger than Cear's few districts. Established characters, factions and stories will all add another depth to the server alongside a developing campaign.
And yes, unfortunately RL gets in the way, and there are a few members of the senior staff that are tending to more important things right now. It's a pendulum, really; we will see moments where the server undergoes rapid development, due to Staff Activity and involvement. When work, family and other RL concerns get in the way, however, this type of development will naturally being to slow. This is the way of things.
If any of you remember from the interview with NWN Podcast, the Development Team had planned to start unveiling the campaign "in a few weeks". That is, of course, before RL steps in to rear its ugly head (damn real life interfering with make-believe!) We're not too far away, and compared to Dasaria 1's development, we're actually ahead of the game.
So, with these things in mind, I am incredibly optimistic. I love this community, I love this development team, and most of all, I love Dasaria. Her story remains incredibly important to me, and despite whatever platform issues plague her development, rest assured; I will be motivated to see that she
continues to tell her story.