IRC Channel Discord Channel

RO Patcher Lite Help (c) 2009-2024 Ai4rei/AN This pre-release content is subject to changes.

Usage

Interface overview

Overview of the RO Patcher Lite interface
  1. Window menu
    Houses the patcher menu under entry 'RO Patcher Lite'.
  2. Titlebar
    Displays overall process while patching. Newer versions are also branded with the type of server they belong to.
  3. Progressbar
    Displays the progress of a single task, such as downloading a file or committing changes to the GRF.
  4. Status line
    Provides information about the patcher status including error messages.
  5. Start button
    Unless the patcher starts patching automatically, it initiates the patch process. When the patcher finishes patching successfully and there is a client available, it starts the game. Shortcut: ENTER
  6. Close/Cancel button
    Closes the patcher. If there is a patch process in progress, all changes already made are reverted. Clicking 'Close' with held-down SHIFT key after successful patch process will keep the patches, instead of cleaning them up. Shortcut: ESC
↑ TOP

Patch process

↑ TOP

Normal

This is the default mode, in which the patcher starts patching immediately after launch.

Command switch: /test and donut (official)

Allows to bypass 'deny' in 'patch_allow.txt', which is set during maintenance on official servers, to prevent you from patching. It is not recommended to use it, unless you really know, what you are doing, since you might receive corrupted or invalid patches, that aren't available later.

Command switch: /autostart

Makes the patcher always start the patch process automatically instead of waiting for you to press start. Intended for shortcut usage.

[v3]

Command switch: /nocleanup

Causes all downloaded patches to be kept after patching. Intended for shortcut usage.

↑ TOP

Manual

There is a video available on this section.

Manual patching involves downloading required patches in advance (for example on someone else's computer with faster connection) thus relieving the patcher from the download task. This method is also supported by the official patcher.

The files can be either downloaded by someone else's patcher (see above) or with any common browser or FTP client. Downside to the latter is, that the patch server address must be known. The downloaded files must be then placed into same folder as the patcher, which will use them, resides in. When the patcher is started, it will still connect to the file server, but only to retrieve meta data of the patches. It is not possible to patch completely without an internet connection.

↑ TOP

Archive consistency check

Command switch: /testpak

Tests the entire main GRF archive for errors, like invalid header, file table or corrupt files. Note, that this process may take a while for larger archives and it is normal that an amount of about 3~15 files do not work correctly. The client doesn't bother about it, since it doesn't check for any extraction errors from uncompress. Note: In older releases this switch was called /test, due to an initial misconception.

↑ TOP

Reclaiming wasted space

Command switch: /repak (official)

Forces complete rebuild of the main GRF archive reclaiming all wasted space. Note, that this process may take a while for larger archives and you must have at least same amount of space free, as the main GRF archive takes up. The patcher asks you automatically about repacking, once too much wasted space is detected inside the archive.

↑ TOP

Last built on Sun, 31 Mar 2024 12:08:43 +0200.