• Joined on 2023-12-03
Exynox pushed to master at metin2/deploy 2024-11-17 11:20:19 +02:00
9a705f42e2 First working version of deployment environment'
b371a5317f Added remove flag to docker run command
35b2b1c57e Updated README.md with a quick start guide
708b65be30 Restructured sample .env file, switched database to biarms/mysql
0a497f5a69 Added database initialization mechanism, support for in-game mall
Compare 9 commits »
Exynox created pull request metin2/deploy#3 2024-11-17 11:20:08 +02:00
First working version of deployment environment
Exynox pushed to nightly at metin2/deploy 2024-11-17 11:19:28 +02:00
b371a5317f Added remove flag to docker run command
Exynox pushed to nightly at metin2/deploy 2024-11-17 10:52:36 +02:00
35b2b1c57e Updated README.md with a quick start guide
708b65be30 Restructured sample .env file, switched database to biarms/mysql
Compare 2 commits »
Exynox pushed tag 0.3.2 to metin2/server 2024-11-17 09:23:22 +02:00
Exynox pushed to master at metin2/server 2024-11-17 09:22:47 +02:00
a2f20a0395 Merge pull request 'Fix communication error between cores' (#36) from nightly into master
db4542dd7a Fixed mishandling of public/private IP addresses
0f259307df Updates from master
Compare 3 commits »
Exynox merged pull request metin2/server#36 2024-11-17 09:22:45 +02:00
Fix communication error between cores
Exynox created pull request metin2/server#36 2024-11-17 09:22:26 +02:00
Fix communication error between cores
Exynox commented on issue metin2/server#27 2024-11-17 09:20:51 +02:00
Players do not get disconnected when already logged in

Duplicate of #32, fixed.

Exynox closed issue metin2/server#27 2024-11-17 09:20:51 +02:00
Players do not get disconnected when already logged in
Exynox commented on issue metin2/server#32 2024-11-17 09:20:33 +02:00
Possible communication error between game cores

This was confirmed and fixed in db4542dd7a35381768521c6aabb57c1014a84b29.

The cause was that the game core reported its public IP instead of its private IP to the db core, which in turn was…

Exynox closed issue metin2/server#32 2024-11-17 09:20:33 +02:00
Possible communication error between game cores
Exynox pushed to nightly at metin2/server 2024-11-17 09:18:10 +02:00
db4542dd7a Fixed mishandling of public/private IP addresses
Exynox pushed to nightly at metin2/server 2024-11-17 09:14:11 +02:00
0f259307df Updates from master
db0a0fef64 Disabled SSL enforcement in libmariadb
671c514cb6 Merge updates from the nightly branch
Compare 3 commits »
Exynox merged pull request metin2/server#35 2024-11-17 09:14:09 +02:00
Updates from master
Exynox created pull request metin2/server#35 2024-11-17 09:13:49 +02:00
Updates from master
Exynox commented on issue metin2/server#27 2024-11-17 06:24:58 +02:00
Players do not get disconnected when already logged in

The bug seems to happen if the account is connected with a player in map c1 (ID 41). For example, if account is in map c3 (ID 43), the logout message is received and the player is disconnected.

Exynox commented on issue metin2/server#27 2024-11-16 21:59:33 +02:00
Players do not get disconnected when already logged in

This only seems to happen in the Docker deploy environment. Might be due to the fact that there are multiple game cores running at the same time. Might also be related to #32.

Exynox pushed to master at metin2/server 2024-11-16 21:15:04 +02:00
db0a0fef64 Disabled SSL enforcement in libmariadb
Exynox pushed tag 0.3.1 to metin2/server 2024-11-16 21:15:04 +02:00