-
Notifications
You must be signed in to change notification settings - Fork 1
Doc_Halo1_MapDownloadMasterServer
The master server exists so that a normal web server with PHP and MySQL can be used as a map download server.
When the client needs to download a map it will first try to download it from the dedicated server it is connecting to. If the dedicated server is not set up to serve map downloads the client will then attempt to download the map from a list of "Master Servers". It is those servers that this document discusses.
The term "Master Server" has no real significance, they are just called that because they serve the entire userbase rather than individual multiplayer servers.
IMPORTANT: I (TheFieryScythe) am no expert of MySQL, PHP, web security, etc. so you use this software at your own risk. I'm happy to hear of any problems, suggestions, improvements, etc. that you have so feel free to contact me or leave an issue on the google code page if it's problem you are having.
The master server infrastructure relies upon website hosts being willing to volunteer some of their bandwidth to help make Halo Custom Edition more accessible to new players and encourage servers to run custom maps, which is the ultimate goal for the map download system.
If you want to be awesome by helping out in this, and you have a website with a decent amount of bandwidth to spare, you can do so by running a master server on your website.
IMPORTANT: If you wish to host a master server you should expect to be doing so on a paid web hosting package. Also, check that your chosen web host's terms of service are appropriate for file serving of this kind.
As a baseline we would like master servers to serve at least 5 of the more popular maps. Quality maps are preferred, and no duplicates or derivative works (such as chaosgulch_CMT_7
and such). Hosting a map that is already hosted on another master server is fine as the client will randomly choose which server to download from which helps to distribute the bandwidth cost.
The master server application is a collection of PHP scripts that provide the same functionality as the OS dedi with some management scripts thrown in for good measure.
NOTE: I will assume you already have your PHP and MySQL set up as information to do that is beyond the scope of this document.
The first thing you will need to do is setup the application on your web server.
All the files you need are in the *OS Source Dir*\OpenSauce\Halo1\Halo1_CE_MapServer
folder. Which you get when you sync/download the OpenSauce source code.
In the Halo1_CE_MapServer
folder you will see two files and one folder:
config.ini
Halo1_CE_MapServer.sql
web_root
The Halo1_CE_MapServer.sql
file defines the SQL map database that will be used to store information about the map's and their parts. You need to import it into your MySQL database. Once imported you will have a database called Halo1_CE_MapServer
with three tables, map_list
, map_part_list
and map_server_users
.
map_list
Field | Type | Description |
---|---|---|
file_id |
int | Auto incrementing index for the map entries |
map_name |
string | The maps name without its extension |
map_compression_stage |
int | Enum stating where the map processing got to in the event of a failure |
map_compression_type |
int | Enums stating what compression was used on the map |
map_md5 |
string | The MD5 checksum of the map |
map_uncompressed_size |
string | The size of the map before being compressed |
map_compressed_size |
string | The size of the map after being compressed |
map_parts_path |
string | URL to the maps parts, relative to the root URL |
map_part_count |
int | The number of parts the map has |
map_part_list
Field | Type | Description |
---|---|---|
map_file_id |
int | ID of the map this part is associated with |
part_id |
int | The parts index within the maps parts |
part_name |
string | Name of the part including its extension |
part_md5 |
string | The parts MD5 checksum |
part_size |
string | The size of the part |
map_server_users
Field | Type | Description |
---|---|---|
index |
int | Auto incrementing user index |
username |
string | The accounts username |
password_hash |
string | A hash of the accounts password |
user_control_permissions |
int | Bitmask defining what controls this account has over the user database |
map_database_permissions |
int | Bitmask defining what controls this account has over the map database |
You need to copy the config.ini
file to somewhere on the web host that CANNOT be accessed through the website. You then need to edit it to fill in your custom configuration parameters.
map_database
Parameter | Usage |
---|---|
username_readonly |
The username of the readonly MySQL account to use when reading from the map database |
password_readonly |
The password for the readonly MySQL account |
username |
The username of the MySQL account to use when reading from and writing to the map database |
password |
The password for the MySQL account |
data_source_name |
The MySQL database location and name, e.g. mysql:host=localhost;dbname=Halo1_CE_MapServer
|
map_server
Parameter | Usage |
---|---|
map_dir |
The absolute directory on the server that maps/definitions are saved to before being processed |
map_compressed_dir |
Location to use as an intermediate directory when compressing maps |
map_parts_path |
The folder to save map parts to |
bandwidth_cap_soft |
The daily bandwidth limit at which point maps stop being served |
bandwidth_cap_hard |
The daily bandwidth limit at which all data stops being served |
The two bandwidth cap values control the daily bandwidth limit for your server. The persistent data for this is saved to the state.ini file defined by you in server_state.php
.
The soft cap is the point at which map part definitions stop being served. It is called a soft cap because in the case of a map part definition being served just before the cap is reached, the user will be still able to continue to download the maps parts, and other downloads in progress will not be interrupted.
The hard limit is the opposite as once that cap is reached all following download requests will be rejected.
You should leave a reasonable margin between the soft and hard caps so that once the soft cap is reached there is enough bandwidth for any map downloads in progress to be completed. Your ideal margin will vary depending on the size of the maps you are serving and the amount of traffic you get.
If you do not want to use the bandwidth caps, set them to 0 and your bandwidth will be used without limits.
To get the map server on your web host you need to copy the following into the directory on your web server that you want to use for map downloads:
web_root/
hce_map_server/
css/
mainstyle.css
map_database/
map_entry_add.php
server_admin.php
server_login.php
map_download.php
You will also need to copy the web_root/hce_map_server/admin
folder to somewhere on your web server outside of the web directory. For convenience this could be in the same folder as your config.ini.
Once your files are on your server you need to edit a number of files to set your servers file paths:
-
*admin folder*\common\config.php
- Add the absolute path to your config.ini to the$config_path
variable on line 52. -
*admin folder*\map_download\server_state.php
- Add the absolute path to where yourstate.ini
should be saved to the $state_path variable on line 42. -
*web directory*\map_download.php
- Set the absolute path to the admin folder toset_include_path
on line 11. -
*web directory*\hce_map_server\server_login.php
- Set the absolute path to the admin folder toset_include_path
on line 11. -
*web directory*\hce_map_server\server_admin.php
- Set the absolute path to the admin folder toset_include_path
on line 11. -
*web directory*\hce_map_server\map_database\map_entry_add.php
- Set the absolute path to the admin folder toset_include_path
on line 11.
With your config.ini
setup, your database imported and your scripts in place your map server is ready to have maps added.
*web directory*\hce_map_server\server_admin.php
is the main administration script and controls the user accounts and map database.
To load the admin script simply enter the URL to your server\_admin.php
in any browser.
The map server has a user account system for allowing access to the admin pages and controlling who can change what. When you imported the map servers sql database a default user account with full permissions was added so that you can get initial access to the admin pages. The default user uses "admin" as both the username and password.
IMPORTANT: You should create your own account as soon as you can and delete the admin account.
IMPORTANT: It is recommended that you use an encrypted connection when logging in and using the server administration pages.
To add a user go to the User Control page and select Add User. Enter a username, select what permissions the user should have and select Add User.
NOTE: If you are creating an account to replace the admin account, give yourself full permissions.
A new user account will be added to the database. When a new user is added a random 8 character password will be generated for the account. This is only displayed to you once, so be sure to copy it and give it to the account owner. The account owner should then log in to their account and change their password using the My Account page.
To edit a users permissions select Edit User on the User Control page, change the permissions as necessary and select Save Changes. The changes will take effect the next time that users signs in.
NOTE: You cannot edit the currently signed in user account.
Should you want to remove a user, select Remove User on the User Control page. You will be asked to confirm or cancel the removal and the user will be deleted if you select Confirm.
NOTE: You cannot remove the currently signed in user account.
To change your password, go to the My Account page, fill in the current, new and repeated password fields and select Save Changes. If all fields are correct your password will be changed immediately.
NOTE: Only the account owner can change their password. If a user forgets their password, their account will have to be deleted and re-made.
You have a couple of avenues for adding maps to the map server. For both you will need FTP access to the maps folder on your server (The map_dir
defined in your config.ini
).
Your first option is to upload the map file directly to that folder. Once uploaded go to the Map Database page and you will see your map added to the "Map Files" table. Because the map was uploaded as-is it needs to be processed (compressed and split) to be made available to download. The server admin scripts do this when you select the "Add Entry" button.
Once selected the map is compressed using the Zip algorithm, split into 1MB chunks and copied to the map parts directory. Information about the map and its parts is added to the map database and made immediately available to clients.
IMPORTANT: The Zip compression occurs on the server as part of a PHP script. This will take some time to complete and will also consume significant CPU resources, so make sure your web hosting package is suitable for the job.
The second option available to you is to process the map yourself locally, and upload the map parts and definition to the server. This is the preferred method as 7zip compression is used by OpenSauceIDE which results in smaller file sizes and doesn't put any load on the webserver.
NOTE: The process for compressing a map can be found here.
To upload the map data put the maps part definition and parts in the maps folder on your server, then go to the Map Database page. The map will appear in the list and you can select Add Entry to add it to the database. The definition will be loaded and it's information added to the database. The parts will be copied to the map parts directory under the web root.
Once your map has been added successfully, you can select Delete File(s) to remove it from the maps directory on the web server, or you can delete it via FTP.
If you want to remove a map from your map server and therefore stop people from downloading it you simply need to select Remove Entry on the map database table.
When the client is loaded it downloads an XML from Halomods that lists the master servers that are available. In order for your server to be used it needs to be on that list.
Once your server is set up you can ask Kornman or myself (TheFieryScythe) to add you to the pool. We need to know the following to process your request:
- The URL to the map_download.php on your server e.g
http://os.halomods.com/Halo1/CE/MapDownload/map_download.php
- The initial set of maps you will be serving so we can test your server and check it is functioning correctly
- Contact details so that we can inform you of any problems that arise
- A string of text max. 63 characters long that will appear in-game as your servers name/title when your server is being used, which could be your websites address for instance.
- A string of text max. 255 characters long on a maximum of 3 lines that is displayed in-game when your server is used, could be something like "Please visit our site" for instance.
We will test your server to check the map downloads are working correctly and then we will add it to the server list.
NOTE: We reserve the right to remove your server from the pool at any time, though we would try to let you know if we do.
You will be free to add maps to your server without informing us. However, we may request that you stop serving certain maps if there is a version conflict with other servers.
-
Wiki Home
- Halo 1
- FAQ
- Getting Started
- Related Forum Threads (Legacy)
- Post-Mortem
- Gamers
- Modders
- Server Hosts
- HTTP Server
- Map Download
- Programmers