Aseco has been decreasing in development because it was meant to be a very slim base for plugins to set on top of it and at a point there has been included much of the core functionality that I wanted.w1lla wrote:Aseco was first because AM and Xymph where in the alpha stage. As aseco now is slowing down development the quest for first server software will be between xaseco and gaseco.
Hope there will be a new gamemode called co-op in the dedicated. Which is like team rounds but only based upon quests or rounds.
It was about the same moment that I also ran into time problems (went studying, found business etc) and from the posts I've read here I am not the only one ...
I am still following these discussions and with the upcoming TM2 I'm pretty motivated.w1lla wrote:well the first author of fast flo-schnell is retired assembler maniac is still trying to make aseco better.
Xaseco is still going strong, tpsgaseco is making a real nice whirlwind of reactions
mistral is a bit behind, and fast is still easy going.
So i think all these combined might make a one hell of a controller.
In my opinion the idea of a collaboration sounds promising, but it takes lot of time to coordinate and discuss - like Xymph has wrote.
My intention would still be some kind of core that takes all the memory-, network-, player- etc etc management and leaves it up to the plugin writers what it would actually do.
Like in Aseco, when you exclude all of the default plugins it's actually doing nothing. All features are built on plugins which are using given interfaces of the core.
Allthough you could extract much of the competing server controller versions' code and encapsulate it into plugins there'd still be much stuff that had to be discussed about, like the handling of windows, interfaces, sw-patterns to use, coding-languages etc.
