Built with UnRAR and MadMilkman.Ini
- Works with all of our sets. TW2008, CN2012 and NA2016.
- Extremely easy to setup without any coding knowledge.
- Automatically check, download and extract patch archives.
- Includes both server and client configuration files.
- Allows modification of application settings through server-side configuration, eliminating the need to distribute a new executable.
- Features a maintenance mode that can deactivate the start button through the server-side configuration.
- Features the ability to reset the patch version.
- Features the ability to optimize the client by selectively disabling certain files, typically .nif files, in order to mitigate in-game lag. The list of files can be modified and updated as desired.
- Features the ability to delete specific files. This is useful, especially when you accidentally patch a server-side file, such as 'IteminfoServer.shn.' Additionally, you can also add and update files to the list.
- Features the ability to perform integrity checks. By using this, a player can better pinpoint the source of a possible "Client Manipulation" error.
To make your patch archives accessible to the public, you'll require a web server of some kind. This may include a VPS, dedicated server, cPanel, web storage, or even an FTP server. The crucial aspect is that you have a publicly accessible server to download your patches from, and that the application can read your server-side configuration file in the .ini format.
When using IIS as your web server, it is necessary to create a MIME TYPE entry for both the .INI file and .RAR archive.
.INI
text/plain
.RAR
application/x-rar-compressed
You will need to place the following files in the root directory of your client.
FiestaHeroes_UL.exe
MadMilkman.Ini.dll
UnRAR.dll
Afterward, you must also copy this folder into your root directory, ensuring that you maintain the folder structure by copying and pasting the folder.
reslauncher/launcher.ini
We will now proceed to edit your launcher.ini file:
[Setup]
; Ensure that you include a forward slash, "/" at the end of your URL.
; Example: http://192.168.1.100:8080/
PatchServerLocation=http://127.0.0.1/
PatchVersion=0
Change PatchServerLocation=
to the location where you're hosting your patch files.
For example:
PatchServerLocation=http://fiestaheroes.com/
Navigate to your wwwroot folder and copy the contents of the folder. Paste the copied files into the root directory of your web server. By default, patch archives are stored in the /patches
directory, although this location can be modified in the server-side configuration file.
Next, open your Config.ini
file. Comments have been made to help explain what each section is for.
[Application Settings]
Name=FH: Universal Launcher
; Image resolution: 500x95
; If this URL becomes invalid, the launcher will not display any image.
Banner=https://archive.fiestaheroes.com/_Tools/fhul/fhul.jpg
[Archive Settings]
; The FileName pertains to the start of the archive name. When creating your patches, append the version number after the FileName. For instance: patch1.rar.
FileName=patch
; You can assign any file extension of your preference. For instance, you may choose to use ".xkl" as an extension.
Extension=.rar
[Version]
; This pertains to version control for your patch files. For instance, if you have the following patch files: patch1.rar, patch2.rar, and patch3.rar, then your version number would be 3.
; Example: PatchVersion=3
PatchVersion=0
[Game IP]
; This will be the game server IP the Fiesta.bin will start with.
IP=127.0.0.1
[Login Port]
Port=9010
[Executable]
File=Fiesta.bin
[Download Directory]
Location=patches
[Control]
; Modify this setting to deactivate the start button while performing maintenance on your server. 0 = Disabled, 1 = Enabled.
MaintenanceMode=0
; Modify this setting to enable the utilization of the integrity check. This will use MD5 for comparing specified file hashes. 0 = Disabled, 1 = Enabled.
IntegrityCheck=0
; Modify this setting to enable file deletion. This is useful if you accidentally patch over a server-side file. 0 = Disabled, 1 = Enabled.
DeleteFiles=0
; By using this, a player can better pinpoint the source of a possible "Client Manipulation" error.
; Use the file path you would like to check. I have some listed examples below. This list can be updated as well, while following the same format.
; Additionally, it is important to maintain the order of hashes when checking. Therefore, the first line in this section will correspond to the first line within "[IntegrityCheckHash]".
[IntegrityCheckFile]
File=Fiesta.bin
File=ressystem/ItemInfo.shn
; Please remember to update these hash values whenever you have patched or updated a file. Failure to do so will result in a failed check.
; Ensure to adhere to the specified order outlined in the section "[IntegrityCheckFile]". This ensures that the file and its corresponding hash align with each other.
[IntegrityCheckHash]
Hash=BF4863931D313D93C7D75DB046CF8DD3
Hash=6538C804723B5BE52F49ED9C06EB7D09
; Example files you can have deleted. This list can be updated as well, while following the same format.
[DeleteFiles]
File=ressystem/IteminfoServer.shn
File=ressystem/MobInfoServer.shn
Ensure to maintain the identical folder structure as your client when creating your patch archive.
Suppose you intend to patch the ItemInfo.shn
file, for instance. In that case, you must ensure that your patch1.rar (Example) file appears as follows: ressystem/ItemInfo.shn
.
Also, if you don't know how to enable RAR4 compression, here is a quick tutorial.