Newbie Spellweaver
- Joined
- Feb 23, 2022
- Messages
- 77
- Reaction score
- 79
This is the TalesRunner Server Emulator 2026, based on the 2021 server source that I shared previously.
I have been working on updating the server to make it compatible with TalesRunner R186632. There are still many bugs and incomplete functions that need to be fixed, but at this point I have fixed enough of the server for the game to run and for many of the main functions to work.
I'm sharing the current source in the hope that someone else might be interested in helping debug, fix, improve, and share their changes with the community.
ProtocolDebug=true
Then run the game, test the function you want to debug, and check the generated logs for Overpop, Remain, or other protocol errors.
You can use TRLogDecrypt to inspect the logs:
This method is mainly useful for functions that already exist in the server but are broken or incompatible with the newer client. If the function does not exist in the server at all, it will need to be implemented first instead of only fixing the protocol.
This is still a work in progress, so contributions, fixes, testing, and shared improvements are welcome.
You can download it here:
Install MariaDB normally and make sure the database service is running.
After installing Navicat:
make db.sql
This script will create the required databases for the server, including:
Run multiple queries in each execution
This is important because leaving this option enabled may cause problems when importing the database scripts.
After both the Game Database and Log Database have been restored successfully, the database setup is complete.
I normally use the Visual C++ Redistributable All-in-One package from TechPowerUp:
Install the required runtimes and restart Windows if necessary.
I have been working on updating the server to make it compatible with TalesRunner R186632. There are still many bugs and incomplete functions that need to be fixed, but at this point I have fixed enough of the server for the game to run and for many of the main functions to work.
I'm sharing the current source in the hope that someone else might be interested in helping debug, fix, improve, and share their changes with the community.
How to Debug
Enable protocol debugging in settings.ini:ProtocolDebug=true
Then run the game, test the function you want to debug, and check the generated logs for Overpop, Remain, or other protocol errors.
You can use TRLogDecrypt to inspect the logs:
To view the content, you need to sign in or register
This method is mainly useful for functions that already exist in the server but are broken or incompatible with the newer client. If the function does not exist in the server at all, it will need to be implemented first instead of only fixing the protocol.
Functions Currently Fixed / Working
Some examples of functions that have already been fixed or partially fixed include:- Login
- Password authentication
- Character selection
- In-game nickname
- Shop
- MyRoom
- Costume apply
- Status reset
- Latest Thai items and boxes
- Item Collection
- Shu
- Farm
- Park
- Create room
- Single Player
- And more
This is still a work in progress, so contributions, fixes, testing, and shared improvements are welcome.
To view the content, you need to sign in or register
TalesRunner Server Emulator 2026 - Installation Tutorial
Before running the server, you need to prepare the database and install the required runtime components.1. Install MariaDB
For the database server, I am using MariaDB 10.4.28.You can download it here:
To view the content, you need to sign in or register
Install MariaDB normally and make sure the database service is running.
2. Install Navicat
For easier database management, I recommend using Navicat.After installing Navicat:
- Create a new MariaDB/MySQL connection.
- Connect to your local MariaDB server.
- Make sure the connection works before continuing.
3. Create the Databases
Before restoring the server databases, run:make db.sql
This script will create the required databases for the server, including:
- Game Database
- Log Database
4. Important Navicat Restore Setting
When restoring or executing the SQL files in Navicat, make sure to untick:Run multiple queries in each execution
This is important because leaving this option enabled may cause problems when importing the database scripts.
After both the Game Database and Log Database have been restored successfully, the database setup is complete.
5. Install Visual C++ Redistributable
Before running the server, you may also need to install the required Microsoft Visual C++ Redistributable runtimes.I normally use the Visual C++ Redistributable All-in-One package from TechPowerUp:
To view the content, you need to sign in or register
Install the required runtimes and restart Windows if necessary.
6. Ready to Run
At this point, you should have:- MariaDB installed and running
- Navicat connected to MariaDB
- Game Database created and restored
- Log Database created and restored
- Required Visual C++ Redistributable runtimes installed

