Closed leolion3 closed 6 months ago
Server logs will not help here. Please post your friends charxml instead or a charxml that had the issue.
As a safeguard, please ensure your client has ugc requests turned off as per the readme.
Disabling ugc services worked. Since its a new change it hadnt been incorporated for my clients.
Does that close the issue or are you planning on troubleshooting further?
that closes the issue. duplicate of #1277.
Also not being able to login after getting kicked to login is a duplicate issue of #154
you can solve the needing to reboot the client when getting kicked to login by renaming the folder with legouniverse.exe in it to client
. This is a requirement and how the game was shipped in live.
Make sure you've done the following:
[X] I have checked that this issue has not already been reported.
[X] I have validated that this issue is not a syntax error of either MySQL or SQLite.
[X] I have pulled the latest version of the main branch of DarkflameServer and have confirmed that the issue exists there.
DarkflameServer Version
e729c7f
Issue Description
Im hosting a DLU multiplayer community server for a couple people, one of them reported the issue to me. I've joined them and operated the server logs to reproduce the issue.
After finishing all Nimbus Station missions, the client attempts to change the world (doenst really matter which rocket launchpad they use). When they attempt to do so, they are kicked out of the server. To other players it seems as if the character is holding his rocket before disappearing due to the disconnection.
Heres a server log from the event:
(*) While the log is a bit older, the issue still persists in DLU 2.2.0
Reproduction Steps
To reproduce, finish all Nimbus Station quests, then attempt to leave the area using the Nimbus Station rocket and any launchpad (perhaps that rocket is buggy).
Expected Behavior
The client should just get moved to another world, as is true for all other players on the server.
Environment
Server is running in an Oracle VM. The infrastructure and databases are set up correctly and all services are reachable. Players are able to play regularly, except for one player who finished all missions.
The server is running as a daemon with some automated scripts (link) - these have no effect on performance though.