immerhin hab ich was gefunden
MapMixer Tutorial - Setting up a Dedicated Server
Klappen Overview
This page describes how to use MapMixer in a Dedicated Server environment.
Background
Ok, so you know how to setup a dedicated UT3 server and are wondering how to launch your session using MapMixer from the command line. MapMixer takes control of the whole game session and the first thing that needs to happen is for it to gain this full-control over the session. Strictly speaking, this doesn't happen until MapMixer, itself, actually launches the first match. When you're using the MapMixer Front End Menus, it launches the first match itself, so it gains full control immediately.
In a command-line context MapMixer doesn't actually exist until the first match is launched by UT3, in which case the Mutator part of MapMixer will be invoked. At this point MapMixer will relaunch the entire Session using it's own internal Session Map List! This means that the map that you use to launch UT3 with from the command line is totally ignored and MapMixer proceeds to initialise (or continue) its own Session Map List.
Launching is therefore quite simple, for example:
UT3.exe server dm-placeholder?mutator=mapmixer.mapmixer -login=gamespyname -password=gamespypassword
As MapMixer totally ignores the map you launched the game with, you could even create a blank map with nothing in it, for quick loading. Note that no server configuration options are given on the command line. All configurations are managed by MapMixer.
Configuring
When you launch a server session of any sort with MapMixer, using either the command-line or the UI, it will always be an Advanced Session - see the UI version of the Advanced Session.
Unfortunately at this stage there is no web-admin facility for MapMixer, as I simply just don't have the time and inclination for this sort of thing at this stage. Currently the only way to configure MapMixer for a command-line Dedicated server environment is by manually editing MapMixer's ini files and using some in-game console commands to manage MapMixer. I suggest you test your server configuration on a separate machine and either ftp or scp the UTMapMixer_*.ini files to the server.
Use Server Admin Lists, available from the Setup Tab in the Advanced Configuration Menu (or see the UTMapMixer.ini file in the section [MapMixer.MapMixer_Data_ServerAdmin]) to manage your actual server parameters, such as server name and password etc.
Configuration Files
MapMixer's configuration is stored in multiple ini files. The reason for this is that there is a lot of data stored and keeping them in separate files helps to separate the groups of data and simplifies management of them if you need to update one type of information on a server. Descriptions of the relevant MapMixer ini files is as follows:
ini File Description
UTMapMixer.ini Core MapMixer configuration file. Holds settings for Gametype configurations and their rules, as well as Server and Session Configurations.
UTMapMixer_MapDatabase.ini Holds entire listing of installed maps, grouped together in prefixes. An important file as it stores important information such as map author recommended player counts, author name and user generated data such as rating and comments.
UTMapMixer_Session.ini Holds the current Session Map List, as well as all parallel map lists when Manual Source Switching is activated.
UTMapMixer_ListsBots.ini User created Bot Lists
UTMapMixer_ListsFactions.ini User created Factions
UTMapMixer_ListsGameRules.ini User created Game Rule Lists
UTMapMixer_ListsMapDefaults.ini User defined Map Defaults
UTMapMixer_ListsMaps.ini User created Map Lists
UTMapMixer_ListsMapSources.ini User created Map Source Lists
UTMapMixer_ListsMutators.ini User created Mutator Lists
These files should be transferred from your test machine to the dedicated server machine. If possible, you could also manually edit them on the server via a text editor, but care should be taken when doing this.
MapMixer Client Packages
MapMixer is designed from the ground-up for a network environment and thus there are separate server and client file packages. A player connected to a MapMixer server only requires the following files, which will be pushed to the client on connection, if required, as usual:
Package File Description
MapMixerClient-xxx.u (xxx = client version, eg 300). Core MapMixer client-side code package.
MapMixerClient_Sounds.upk Client-side sounds package.
MapMixerClient_Gfx.upk Client-side texture package.
Map Voters
Map voting is another thing I don't have the time or inclination to use or test. Normally MapMixer expects that all map switches will be called by itself, however I have incorporated the ability for MapMixer to accept externally invoked maps, in which case it will add the map to its Session Map List. This means that in theory, a Map Voter should be able to run in parallel with MapMixer, however this is only in theory and has not yet been fully tested. (If only I had more time and resources.)