a multiplayer game of parenting and civilization building
You are not logged in.
Pages: 1
For anyone else who has this problem, the issue was that my server code was ahead of my client code. The official servers hadn't pushed version 180 to my client yet.
By copying the contents of my server's OneLifeData7/ folder into the directory containing the .exe for steam, I was able to connect to my custom server without issue. Always check to make sure you have the same dataVersionNumber.txt on both client/server
Oh and this is a hacky way of doing it, if I was patient I would have just been able to connect to the official servers and get the update eventually.
I am building the server myself using the pullAndBuildTestSystem.sh script. I have completely uninstalled both the client and server, reinstalled the latest, still seeing the same issue. When you say latest version I assumed I want the master branch from github. Do I need a special tag such as OneLife_liveServer?
I've been enjoying this game for a couple weeks now but I've had some issues while playing with my buddy on my custom server.
The textures for gooseberry plants get switched out with a goose pond, essentially anything stackable shows the wrong texture. I saw in the sticky thread that some people were having these issues due to database files or cache files. I've tried removing these, and even cloning and building fresh still has this problem.
Heres my setup:
Server: Running an Ubuntu Bionic Beaver VM.
Client: Steam on windows 10
I ran my custom server on the previous release (before thanksgiving) without issue. After the new update I seem to have this texture issue. I'm wondering if there is somehow a mismatch between the master branch on github and what has been released to steam. Any help on this would be appreciated.
The only thing I haven't tried is reinstalling on steam, I will try that now and report back later.
Pages: 1