Start and server setup

Preparation for start

The server doesn't require any special installation, all that it is necessary to launch it an executable file "@cedserver.exe" from a directory. / server / (since version 0.7.6 the server enters into an installation packet if it at you not is set you always can to set it. In difference from the client the server upon doesn't need installation and if necessary you can copy it in other folder or on other machine). Then the server will suggest to make necessary settings and to create the accounting entry of the manager therefore the configuration file "by @cedserver.xml" will be created. In case of restart all settings will boot automatically from the configuration file "@cedserver.xml", located in the same folder as the server, on it if you want to repeat this step, simply delete or rename the configuration file, you also can create it manually by means of any text editor.

Первый запуск сервера

For operation of the server 5 files are necessary: tiledata.mul, radarcol.mul, map#.mul, staidx#.mul, statics#.mul. The last three files define with which map the server will work, for a map it is also necessary to specify its sizes (Width x Height) in tiles. Sizes of standard map are writed below. Also you is required need flags defining the *.mul version of files. The simplest method it to place these files in one folder with the server and it is simple to specify their names, but you also can place them anywhere, in this case it is necessary for you to specify full or relative paths (e.g. "С:\\Program Files (x86)\Ultima Online\tiledata.mul")

Its important: the server requires exclusive access to files, it means that you can't use one and теже files for simultaneous operation of the CentrEd server + and UOClient/Sphere/RunUo/Fiddler.

Monitoring of versions of files

The server realizes version monitoring a mule of files of the client and the server, thus it is automatically determined the version of used *.mul of files (Pre SA, SA, HS +). In avoidance of errors and problems the server the mule doesn't allow to use to clients files of other version than on the server.

Patch statics and map files

The last clients use a patch files of maps and a statics. These patches are files: @mapdif#.mul, @mapdifl#.mul, @stadif#.mul, @stadifl#.mul, @stadifi#.mul. CentrEd + isn't able to work about a patch with files and if your server uses patches (even if these files are present, they can not be used by the server), it is required to you by means of third-party programs (such as Fiddler) to copy data from patches in *.mul files, then already to use propatchenny *.mul files (don't forget after that to disconnect use of patches on the UO server).

Server up-dating

For server up-dating, it is in most cases rather simple to replace an executable file "with @cedserver.exe" with newer version. However in some cases file editing (ов) can be demanded a configuration in case of change of their format. The message testifies to it about not compliance of the version of the file of a configuration that the first line sets the Version attribute of a root tag. In this case to you costs will address to Wicca for detection of differences and to remove them.

Widespread errors

The server is closed in two cases if you finish its operation or in case of origin of errors, that the server is closed at once after start speaks about errors. For this purpose to look at a log and the description of errors it is necessary to look at a console log, it can be done for example having launched the server from the console (@cmd.exe) as follows _ (having naturally replaced a way with the) _:

1START/B "C:\centred-plus\cedserver.exe" 
Known most frequent errors:
  • EFOpenError: Unable to open file "..." - specified *.mul the file aren't found, the possible reasons: set wrong file paths in the configuration file, the not exists, specified path contains invalid characters or is written in an unreadable look, the file is already used with other program (see above note about exclusive access to files).
  • Incorect data. Check the sizes of a maps and files. - wrong map dimensions in the configuration file are specified (it is necessary to understand that check sizes of a map actually not possibly, this error signals to impossibility to continue operation as the specified sizes don't match number of tiles\blocks in files, otherwise, if the sizes of a map 1 x 4, having specified the sizes 2 x 2 of this error won't be, however the map will be incorrectly displayed.)
  • Error: Error on on bind [10048] - the network Error, the specified port can't be open, as any application or process already uses it.
  • TInvalidConfigException : Version mismatch: 4 <> 5 - Old config file is used. (version 4 instead of ver. 5). Compare example below with your config file to find difference and fix them. Or create new one config file.

Integration of the server and remote access to *.mul to files

By collective operation over a facet as a rule it is required to organize access to *.mul to files to group of people. It becomes individually or by means of third-party software, such as means of remote administration, schedulers, web scripts, jabber\icq bots and other. As an example of the simplest implementation we will give a method based on standard possibilities of wasps of Windows, for this purpose we will create bat the file for server start in one folder with the server of the following contents, in this example the server in case of need automatically copies all *.mul files from the root directory in the subdirectory "backup" after completion of operation of the server, and on operation completion automatically launches the server again with the configuration file "@map0.xml", switching off of the server goes with the help, available to the managers, the appropriate menu item in the client, and the data access is carried out by a subdirectory @backup rassharivaniye on FTP or a local area network.

2START "" /I /B /WAIT "%~dp0cedserver.exe" "map0.xml" 
3ECHO Copying *.mul files...
4XCOPY "%~dp0*.mul" "%~dp0backup" /I /R /K /Y /D
5START "" /B "%~0" 

