Quote from: Phantasm on Aug 27, 2026, 11:36 AMData\Local\Eng

And here you create ur Chn folder, so after creating you will have Data\Local\Chn, and translate all the .bmd file from Eng folder to Chinese.

+ you need .reg registry in order to work. Additionally you can leave the Eng folder and translate it to Chinese, much easier.

Good luck.

I directly translated item_eng.bmd and Text.bmd in the Data/local/eng folder, re-encrypted them into bmd files, but the game still displays in English. Is there any missing step? Also, I noticed you mentioned editing the registry earlier. Could you please guide me on how to do that? I'm seeking help, please assist me

Quote from: Phantasm on Aug 27, 2026, 11:36 AMData\Local\Eng

And here you create ur Chn folder, so after creating you will have Data\Local\Chn, and translate all the .bmd file from Eng folder to Chinese.

+ you need .reg registry in order to work. Additionally you can leave the Eng folder and translate it to Chinese, much easier.

Good luck.

Guru, can the file BmdDec.exe encrypt and decrypt all .bmd files under Data/local/eng?

Quote from: Phantasm on Aug 27, 2026, 11:36 AMData\Local\Eng

And here you create ur Chn folder, so after creating you will have Data\Local\Chn, and translate all the .bmd file from Eng folder to Chinese.

+ you need .reg registry in order to work. Additionally you can leave the Eng folder and translate it to Chinese, much easier.

Good luck.

Understood, thank you very much for your guidance

Data\Local\Eng

And here you create ur Chn folder, so after creating you will have Data\Local\Chn, and translate all the .bmd file from Eng folder to Chinese.

+ you need .reg registry in order to work. Additionally you can leave the Eng folder and translate it to Chinese, much easier.

Good luck.

Quote from: Phantasm on Aug 27, 2026, 08:10 AM

Quote from: xiaowcji33 on Aug 27, 2026, 07:45 AMclient login,gamserver print error log:
14:34:36 [RAKLION] [BossEggRegen] : BossEgg[0 ea]
14:34:39 [CastleSiege] CCastleSiege::DataRequest() - REQUEST DATA FIRST
14:38:02 [ObjectManager][3500] AddClient [10.100.30.27]
14:38:03 [ObjectManager][3500] DelClient [10.100.30.27]
14:38:36 Response error after connection causes conclusion [3500][][][10.100.30.27]

Help me, how to solve it

FIX: Client connects to GameServer and disconnects immediately – LTP Season 6

I checked this issue directly in the LTP sources.

If your GameServer shows:

Code Select Expand

14:38:02 [ObjectManager][3500] AddClient [10.100.30.27]
14:38:03 [ObjectManager][3500] DelClient [10.100.30.27]
14:38:36 Response error after connection causes conclusion [3500][][][10.100.30.27]

the important part is:

Code Select Expand

AddClient
DelClient

The client is successfully reaching the GameServer, so this is normally not a basic firewall or GameServer port problem.

The connection is being lost during the initial client/GameServer handshake.

1. Check the correct client settings

Open:

Code Select Expand

Tools\GetMainInfo_New\Release\MainInfo.ini

For the original LTP configuration, use:

Code Select Expand

[MainInfo]

CustomerName = release
IpAddress = YOUR_SERVER_IP
IpAddressPort = 44406

ClientVersion = 1.04.05
ClientSerial = TbYehR2hFUPBKgZj

ClientName = main.exe
UseWrongPacketsCheck = 0

Change only:

Code Select Expand

IpAddress = YOUR_SERVER_IP

For example:

Code Select Expand

IpAddress = 10.100.30.10

if that is the LAN IP of your server PC.

Important:

The ConnectServer port in this configuration is:

Code Select Expand

44406

not 44405, unless you manually changed your ConnectServer configuration.

2. Check GameServer version and serial

In your GameServer configuration, make sure you have:

Code Select Expand

CustomerName = release
ServerVersion = 1.04.05
ServerSerial = TbYehR2hFUPBKgZj
UseWrongPacketsCheck = 0

The following values must match exactly:

Code Select Expand

ClientVersion = ServerVersion

1.04.05 = 1.04.05

and:

Code Select Expand

ClientSerial = ServerSerial

TbYehR2hFUPBKgZj = TbYehR2hFUPBKgZj

The serial is case-sensitive and must be identical character by character.

3. Do not forget to regenerate main.ltp

This source does not simply use MainInfo.ini directly while the client is running.

After editing MainInfo.ini, run:

Code Select Expand

GetMainInfo.exe

It generates:

Code Select Expand

Client\Data\Custom\Configs\main.ltp

Copy the newly generated:

Code Select Expand

main.ltp

to your actual client:

Code Select Expand

YOUR CLIENT\Data\Custom\Configs\main.ltp

