Dedicated server software

[Slig]

Still it could be a good idea to make something "dediplanet" where there is a commune basis that captures all callbacks, and saves relevant info to a database.

you mean the callbacks of all dedicated ? then it's just a joke, have you some idea of the number of callbacks that a script receive from a single dedicated ?

After that the "personal touch" of each coder, working with different skins and mods.
Something you can see for example in the phpbb software, where users and coders share their skins and mods (for simple extra functionality, but also you can find real big addons.

plugins of each script are already shared, like each forum system has its own plugins

I mean, you are almost all build around an aseco core with more or less different results for each one.

Are you joking again ?
The various (x)aseco script mostly share the same core (but not exactly, else only one would exist), but other script use a different core. Of course they share some similar things as they are built around the dedicated callbacks, but many things are different.

[www.e-gekko.net]

Come on Gekko, 6 years ago TM didn't even have a dedicated server yet, so there can't have been any FAST

Ops sorry!!! Damn Zooz is right!!! noooOOOOOO!!

Also agree with Xymph...

[Xymph]

Still it could be a good idea to make something "dediplanet" where there is a commune basis that captures all callbacks, and saves relevant info to a database.

I don't think you mean what that seems to indicate, as Slig already commented.

Anyway, collecting all server info into one place is not a bad idea, but then why is this TM-Wiki section so barren? I'm not saying it'll go like that again for TM2, but it doesn't exactly inspire confidence either.

I mean, you are almost all build around an aseco core with more or less different results for each one.

The FAST, Gery and Onyx cores are vastly different, and we don't know anything about the cores of Truck, TMSPS, TMSC, TMST or ASRM (to name just a few small controllers) because their sources aren't public AFAIK. So that comment is too broad and inaccurate.

[w1lla]

well maybe for the strange reason.

Why can't http://methods.xaseco.org/ be put in to the tm-wiki.

That's the strangest part ever...

So many hands and so little helpers to find information about it.

Also a nice things might be that the software of the dedicated is update with documents and every .php file is also documented.

SpectatorUI is for example a nice manialink for spectators on a relay.

[Xymph]

Why can't http://methods.xaseco.org/ be put in to the tm-wiki.

That's the strangest part ever...

Not strange at all. Those method lists are dynamically generated by PHP scripts that run against the actual dedicated server versions and determine the diffs. Plus there's JavaScript in them for some interactive features. You'd have known this if you have downloaded the source. So it's funny you're using this as example, as these are precisely the pages that cannot be embedded in a Wiki system.

Obviously most other static info pages on various sites could be wikified, but it takes a concerted effort by someone or a small team to make that happen. For TM, that never came about.

So many hands and so little helpers to find information about it.

I've done my best updating a few TM-Wiki pages on technical topics, and some other people contributed over the years, but as a whole it's been a meager effort. Why? Your guess is as good as mine... maybe there aren't as many willing and able hands as you think.

SpectatorUI is for example a nice manialink for spectators on a relay.

That name doesn't exist in my ML browser.

[Slig]

SpectatorUI is for example a nice manialink for spectators on a relay.

That name doesn't exist in my ML browser.

It's a php script which is in the dedicated archive
RemoteControlExamples\PhpRemote\SpectatorUi.php

[Xymph]

SpectatorUI is for example a nice manialink for spectators on a relay.

That name doesn't exist in my ML browser.

It's a php script which is in the dedicated archive
RemoteControlExamples\PhpRemote\SpectatorUi.php

Oh, thanks. How typical of w1lla to provide incomplete information so it's unclear what he's talking about.

[svens]

I've made the experience that wikis aren't liked by the users. Navigation in a wiki is very problematic and you'll shortly loose the overview if there aren't (very) good index pages and it gets worse if users don't know where and what to search for. For non-technical people adding content is way too difficult (What's these cryptic signs?) and technical people prefer to stick to html directly instead of learning new syntax for images, tables, etc. For both groups a WYSIWYG html editor is the better choice . I had no success with wikis and that's why I don't like them too.

Not strange at all. Those method lists are dynamically generated by PHP scripts that run against the actual dedicated server versions and determine the diffs. Plus there's JavaScript in them for some interactive features. You'd have known this if you have downloaded the source. So it's funny you're using this as example, as these are precisely the pages that cannot be embedded in a Wiki system.

I guess it's more about having a list of methods. The description of most methods is insufficient, a static page with some helpful comments on each method would be an improvement over the current situation.

It's a bit late to start with all these things for Trackmania Forever, but I hope that with Trackmania 2 there will be a collaboration for making good documentation (or other things) and I also hope that Nadeo provides some more information this time, as the whole topic's going to be a lot more complex with the other ManiaPlanet games.

[tcq]

Something like the java api would be a nice.
In this way, i really like the xaseco site with the listed methods.

[weerwolf]

Hmm, although the subject most discussed (server controllers) was not my intention to discuss, it turned into a nice topic. Shall i change the topic name to TM2 server controllers?