This method doesn't claim for a completeness, and is only the elementary example for demonstration of methods server management by third-party software (in the majority a case everything is reduced to the same *.bat to files). Not much more difficult, in case of knowledge of the appropriate languages to implement server management through scripts of RunUO\Sphere\Php\Perl or any other, having elementary possibilities of operation with OS.

Use of several configurations

As the server can work at the same time only with one facet, operation with several facets is carried out by server start with different configurations. Naturally for simultaneous operation ports shall be different in each configuration. For this purpose we create some configurations (for example "@map0.xml", "@map1.xml", "@map2.xml") and we launch the server, having transferred as parameter the profile name ("@cedserver.exe "map0.xml""). For automation of start it is possible to make *.bat the file:

1START cedserver.exe "map0.xml" 
2START cedserver.exe "map1.xml" 
3START cedserver.exe "map2.xml" 

Configuration file

Example of the configuration file:

 1<?xml version="1.0"?>
 2<CEDConfig Version="6">
 3  <Language>..\Language\English.ini</Language>
 4  <Port>2597</Port>
 5  <Map>
 6    <Map>map0.mul</Map>
 7    <StaIdx>staidx0.mul</StaIdx>
 8    <Statics>statics0.mul</Statics>
 9    <Width>896</Width>
10    <Height>512</Height>
11    <Prefix>0</Prefix>
12    <Format>0x0000</Format>
13  </Map>
14  <Tiledata>tiledata.mul</Tiledata>
15  <Radarcol>radarcol.mul</Radarcol>
16  <Accounts>
17    <Account>
18      <Name>admin</Name>
19      <PasswordHash>d41d8cd98f00b204e9800998ecf8427e</PasswordHash>
20      <AccessLevel>255</AccessLevel>
21      <LastPos x="0" y="0"/>
22      <Regions/>
23    </Account>
24  </Accounts>
25  <Regions/>

In this example the account "admin" without the password so in case of problems with server setup, it is possible to create the configuration file manually. Editing of data on accounts and regions is carried out directly by the manager through the client. The element Format is a set of the flags which are setting *.mul versions of files of used on the server and the client, the following flags are generally used:

Value Name Description
0х0000 Old Data Format Sets use of the old TileData.mul format. This format is used by the majority of clients, except the last.
0х0001 Pre-alpha Format Sets use of an old format of the files art.mul, artidx.mul, staidx#.mul, statics#.mul. And also disconnects use of texidx.mul, texmaps.mul. This data format was used only in early pre-alpha the client.
0х0002 Use VerData It is not implemented yet.
0х0004 Use DifPatch It is not implemented yet.
0х0008 New Data Format Sets use of the new TileData.mul format entered in a buster of "High Seas". This value by default.
0х0010 Use *.uop files Use LegacyMUL data in MYP format (*.uop). To do this, you also require valid value for Prefix, in other way data from map file can't be read.
Thus, standard values of flags for standard clients:
Client pre-Alpha Alpha Beta SL R TD LBR AoS SE ML SA HS HS\ToL


Flags 0х0001 0x???? 0x???? 0x0000 0x0002 0x0002 0x0002 0x0002 0x0002 0x0004 0x0004 0x000C 0x001C

Value Prefix using only for working with maps in uop format and must contain map index, for example: 2 or 2x for Ilshenar.

Sizes of standard maps

# Facet name Size in tiles Size in blocks Files File size
0 Pre-Alpha 1024 x 1024 128 x 128 map0.mul 3 211 264 byte
staidx0.mul 196 608 byte
0 Felucca (Pre-ML) 6144 x 4096 768 x 512 map0.mul 77 070 336 byte
staidx0.mul 4 718 592 byte
0 Felucca 7168 x 4096 896 x 512 map0.mul 89 915 392 byte
staidx0.mul 5 505 024 byte
0 Felucca (Post-SA) 7168 x 4096 896 x 512 map0x.mul 89 915 392 byte
staidx0x.mul 5 505 024 byte
1 Trammel (Pre-ML) 6144 x 4096 768 x 512 map1.mul 77 070 336 byte
staidx1.mul 4 718 592 byte
1 Trammel 7168 x 4096 896 x 512 map1.mul 89 915 392 byte
staidx1.mul 5 505 024 byte
2 Ilshenar 2304 x 1600 288 x 200 map2.mul 11 289 600 byte
staidx2.mul 691 200 byte
3 Malas 2560 x 2048 320 x 256 map3.mul 16 056 320 byte
staidx3.mul 983 040 byte
4 Tokuno 1448 x 1448 181 x 181 map4.mul 6 421 156 byte
staidx4.mul 393 132 byte
5 TerMur 1280 x 4096 160 x 512 map5.mul 16 056 320 byte
staidx5.mul 983 040 byte
6 Unknown