Block a user
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
First working version of deployment environment
35b2b1c57e
Updated README.md with a quick start guide
708b65be30
Restructured sample .env file, switched database to biarms/mysql
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
Fix communication error between cores
Fix communication error between cores
Players do not get disconnected when already logged in
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…
Possible communication error between game cores
0f259307df
Updates from master
db0a0fef64
Disabled SSL enforcement in libmariadb
671c514cb6
Merge updates from the
nightly
branch
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.
…
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.