RO Patcher Lite Mirror Application Form

Following are the requirements the patch server mirror has to meet:

• Free public HTTP server (file size information and no HTTPS redirects) or FTP server (read-only anonymous login, enumerable directory contents, file size information and working passive mode)
• Each connection should have at least 40KB/s bandwidth, minimum is 10KB/s
• Latest patches must be available no later than the following Friday, 01:00 (AM) UTC, unless you serve old patches only. They are released for download by the patcher one or two hours after that.
• Patches must be unchanged^[1],[2]. The patcher discards files, that do not comply with the MD5 hashes and sizes.
• If you want to serve patches for multiple server-types. Apply for each type separately.

All fields are required, unless noted otherwise.

Description	Value	Example
Host name/address Hostnames should provide at least one IPv4 address		kromirror.example.com
Protocol	HTTP FTP
HTTP/FTP port optional, leave blank for defaults		21
HTTP/FTP path to patches		/Patch
Capacity max. amount of simul. connections, affects order in which the patcher selects mirrors		30
Server type	kRO Main[2],[3],[4] kRO Sakray Renewal[2],[3],[4] kRO Zero[0],[1]
Lowest progress that can be served. This is the patch progress ID the patcher at least has to have to make use of the mirror. For example, if you serve patch.txt patches from 2100 onwards, the minimum progress needed is 2099. You do not have to serve all existing patches, past 3 months are fine, too.
Minimum progress (patch.inf)		2060
Highest progress that can be served. This is the patch progress ID the patcher at most can have to make use of the mirror. For example, if you serve patch.txt patches up to 2200, the maximum progress allowed is 2199. You do not have to serve all existing patches, random range of the past is fine, too.
Maximum progress (patch.inf) optional, leave blank for latest		2200
Maintainer attribution, as short as possible, ASCII printable characters only		Ai4rei/AN
Contact e-mail not public, used to notify of issues with the mirror		mail@example.com
Comments not public, provided as part of the application		only until 2016-07-23
Existence	I confirm, that the mirror server stated above is up and ready to serve patches in the given range.