Overwrite the old file.

This is very important.

If you change MainInfo.ini but keep an old main.ltp, the client can still use the old IP, version, serial or other configuration.

4. Keep CustomerName as "release" for testing

Use:

Code Select Expand

CustomerName = release

Do not change it to:

Code Select Expand

CustomerName = MyServer

until the client is connecting correctly.

In these sources, CustomerName is also involved in client/server initialization and protection/encryption-related logic.

A mismatch can cause exactly this:

Code Select Expand

AddClient
DelClient

without reaching the normal login stage.

5. Use the correct LTP client Main/DLL

Do not mix these server files with a random Season 6 client.

For example, do not use:

Code Select Expand

LTP GameServer
+
random main.exe
+
DLL from another MuEMU/X-Team/Louis source

Even if the client is also Season 6 Episode 3, the protocol/hooks/encryption can be different.

Use the Main and client DLL that belong to these LTP sources.

The client source is under the LTP client project, similar to:

Code Select Expand

Client\Main_EX603_vs2019

Make sure the correct compiled client DLL is actually loaded by the client.

6. Encryption is enabled

The GameServer source uses:

Code Select Expand

#define ENCRYPT_STATE 1

So the client and GameServer must use compatible packet encryption/protocol handling.

If you use a Main/DLL from another source, GameServer may accept the TCP connection but the first packets cannot be processed correctly.

Result:

Code Select Expand

AddClient
DelClient

after approximately one second.

Do not disable ENCRYPT_STATE as the first fix.

First test the original LTP configuration with the correct client.

7. Understand where the connection fails

The normal connection sequence is approximately:

Code Select Expand

Client connects
|
GameServer AddClient
|
GameServer sends initial connection packet
|
Client processes F1:00
|
Client sends F1:01
|
GameServer checks version/serial
|
Login process continues

In this problem, you normally get:

Code Select Expand

Client connects
|
AddClient
|
FAIL
|
DelClient

The GameServer sends the initial connection packet through:

Code Select Expand

GCConnectClientSend(index,1);

which is associated with:

Code Select Expand

F1:00

The client must process it and continue with:

Code Select Expand

F1:01

If the client cannot decode/process F1:00 correctly, it can close the socket immediately.

8. Check the GameServer log for these errors

If you see something related to:

Code Select Expand

err 2

check:

Code Select Expand

ClientVersion
ServerVersion
main.ltp
client DLL

If you see:

Code Select Expand

err 3

check:

Code Select Expand

ClientSerial
ServerSerial
main.ltp
client DLL

Also check for messages such as:

Code Select Expand

Protocol header error
Protocol size error
Packet unknown error
Packet encryption error
Packet serial error

If you get a protocol/encryption error, the problem is most likely:

Code Select Expand

wrong client DLL
wrong main.exe
wrong main.ltp
wrong protocol
wrong encryption configuration

9. The "Response error after connection causes conclusion" message is not the main problem

This:

Code Select Expand

Response error after connection causes conclusion

is normally a later cleanup/timeout message because the object never completed the login process.

Do not "fix" this by increasing a timeout from something like:

Code Select Expand

30000

to:

Code Select Expand

300000

Your client already disconnects after around one second.

Increasing the timeout only delays the cleanup. It does not fix the handshake.

10. Castle Siege and Raklion messages are unrelated

These lines:

Code Select Expand

[RAKLION] [BossEggRegen] : BossEgg[0 ea]

[CastleSiege] CCastleSiege::DataRequest() - REQUEST DATA FIRST

are not the cause of this connection problem.

The relevant part is:

Code Select Expand

AddClient
DelClient

11. Recommended clean test configuration

Client:

Code Select Expand

CustomerName = release
IpAddress = YOUR_SERVER_IP
IpAddressPort = 44406
ClientVersion = 1.04.05
ClientSerial = TbYehR2hFUPBKgZj
UseWrongPacketsCheck = 0

GameServer:

Code Select Expand

CustomerName = release
ServerVersion = 1.04.05
ServerSerial = TbYehR2hFUPBKgZj
UseWrongPacketsCheck = 0

Then:

Code Select Expand


Save MainInfo.ini
Run GetMainInfo.exe
Get the new:
main.ltp
Copy it to:
Client\Data\Custom\Configs\main.ltp
Use the correct LTP main.exe
Use the correct LTP client DLL
Restart GameServer
Start the client
Select the server
Check the GameServer log

12. If it still shows AddClient -> DelClient

If you still get:

Code Select Expand

AddClient
DelClient

and you do NOT get:

Code Select Expand

err 2

or:

Code Select Expand

err 3

then the client is probably disconnecting before the version/serial validation is even reached.

At that point, concentrate on:

Code Select Expand

main.exe
client DLL
main.ltp
CustomerName
encryption
packet protocol
F1:00 handling
F1:01 handling

