Configuration with Minecraft Bedrock - LAN visibility to true

Technical Support
,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Phobos’ v2.6.2.0 (Mainline)
Virtualization QEMU_KVM
Application Minecraft Bedrock
Module GenericModule
Running in Container No
Current State Ready

Problem Description

Issue

I keep changing enable-lan-visibility=false to true in server.properties.
When I start the server, it automatically changes it back to false.
I need this automatic change to stop.

Reproduction Steps

  • Change file
  • Save server.properties file.
  • Start server
2

AMP disables that because otherwise the server ignores the port set in server.properties and tries to listen on port 19132, causing potential port conflicts, firewall issues and confusion

3

Can I change configuration to ensure this does not change? As reason I bought licences was for this precise reason, and if this doesn’t work, then the licences I bought are pointless.

4

You could use the “Minecraft Java Edition” option when creating an instance (it also supports Bedrock despite the name) which doesn’t wield control over this setting, or if you don’t mind manually editing JSON files you could remove that setting reference so it isn’t overwritten.

But can I check why you want this setting? Players on your LAN will still be able to connect even without it.

5

Legacy bedrock won’t work. It’s download sources are way out of date

6

I could potentially enable it in the settings with a BIG warning

7

So although I am running a hosted server bedrock, I need a PS5 and Switch to connect to it via the LAN.
I am using Phantom to bring the server into the LAN, which works all good.
It’d be fine if it wasn’t consoles connecting, but always fun!

I’m happy with whatever solution allows it to work, and not have to keep changing anytime I make a change or update etc,

8

What does it actually control? Isn’t this just the discovery so it appears automatically in the list without needing to connect directly? Edit: Ah I see it’s needed for the consoles. So yeah it was disabled because it breaks things, but we’ll see what we can do.

9

If the LAN is set false, Phantom is unable to do anything with it. I on my PC use the server connect as normal, but PS5 without the plus membership, has to be LAN only.

10

@Greelan Perhaps name the setting “Console Compatibility” so people don’t turn it on who don’t need it and a warning that it locks the server to the default port and could cause conflicts?

1 Like
11

I can see the support requests already - why is my port not listening, why won’t the server start? - but sure xD

12

From an end-user point of view, this is clear and solves the problem I think.
I’m only planning on running the 1 server myself for this exact purpose, so the effect it will have on the others doesn’t matter to me.

I am happy if its a case that I can change something just for me, and it doesn’t effect everyone else and cause you guys an issue? haha

13

Any changes you make will get overridden when you next update the instance

14

If the change is easy enough, I guess it doesn’t matter too much. Depends what it required really.
I just don’t want to cause issues for you later on haha.

15

Stop the instance. Go into its datastore. Edit metaconfig.json. Change false to true there

16

Thanks all for your help, I haven’t abandoned this thread haha.
I’m just having problems with the PS5 actually connecting now. Sees the world on the LAN but doesnt get any further. I think I had this problem because, but can’t for the life of me remember what I did to solve it. But pretty sure it’s not your system now haha.
Thanks!