Search results

If anyone else comes across this and wants to experiment himself, feel free to use the repo from which I run my container.

@EmptyBasket Another couple of turbulent months, but I finally got to get back to this. And I got it to actually work as per your suggestion of that PR! I can now connect using ClassicUO + ClassicAssist to a ServUO server running in a Docker container on a Synology NAS. As a UO vet of 20+ years...

Sorry for the late reply, but many thanks for pointing me to that PR and putting in the effort of writing a summary! I'll only be able to actually do something with it in a few weeks' time, but I'm excited to try it out and make it work. I will report back when I got to work on it.

Sort of; I ran it on a DigitalOcean droplet just fine, but I use those for work which is less than ideal. It's somewhat encouraging that I'm not the only one that faced a similar problem, but if it's a technical thing between containers and the way ServUO accepts connections I may have to give...

First of all, thanks for your reply @Max! Answers inline; no solution yet but with your checklist of suggestions I can continue to tinker. If I get it fixed, I'll comment in this thread again. Hmm, connecting with the ECLauncher tool I can play and trigger world saves that persist just fine...

I configured a Docker container that successfully compiles and runs a fresh install of the latest ServUO (publish 57 at the time of writing this) on my Synology NAS. It reads the necessary game files from a folder within ServUO, and I can connect to it fine using the EC Launcher tool. However...