Do not waste time debugging SQL, Castle Siege or character database tables at this stage.

Final check

For these LTP sources, start with exactly:

Code Select Expand

CustomerName = release

ClientVersion = 1.04.05
ServerVersion = 1.04.05

ClientSerial = TbYehR2hFUPBKgZj
ServerSerial = TbYehR2hFUPBKgZj

ConnectServer Port = 44406

UseWrongPacketsCheck = 0

Then regenerate:

Code Select Expand

main.ltp

and replace:

Code Select Expand

Client\Data\Custom\Configs\main.ltp

If the values are correct but the client still disconnects immediately, the next thing to verify is the exact main.exe/client DLL and encryption/protocol compatibility.

That is the correct direction for this specific:

Code Select Expand

AddClient -> DelClient


The issue has been resolved, thank you very much. Additionally, I would like to add a client that can be translated into Chinese. How can I translate it? (Which files should be modified?)

The issue has been resolved, thank you very much. Additionally, I would like to add a client that can be translated into Chinese. How can I translate it? (Which files should be modified?)

It has been resolved. Thank you very much

Quote from: xiaowcji33 on Aug 27, 2026, 07:45 AMclient login,gamserver print error log:
14:34:36 [RAKLION] [BossEggRegen] : BossEgg[0 ea]
14:34:39 [CastleSiege] CCastleSiege::DataRequest() - REQUEST DATA FIRST
14:38:02 [ObjectManager][3500] AddClient [10.100.30.27]
14:38:03 [ObjectManager][3500] DelClient [10.100.30.27]
14:38:36 Response error after connection causes conclusion [3500][][][10.100.30.27]

Help me, how to solve it

FIX: Client connects to GameServer and disconnects immediately – LTP Season 6

I checked this issue directly in the LTP sources.

If your GameServer shows:

14:38:02 [ObjectManager][3500] AddClient [10.100.30.27]
14:38:03 [ObjectManager][3500] DelClient [10.100.30.27]
14:38:36 Response error after connection causes conclusion [3500][][][10.100.30.27]

the important part is:

AddClient
DelClient

The client is successfully reaching the GameServer, so this is normally not a basic firewall or GameServer port problem.

The connection is being lost during the initial client/GameServer handshake.

1. Check the correct client settings

Open:

Tools\GetMainInfo_New\Release\MainInfo.ini

For the original LTP configuration, use:

[MainInfo]

CustomerName = release
IpAddress = YOUR_SERVER_IP
IpAddressPort = 44406

ClientVersion = 1.04.05
ClientSerial = TbYehR2hFUPBKgZj

ClientName = main.exe
UseWrongPacketsCheck = 0

Change only:

IpAddress = YOUR_SERVER_IP

For example:

IpAddress = 10.100.30.10

if that is the LAN IP of your server PC.

Important:

The ConnectServer port in this configuration is:

44406

not 44405, unless you manually changed your ConnectServer configuration.

2. Check GameServer version and serial

In your GameServer configuration, make sure you have:

CustomerName = release
ServerVersion = 1.04.05
ServerSerial = TbYehR2hFUPBKgZj
UseWrongPacketsCheck = 0

The following values must match exactly:

ClientVersion = ServerVersion

1.04.05 = 1.04.05

and:

ClientSerial = ServerSerial

TbYehR2hFUPBKgZj = TbYehR2hFUPBKgZj

The serial is case-sensitive and must be identical character by character.

3. Do not forget to regenerate main.ltp

This source does not simply use MainInfo.ini directly while the client is running.

After editing MainInfo.ini, run:

GetMainInfo.exe

It generates:

Client\Data\Custom\Configs\main.ltp

Copy the newly generated:

main.ltp

to your actual client:

YOUR CLIENT\Data\Custom\Configs\main.ltp

Overwrite the old file.

This is very important.

If you change MainInfo.ini but keep an old main.ltp, the client can still use the old IP, version, serial or other configuration.

4. Keep CustomerName as "release" for testing

Use:

CustomerName = release

Do not change it to:

CustomerName = MyServer

until the client is connecting correctly.

In these sources, CustomerName is also involved in client/server initialization and protection/encryption-related logic.

A mismatch can cause exactly this:

AddClient
DelClient

without reaching the normal login stage.

5. Use the correct LTP client Main/DLL

Do not mix these server files with a random Season 6 client.

For example, do not use:

LTP GameServer
+
random main.exe
+
DLL from another MuEMU/X-Team/Louis source

Even if the client is also Season 6 Episode 3, the protocol/hooks/encryption can be different.

Use the Main and client DLL that belong to these LTP sources.

The client source is under the LTP client project, similar to:

Client\Main_EX603_vs2019

Make sure the correct compiled client DLL is actually loaded by the client.

