Private Patch Server

This is a guide on how to setup your private patch server for Granado Espada. This may not work for SEA server, which uses Steam to update files.

💣 WARNING! This guide is provided as is. Tamper with the game client at your own risks!



PART I: PREPARE CUSTOM PATCH FILES
First you need to prepare the custom patch files. The following is the basic method without requiring any 3rd-party tools. Alternatively, you can use GE Tools to directly create IPF from folder (function 2), replacing Steps 1-3. 

1. Place all your customized files in the appropriate folders according to the folder structure of the associated .ipf file. Do not include unmodified files.
• For example, char_texture.ipf has 3 folders—monster, npc, and pc folders. Make sure the files are located in the proper folders.
• If you need to know the folder structure, you can extract the original .ipf file to find out by reversing Steps 2-3. Alternatively, use IPF Extractor or GE Tools. Do not include the base folder (e.g. char_texture folder).
2. Select all the folders (e.g. monster, npc, and pc) and create a .zip file with password (see below).
• If you cannot copy the password below, it is also found in bin\ipfpassword.txt in GE Tools.
3. Rename the file extension from .zip to .ipf.
4. Repeat Steps 1-3 for other .ipf files to be patched (if any).
5. Create a new folder named ge and move all your customized .ipf files inside.
6. [Optional] Create a new folder named release and move any related files inside. This is needed only if you are going to patch files inside Granado Espada\release folder.
7. Create a .zip file containing ge folder (and release folder, if desired) named [patch_number].zip.
• Patch numbers should be unique. For example, the first patch file might be named 1.zip. 
• Note: This .zip file should not have password.

The IPF password is:

%f %f %s %s ÿÿÿÿ?[ ÿÿÿÿ?%f %f %s h %s .?.   Xÿ$$

PART II: PREPARE THE SERVER
You need a server with direct URL access (e.g. http://myserver.com/ge/patch/). All patch-related files must be located in the same folder. Direct URL means most file hosts (e.g. Google Drive, OneDrive, MEGA, MediaFire) are currently not usable. You can try using Firebase 🔗 instead. Alternatively, you can also use HTTP File Server 🔗 (simple freeware) to host the files yourself.

1. Download and extract privatepatchserver_v1.7z from MEGA 🔗 (Tools folder).
• It should contain a client folder and a patch folder.
• Patch folder should contain 6 files—prepare_revision_v2.txt, revisions_v2.txt, updaterevisionsv2.bat, notice.html, gelogo.png, and mypatch_hfs.jpg.
2. Move all the .zip files created in Part I (see above) into patch folder. 
3. Run updaterevisionsv2.bat in patch folder to update revisions_v2.txt.
4. [Optional] Edit notice.html in patch folder to customize your patcher web page.
5. Upload all files in patch folder to your server.
• For HTTP File Server, drag and drop the patch folder onto Virtual File System (left) panel, then click Real Folder button. You must decide if you want it to be accessible remotely by everyone or only in your local network.
• For local network only, your URL is http://localhost/patch or http://127.0.0.1/patch. You can also use the internal IP displayed in HTTP File Server (e.g. http://192.168.0.105/patch in the sample screenshot). 
• For remote access, click Menu ➢ IP Address ➢ Find External Address. If you are behind a router, remember to forward the respective port (default 80) for remote access. Consider using a Dynamic DNS service (e.g. http://freeddns.noip.com 🔗) if you don't want to deal with external dynamic IP.

If you wish to host your own emblems (see Patch Party Emblems), you can put the emblem images in another folder (e.g. emblem folder), then drag and drop the folder onto HTTP File Server as mentioned above.

PART III: PREPARE THE CLIENT
If you are using a private patch server hosted by someone else, you can skip Part I and Part II.

1. Download and extract privatepatchserver_v1.7z from MEGA 🔗 (Tools folder), if you skipped Part II earlier.
• It should contain a client folder and a patch folder.
• Client folder should contain 5 files—mypatch.exe, mypatch.config.xml, mypatch.revision.txt, mypatch_client.jpg, and readme_privatepatch.txt.
2. Open mypatch.config.xml in client folder with Notepad.
3. Find the line that says Key="Revisions" (usually line 4) and change its value to your server URL.
• The default value is http://localhost/patch/ which is meant for local network only.
4. Find the line that says Key="Notice" (usually line 5) and change its value to your notice page URL.
• The default value is http://localhost/patch/notice.html which is meant for local network only.
5. [Optional] Find the line that says Key="Home" (usually line 6) and change its value to your home page URL.
6. Save and exit Notepad.
7. Copy all files in client folder into your Granado Espada folder (e.g. C:\Program Files (x86)\Granado Espada).
8. Run mypatch.exe in Granado Espada folder to start patching. 
• Obviously, your server must be online.

The files in client folder (e.g. mypatch.exe) are modified to use different file names from the default patcher (ge.exe). If you prefer to use the default patcher instead, make backup copies of updater.revision.txt and updater.config.xml files. Modify updater.config.xml instead of mypatch.config.xml as stated in Steps 2-6 above. Run ge.exe to start patching. To revert to official patch server, restore the 2 backup files.