Dedicated Server - Disable Code Builder?
I don't know if this is a bug per se, but it appears that I'm unable to disable the Code Builder on a dedicated server. I have the server.properties line "allow-commands" set to "false". The exact line is
allow-commands=false
From the in-game settings I've also double checked that commands and cheats are both set to disabled, yet students can still perform code builder activities when set to Member.
I haven't performed a ton of testing yet, but certainly Agent commands all work (my students are all complaining that the kids that can code have an advantage since they are having agents mine for them - I'm proud, but want to see if I can disable it for everyone).
The Code Builder option from the in-game settings menu is greyed out, with it toggled on. Just wondering if I can disable it somehow.
-
Hey there!
Let me ask the team on this one and get back to you!
0 -
I'm facing the exact same problem.
What happened with this issue?I want to prevent MakeCode from being used on the server.
Simply disabling chat isn’t enough.
Using MakeCode’s “Forever” block allows users to spawn large numbers of blocks, destroy them, change game modes, alter the time, and perform various other actions.
Please implement controls to restrict MakeCode usage as soon as possible.
0 -
Hey there,
Sorry to hear you are running into some issues with this as well. Let me check if there is any updates on this for you!
0 -
Hey there all,
Just wanted to let you know the devs are actively looking into this!
0 -
Hey there!
The team is still reviewing this, but in the mean time we have a small workaround.
Users can be set to
memberinstead ofoperatorwhich may, if done in addition toallow-commands=false, restrict the majority of MakeCode functionality. Try reducing their students' permissions fromoperatortomember. It won't solve the problem fully but might help. The player will still be able to open codebuilder, and can run actions that do not need console commands to run like moving the agent forward. Thanks for the understanding and patience with this!0 -
Thanks for the update!
Yep, having students set to member with the allow-commands=false set does restrict some of the coding.
I think it would work well if there was a way to just disable the agent entirely - that would prevent them from using it as their own personal ender chest that no one else can destroy, as well as stopping the agent from going around destroying/building/collecting in an otherwise code/cheat-free world.
0 -
Thank you for your reply.
As you mentioned, I have configured the server.properties file as follows:
default-player-permission-level=member
allow-commands=falseHowever, the agent is still able to act.
For example, if I give the agent 64 diamond blocks and a player collects them, it easily disrupts the balance of a healthy survival mode.To ensure everyone can enjoy the server more fairly, it would be best to configure the settings so that MakeCode cannot be opened.
0 -
Hey there,
Thanks all for the patience and understanding with this. We will absolutely forward this feedback to the team as we work on future solutions.
0
Please sign in to leave a comment.
Comments
8 comments