FIRST and foremost, the following assumes that you have:
- Installed Microsoft SQL Server 2014 (FULL) Evaluation [180 days] with the following settings
- Default (NOT NAMED!) instance [VERY IMPORTANT]
- Mixed Authentication Mode
- TCP/IP Enabled (In SQL Configuration Manager under protocols) enabled
- Caution: It is advised to not only firewall lock 1433 but if you MUST have external use to use a custom port and change it often couple with strict permission based database accounts.
- Downloaded and extracted the
(Thanks Team Revolution
) - Downloaded and extracted the 9.1 Client for your region
- Installed

Warnings:
- If you do not meet the above requirements this guide does not apply to you, you should stop right now!
- To make the server public:
- Open the following ports in your Windows Firewall + any router based fire-wall that may be applicable! [Ports: 58422, 32214, 15574]
- Change 'S:io.ip_address:127.0.0.1' setting in gameserver.opt to your external ip [you can find
]
Moving on...
For the sake of this guide we're gonna use a specific folder setup, failure to follow the below guide will result in 'NO SUPPORT FOR YOU' keep that in mind.
Step One
- Create a new folder on your Desktop called: server_bin
- Create folder called: Auth_Bin
- Create a folder inside [Auth_Bin] called upload
- Download the
(Thanks Glandu2
)
- Open the Auth Emulator package
- Example:
- Extract RappelzAuthServer.exe to the folder you created [Auth_Bin]
- Create a new file in notepad++ and paste the following code into it, edit as needed and save as auth.opt in the 'Auth_Bin' folder
Code:- Create a new file in notepad++ and paste the following code into it, edit as needed and save as common.opt in the 'Auth_Bin' folder
Code:- Open the 9.1 package
- Example:
- Open GameEngine, extract all contents [Except for Auth_Bin] to the previously created [server_bin] folder
- Download
(for gameserver.opt) and extract it's contents to the [server_bin]/[game_bin] folder
- Bring 9.1 package back to front
- Back out of GameEngine and enter dbs folder
- Extract arcadia ONLY (Billing/Telecaster are not needed) to the root of your Local Disk (e.g. C:\)
- Download my
(place it also in the root of your Local Disk)
- Download my
(place it also in the root of your Local Disk)
- Minimize the 9.1 Package for now
Step Two
- Open SSMS and right click 'Databases' then click 'Restore Database'
- Example:
- In the prompt the pops up, select the 'From Device' radio button and press the browse [...] button
- Example:
- Press add and navigate to the root of your Local Disk [where you previously extract the contents of the dbs folder]
- Example:
- Restore Arcadia/Auth/Telecaster in this manner
- UPDATE: Download the
- UPDATE: Download the
(Thanks LadySeraph for heads up!)
- Extract the .sql's to your Local Disk root and then double click them to open them in SSMS
- Make sure they are targeting the Telecaster table
- Execute and Billing is fixed
- Collapse 'Databases' tree and double click 'Security' tree to expand it
- Create a new file in notepad++ and copy the following template into it:
- Template:
- Visit my favorite
- Generate a unique key for each field of the file you just create (this will be a reference for you later)
- Save this list wherever you will not lose it. Name it what you like, as long as you will remember
- I cannot say at this time but the Game Server may reject mixed-case passwords. If you keep getting 'Login for '<login-name>' failed' you may want to try an ALL LOWER variation of your passwords
- Right click 'Logins' and click 'New Login'
- Example:
- Click the 'SQL Server Authentication' radio button
- Uncheck 'Enforce Password Expiration'
- Example:
- Using this form create the three logins from the file you created recently.
Step Three
- With the 'Security > Logins' branch still expanded, right click the user you have created for Auth and double-click it
- Click the 'Mappings' label to the left of the window
- Example:
- In the 'Users mapped to this Login:' section, check the 'auth' table
- In the 'Database Role Membership:' section, check appropriate roles:
- Auth Roles: db_reader/db_writer
- Arcadia Roles: db_reader
- Telecaster Roles: db_reader/db_writer
- Do this for each name (we have already done auth, now do arcadia and telecaster using the above Roles)
- Collapse the 'Security' branch and expand your Auth table (double-click)
- Expand the 'Security' branch of your Auth Database
- Expand the 'Schema' branch
- Example:
- Double click the 'db_reader' / 'db_writer' role (one by one) according to the accounts roles to open the Schema Settings
- Click the 'Permissions' label to the left side of the window
- Beside 'Users or Roles' click 'Search' button
- In search prompt click 'Browse'
- Check the name of your Auth account who you mapped previously
- Example:
- Press 'Ok' on the search prompt
- Back inside the 'Permissions' section of the schema settings make sure your previously searched user is highlighted
- In the 'Permissions for <name>' section check the appropriate permissions for the role and database being done
- Auth db_reader permissions: Select
- Auth db_writer permissions: Insert
- Arcadia db_reader permissions: Select
- Telecaster db_reader permissions: Select
- Telecaster db_writer permissions: Insert/Update/Delete
- Set the permissions for Arcadia, Telecaster in the same manner using the above permissions.
- Collapse the branches back down so that you can see all three databases [auth, telecaster, arcadia]
- For Auth/Telecaster ONLY Right click and click 'Properties'
- For Auth/Telecaster ONLY Click the 'Permissions' label to the left of the window
- Example:
- Make sure that the access name for your table is listed in the 'Users or Roles:' section and make sure to click it to select it (if its not selected)
- Scroll down and check 'Execute' and save/exit the window
Step Four
- We are done with SSMS so you can close/minimize it for now.
- Navigate to the [server_bin]/[game_bin] folder and open the gameserver.opt
- Immediately replace it's entire contents with the following code:
- Code:
- IMPORTANT! Setting S:game.local_flag:4 must be set to your proper locale refer to the spoiler below
- locale_codes:
- All instances of local_flag in the arcadia database will need to be set to your locale code or 0 to show in-game when launched in your specific local. For instance, ASCII/US will need S:game.local_flag:4 and any NPC/FieldProp/Dungeon I wanted to be available to me would need to have a local_flag of 0 or 4
- Where in most cases local_flag 4 OR 0 is applicable it seems in NPCResource it must be 0 not 4 [CONFIRMED]
- Edit the gameserver.opt as you needed and save, now compress it by dragging it ontop of the Rappelz Compressor which should be in the same folder
- For database details refer to the file you created earlier with the login information
- Example:
If you have followed the above guide correctly you should now have a fully working server for you and/or your friends, so just enter the Auth_Bin folder and launcher the RappelzAuthServer executable. Back out of the Auth_Bin folder and enter the Game_bin folder and launch CaptainHerlockServer.exe.
You DO NOT have to type 'start_service' or 'set game.open_external'
The rest is pretty simple:
Final Steps
I wish you the best on getting your server setup and I'm going to be honest -- I may not have the time to answer any and every question that comes through this thread, so don't be offended if I miss your question. I hope other dev's in the community will help to answer your questions, this is just a tool to aid them!
- Bring the 9.1 Package back into focus and enter the 'Launcher' folder
- Extract 'RappelzCmdLauncher.exe' into your 9.1 clients root folder
- Create a new file in notepad++ and copy the following code into it:
- Replace it's contents with the following:
- Code:
- Save the file as 'Start.Bat' with File Type: 'All' into your 9.1 client directory
- Open/Bring SSMS back into focus
- Double click your Auth table to expand it
- Visit
- Create the password for your Admin Account
- Example:
- The MD5 hash [result of md5_key+plain-text-password] goes in the 'password' field of the dbo.Accounts table in the Auth Database
- Create the account entry in dbo.Accounts and login!
If you have any suggestions to this guide feel free to post them (within reason)
GOOD LUCK!






