Source Tales of Pirate 2026 x64 DX9 by alexxst.st

1780602880222.webpBro these files need way more work than updating your vb

1. You can't use the original mhontana files because the game now uses a different protocol, msgpack. The network part has been heavily refactored and tested.

2. You need to install .NET support in the studio, as indicated in the solution explorer.
1. You can't use the original mhontana files because the game now uses a different protocol, msgpack. The network part has been heavily refactored and tested.

2. You need to install .NET support in the studio, as indicated in the solution explorer.
1780602694561.webp1780602822926.webp
I connected and created an account\gate\group and launched it. Using C++, I compiled an .exe file that was missing from the server folder containing the .cfg files.
1780602946402.webp

I also created the same account for the databases, with the same password, and I hope there were no errors or edits. I allowed access to the folder with the game files for the entire Windows. I tried everything. I changed the following in C++:
from ->

"DRIVER={ODBC Driver 17 for SQL Server};SERVER=localhost;DATABASE=gamedb;Trusted_Connection=Yes;"

to ->
"DRIVER={ODBC Driver 17 for SQL Server};SERVER=localhost;DATABASE=AccountServer;Trusted_Connection=Yes;"

I tried to launch it in different ways. I did everything I could from memory and with the assistant. But unfortunately, I couldn't get anything to launch.

This is my first time running the program with this size and problems. Versions 1.3/2.0 and the main version of mothannakh ran differently and without this error.
Please help me figure out where I made a mistake? How can I fix this? And what additional information do I need to provide for verification?

I tried running it in different ways without changing the values in C++.
After fixing it, to avoid breaking anything, I uploaded clean files, created a new executable in C++, and then kept getting the same error.
 
The service connects using the standard ODBC connection string, without any password encryption features that are not required here.
You need to enable Windows user authentication on the MSSQL server.
Next, since you have SQLEXPRESS instead of the normal version, you need to change the line

DRIVER={ODBC Driver 17 for SQL Server};SERVER=localhost\SQLEXPRESS;DATABASE=gamedb;Trusted_Connection=Yes;

1780603122264.webp