Jump to content

I beg Klei not to make those slave world bugs anymore.


gznc
  • Fixed

Every time you guys update the game, our slave worlds must encounter disaster due to error like NOT_IN_DB, aws 433, etc.

Can you guys test before the update? This is a base function in the game!

And I want to say my region was in China before this update, now in Sing.

5bb7d323c74f0_QQ20181006050110.thumb.png.bdc54e03b16e70026500375e833497b5.png


Steps to Reproduce
Just start a pure game.



User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.

I find it interesting that run slave worlds first then this error would not appear.

Edited by gznc

Share this comment


Link to comment
Share on other sites

I think this problem may be fixed...

But it's stupid right now because slave worlds will restart itself when it connected to the master.

Hey, Klei devs!

Although worlds start without NOT_IN_DB, now players cannot go into caves(slave worlds)!!!

It just likes the first update recently!

Edited by gznc

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...