6. Encryption is enabled

The GameServer source uses:

#define ENCRYPT_STATE 1

So the client and GameServer must use compatible packet encryption/protocol handling.

If you use a Main/DLL from another source, GameServer may accept the TCP connection but the first packets cannot be processed correctly.

Result:

AddClient
DelClient

after approximately one second.

Do not disable ENCRYPT_STATE as the first fix.

First test the original LTP configuration with the correct client.

7. Understand where the connection fails

The normal connection sequence is approximately:

Client connects
|
GameServer AddClient
|
GameServer sends initial connection packet
|
Client processes F1:00
|
Client sends F1:01
|
GameServer checks version/serial
|
Login process continues

In this problem, you normally get:

Client connects
|
AddClient
|
FAIL
|
DelClient

The GameServer sends the initial connection packet through:

GCConnectClientSend(index,1);

which is associated with:

F1:00

The client must process it and continue with:

F1:01

If the client cannot decode/process F1:00 correctly, it can close the socket immediately.

8. Check the GameServer log for these errors

If you see something related to:

err 2

check:

ClientVersion
ServerVersion
main.ltp
client DLL

If you see:

err 3

check:

ClientSerial
ServerSerial
main.ltp
client DLL

Also check for messages such as:

Protocol header error
Protocol size error
Packet unknown error
Packet encryption error
Packet serial error

If you get a protocol/encryption error, the problem is most likely:

wrong client DLL
wrong main.exe
wrong main.ltp
wrong protocol
wrong encryption configuration

9. The "Response error after connection causes conclusion" message is not the main problem

This:

Response error after connection causes conclusion

is normally a later cleanup/timeout message because the object never completed the login process.

Do not "fix" this by increasing a timeout from something like:

30000

to:

300000

Your client already disconnects after around one second.

Increasing the timeout only delays the cleanup. It does not fix the handshake.

10. Castle Siege and Raklion messages are unrelated

These lines:

[RAKLION] [BossEggRegen] : BossEgg[0 ea]

[CastleSiege] CCastleSiege::DataRequest() - REQUEST DATA FIRST

are not the cause of this connection problem.

The relevant part is:

AddClient
DelClient

11. Recommended clean test configuration

Client:

CustomerName = release
IpAddress = YOUR_SERVER_IP
IpAddressPort = 44406
ClientVersion = 1.04.05
ClientSerial = TbYehR2hFUPBKgZj
UseWrongPacketsCheck = 0

GameServer:

CustomerName = release
ServerVersion = 1.04.05
ServerSerial = TbYehR2hFUPBKgZj
UseWrongPacketsCheck = 0

Then:


Save MainInfo.ini
Run GetMainInfo.exe
Get the new:
main.ltp
Copy it to:
Client\Data\Custom\Configs\main.ltp
Use the correct LTP main.exe
Use the correct LTP client DLL
Restart GameServer
Start the client
Select the server
Check the GameServer log

12. If it still shows AddClient -> DelClient

If you still get:

AddClient
DelClient

and you do NOT get:

err 2

or:

err 3

then the client is probably disconnecting before the version/serial validation is even reached.

At that point, concentrate on:

main.exe
client DLL
main.ltp
CustomerName
encryption
packet protocol
F1:00 handling
F1:01 handling

Do not waste time debugging SQL, Castle Siege or character database tables at this stage.

Final check

For these LTP sources, start with exactly:

CustomerName = release

ClientVersion = 1.04.05
ServerVersion = 1.04.05

ClientSerial = TbYehR2hFUPBKgZj
ServerSerial = TbYehR2hFUPBKgZj

ConnectServer Port = 44406

UseWrongPacketsCheck = 0

Then regenerate:

main.ltp

and replace:

Client\Data\Custom\Configs\main.ltp

If the values are correct but the client still disconnects immediately, the next thing to verify is the exact main.exe/client DLL and encryption/protocol compatibility.

That is the correct direction for this specific:

AddClient -> DelClient


client login,gamserver print error log:
14:34:36 [RAKLION] [BossEggRegen] : BossEgg[0 ea]
14:34:39 [CastleSiege] CCastleSiege::DataRequest() - REQUEST DATA FIRST
14:38:02 [ObjectManager][3500] AddClient [10.100.30.27]
14:38:03 [ObjectManager][3500] DelClient [10.100.30.27]
14:38:36 Response error after connection causes conclusion [3500][][][10.100.30.27]

Help me, how to solve it

Files based on SSeMU 2.1.9 logs and some Wizardteam features added
+:

-Interface Menu Option
-AutoPotion
-AutoVault
-Interface Event
-Interface Helper(Clicker)
-Interface AutoBuff
-FPS Increased
-Fixed Tooltip
-Fixed Flicker
-Fixed MS