Quote:
Originally Posted by LoneAngelIbesu
I don't understand why you are assuming that it wouldn't work. There is no reason why the GDT cannot develop servers, if not a single server. Obviously, with how many scripters we have we wouldn't need everybody to be working on a single server. But I think that a lot of you guys are completely missing the forest for the trees, if the GDT really is about improving Graal: this game is about playerworlds, not about GS2 documentation and pre-made tools and packs.
We can throw all the resources we want into the developing pool, but it's simply not as large as it once was. It's the least rewarding aspects of the GDT, in terms of how the team can benefit Graal. People don't just come to Graal to develop. They arrive first at a game and then become developers. Focusing on making tools and guides for a small pool of developers is kind of inconsequential if players (new developers) aren't coming in.
There are servers that need to be worked on and that can be improved. At the very least, the GDT can and should step in there. If there's enough impetus and reason, the GDT can and should develop an original server. These are the things that can really help Graal. I don't think we should forget about documentation and small projects, but pigeonholing the GDT into serving only those functions simply ensures that the group remains in the same position as it is right now.
|
I
agree that most important thing for Graal is new players.
I
agree that a good server would be one of the major pieces in getting new players.
What does a good server require? Just off the top of my head... direction, management, resources.
So why hasn't there been a good server already? Most would argue lack of resources.
Your point seems to be that if we just shove "GDT" into the resources slot, we will get a good server. This is where I disagree.
If everyone was interested enough in a single server more than all other servers, they would have gotten together and developed it already.
But, the obvious counter-argument is that "the GDT has a command structure to make people do certain work they aren't 100% interested in". This is where my point lies.
How is the management of the GDT different from a server's management? What in the GDT makes it possible to unite uninterested developers into doing something?
Nothing.
In summary...
The ideal server developers are many and willing.
The current server developers are few and willing.
The GDT are many and unwilling.
We can still utilize the GDT for small projects which don't require so much will, but not for something like developing a server.