OpenDBO

1. Download / Install the necessary files:

   • DirectX9.
     • In case of encountering error S1023, execute the following commands as administrator:

       MsiExec.exe /passive /X{F0C3E5D1-1ADE-321E-8167-68EF0DE699A5}
       MsiExec.exe /passive /X{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
       

   • 3rd party tools that you downloaded from our 3rd party repository.
   • Client files: Download them from the Assets repository. First get the Base Client from the Releases section and then replace all needed files with the updated ones on the repo itself.
   • Download v142 build tools (C++ MFC) via Visual Studio Installer.

2. Extract Xtreme Toolkitpro and GFx SDK 3.3 somehwere

3. Set up environment variables:

   • Open the Control Panel, go into System and Security, and click on System
   • In the search bar, type in "System Environment Variables" and open "Edit the system environment variables"
   • In the System Properties window that opened, click "Environment Variables..."
   • In the "System Variables" section, click on "New..."
     • In "Variable name:", write "GFXSDK_DIR"
     • Click "Browse Directory..." and locate where you extracted the GFx SDK 3.3 folder.
     • Do the same for Xtreme Toolkitpro except in "Variable name:" write "XtremeToolkitPro_Dir"

4. Access the GFx SDK 3.3 folder you just moved:

   • Navigate to GFx SDK 3.3\3rdParty\jpeg-6b\gfx_projects\Win32
   • Rename the folder named "Msvc80" to "Msvc142."

5. Enter the Msvc142 folder and open the project: "libjpeg.sln"

6. Ensure the solution configuration in VS 2019 is set to: "Release and Win32." If not, adjust it.

7. Configure the libjpeg project settings:

   • Right-click on libjpeg, go to Properties, and under Windows SDK Version, set it to the latest (10.0).
   • Change both Output Directory and Intermediate Directory's Msvc80 to Msvc142.
   • Change the Platform Toolset to (v142).
   • Right-click on libjpeg -> Build.

8. Navigate to folder: source\repos\OpenDBO-Core\DboClient\DragonBall and extract the client's contents.

   • The downloaded RAR file should contain a folder named DragonBall; copy and paste its contents into the specified path.
   • This RAR file is from the "Client" link provided above.

9. Go to folder: source\repos\OpenDBO-Core\DboClient and open "DboClient.sln"

10. In Solution Explorer, go to DBO\Client.vcxproj and repeat step 7.

11. Unload all Tool projects:

    • In Solution Explorer, expand the Tool solution folder.
    • Right-click each tool project (2DParticleEditor, DTEditor, GUIEditor, GuiDevTool, ModelTool2, NaviTool, NtlWE, PackEditor, SkillCustomizeViewer, TSEvtMaker, TSTool, Venus, WorldEditor, WorldPatchProcess) and select Unload project.
    • These tools are not required for building the Client and may cause compilation errors if left loaded.

12. Right-click on Client.vcxproj -> Build

    • You should encounter only one error after compiling: 'libjpeg.lib'

13. Right-click on Client.vcxproj then go to properties:

    • Navigate to Linker -> General -> Additional Library Directories.
    • Update the paths to match your system:
      • $(GFXSDK_DIR)\Lib\$(PlatformName)\Msvc80\Release
      • $(GFXSDK_DIR)\3rdParty\jpeg-6b\lib\$(PlatformName)\Msvc142\Release

14. Compile RenderWare x64 libraries:

    • Open DboClient\RenderwareX64\Include\rwcore.vcxproj in Visual Studio 2019.
    • Build each RenderWare plugin project in DboClient\RenderwareX64\Include\ with Release|x64 configuration.
    • The compiled .lib files will output to DboClient\RenderwareX64\Lib\Release_x64\.
    • This step is required before building the Client for x64.

15. Right-click on Client.vcxproj -> Rebuild

16. The Client should have compiled successfully.

1. Requirements:

   • Windows 10
   • 8 GB of RAM

2. Download and install Visual Studio 2019:

   • Visual Studio 2019
   • Select the "Community - Free Download" option to obtain the installer app.
   • Open the installer app and follow these steps:
     • Navigate to the "Workloads" section and install both "Desktop development with C++" and "Game development with C++."
     • In the "Individual components" section, install "C++ Clang-cl for v142 build tools (x64/x86)."
   • Click "Install while downloading" and wait for the process to complete.

3. Download and extract the OpenDBO-Core Repository:

   • OpenDBO-Core Repository. Click "Code" -> Download ZIP.
   • Extract the ZIP file to the main folder named "OpenDBO-Core."

4. Download and install/extract additional programs: it's recommended to set up the Client repository now. Otherwise perform steps 1 and 2 from the Client guide (if you already did it you can skip this step)

5. Compile the private server using Visual Studio 2019:

   • Navigate to the "OpenDBO-Core" main folder, then to the "Dboserver" subfolder.
   • Double-click "Dboserver.sln" to open it in Visual Studio 2019.
   • Ensure "Release" and "x64" are selected from the top bar.
   • In the "Solution Explorer," under "Server," right-click each server (AuthServer, CharServer, etc.) and click "Build" one by one.
   • Wait for the server executable files to finish compiling.

6. Download and install XAMPP (you can also install the latest version of MariaDB directly, if so, you can skip this step and some steps of 7.):

   • Deactivate User Account Control (UAC) by searching for "msconfig" in Windows, accessing the "tools" tab, and selecting "Disable UAC."
   • Download and install XAMPP from XAMPP
   • Navigate to "C:/xampp/apache/conf/httpd.conf" in Explorer.
   • Open "httpd.conf" in Notepad, change the port to "Listen 8080," and change "ServerName localhost:" to "ServerName localhost:8080."
   • In the XAMPP Control Panel, start "Apache" and "MySQL."
   • Ensure your antivirus accepts XAMPP.

7. Open your browser and type: "localhost:8080/phpmyadmin/"

   • Click "New" in the left column.
   • Add a database named "dbo_acc" and click "make."
   • Click "import" at the top, choose file, and select "dbo_acc.sql" from "OpenDBO-Core/DboServer/Database."
   • Click "Start" at the bottom.
   • Repeat this for "dbo_char" and "dbo_log."
   • Within "dbo_acc," find "accounts," click "insert," and fill in a username and password.
   • Generate a SHA3-256 Hash for the password using SHA3-256 Hash Generator, paste it next to "Password_hash," and click "Start" at the bottom.
   • If you want GM permissions make sure to set admin and isgm to 10 in the accounts table and gamemaster to 10 in the characters tabel from the dbo_char database.

8. Change the server .ini files:

   • Navigate to "OpenDBO-Core/DboServer/ExecutionEnv/Config."
   • Open "AuthServer.ini," "CharServer.ini," etc., with Notepad.
   • Ensure all IP addresses are "127.0.0.1" and change the password to "test."

9. Run the server executables:

   • Go to "OpenDBO-Core/DboServer/ExecutionEnv."
   • Run start_master_server.bat
   • Run start_query_server.bat and wait until its done (if you get missing MSVCP120.dll error you can fix it by installing Microsoft Visual C++ Redistributable 2013).
   • Run start_char_server_0.bat
   • Run start_auth_server.bat
   • Run start_channel_0.bat and wait until it's finished (can take a lot of time, might need to press ENTER). Then close it.
   • Run start_chat_server.bat and wait until its done.
   • Run start_channel_0.bat again, start_channel_1.bat (if you need 2 channels) and start_channel_9.bat

10. Download and extract the DBO Client Files:

    • Development Client/Server Access
    • In the main folder, locate "ConfigOptions.xml," change the IP to "127.0.0.1" on each line, and save.
    • Run the client, enter your username and password, and you’re ready to go.

DBOLauncher (DboClient/Tool/DBOLauncher) is the game's launcher: it optionally checks a patch server for updates, then starts Client.exe. It's part of DboClient.sln (Release4Tools|Win32).

1. Build it: open DboClient.sln, right-click DBOLauncher under the Tool solution folder, and build it with the Release4Tools|Win32 configuration. The post-build step copies LauncherConfig.xml, launcherdevmaster.xml, patchw32.dll, and the patch/ folder from Tool/DBOLauncher/Test/ into DragonBall/.

2. Offline mode (default): Test/launcherdevmaster.xml ships with OFFLINE_MODE_ENABLE set to 1, so the launcher skips the online patch-server flow entirely and goes straight to its idle screen, where clicking Start launches Client.exe directly. No server setup needed — this is the quickest way to just launch the client.

3. Online mode (testing the real patch flow): set OFFLINE_MODE_ENABLE to 0 in Test/launcherdevmaster.xml and rebuild to exercise the real patch-server flow instead. This needs a reachable HTTP patch server (port 80 — hardcoded in the launcher, it can't use another port) — the files it needs to serve are Test/LauncherConfig.xml (points at the server) and Test/patch/ (PatchServerConfig.XML + PatchList.xml, which ship declaring "nothing to patch" so the launcher reports the client as up to date and proceeds straight to the idle screen). How you host those is up to your own setup.