mojira.dev

Derrick Walton

Assigned

No issues.

Reported

BDS-17019 Bedrock server/client crash - Fishing rod and nether portal. Duplicate BDS-15574 Unable to change default Member level after initial map creation. Duplicate

Comments

this appears to have been resolved in 1.19.2

 

This appears to be resolved in 1.19.2

This issue is still relevant on the most recent update. 1.18.31

Try upgrading to the 1.16.201.3 (about 7 days old now)

 

Edit:  I saw a similar error to this one, it could be related to where the player spawns in. Something in particular villages causes a crash when players enter them.

Also confirmed this behavior with windows based server. Identical steps.

I have confirmed this bug.

 

Steps to recreate.

  1. Create world and set world to default to visitors.

  2. Save and exit world.

  3. Copy world directory from win10 app local to linux host and configure server to run off of new world.

  4. configure default user perm to be 'member'

  5. ensure permissions are correct for user starting minecraft.

  6. empty permissions.json

  7. start server

  8. connect with client

  9. user is now a visitor.

https://www.youtube.com/watch?v=AW5X7-qnvLk

Check the provided HTML file with the bedrock server, it has a list of the save commands.

 

  • save hold

  • save query

  • save resume

I will do a little testing and attempt to confirm. That is good to know.

So I think this disabled by default. I would probably just leave them in the same subnet, there are a number of ways you can work around this (DNS spoofing for example). Just set one of the default 'featured' servers to your internal ip for example at your local resolver.  Unless you are trying to give external access to your minecraft server, I'm not sure what segregation on your internal network would actually do for you. (Maybe monitoring and reporting?) Either way, at this point in time the auto-discovery doesn't appear to work cross subnet with xbox and switch.

 

Source: I run a bedrock server.

This is interesting, I am running a home server on UB20 and have done some minimal tuning with systemd to gain huge performance boosts out of my server. Here is what I have done:

  • set Limitcore/limitas/limitrss to infinity

  • set nofile limit to 10K

  • set nproc limit to 10K (neither file handles or thread count come close to these limits)

  • set bedrock max threads to 0

  • set process niceness to -10

I also noticed a mild hit when wrapping the  running instance in screen, so I just connect the bin to a tty and use systemd to launch and configure the service. I can drop my service file if interested.

 

With the setup I experience almost no mob lag, but do experience a little block lag when there is a large amount of mining in the nether, or a large amount of chunk generation within the overworld. Minecarts seems to function fine, but I need to experiment more to decide if they are slow.

My box is running an i7-10700k w/hyper-threading enabled (8-core, 16-thread)

 

 Edit: I agree with the assessment that the way threading is implemented it is problematic with linux hosts.

 

Also: I'm running the 5.4.0-65-generic kernel.  and using the SLUB allocator (default I believe)

Note: I am not a developer or associated with Mojang. But can you provide a copy of your config? I'm not able to replicate this, my config line looks as follows.

 

default-player-permission-level=member

Note there are no spaces or quotes. I wonder if the server is defaulting to the visitor value because of an error in your config.