[BDS-1013] Cannot Use wsserver Command (connect) Created: 21/Jun/19  Updated: 04/Jan/24  Resolved: 04/Jan/24

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.17.11 Hotfix, 1.8.1.2, 1.14.32.1
Fix Version/s: None

Type: Bug
Reporter: Joshua Greenlaw Assignee: Unassigned
Resolution: Works As Intended Votes: 35
Labels: feature-check
Environment:

Windows Server 2016 Datacenter Edition, Windows 10, Ubuntu


Attachments: Zip Archive BDS-1013-Evidence.zip     PNG File BDS1206Actual.png     PNG File BDS1206Expected.png    
Issue Links:
Duplicate
is duplicated by BDS-1206 /connect and /wsserver (Websockets) a... Resolved
is duplicated by BDS-14806 /connect (wsserver) command does not ... Resolved
Confirmation Status: Confirmed
ADO: 324331

 Description   

I've created a simple websocket server in order capture more in game events than console output would allow (mainly so that I can create two-way chat in Discord).

The test I set up works flawlessly in single player but fails entirely from a BDS console. There's no output. Enter an incorrect address or port in single player results in a "Could not connect to server" message, but the BDS console is empty.

Edit: Per many people's suggestion, I also tried initiating the connection from a game client as an op. This resulted in a "command not found" type of error.



 Comments   
Comment by Jiulio [ 04/Feb/22 ]

Hello, I just wanted to confirm that the issue is still there, even in the latest bds software in mc 1.18.2.03.

I would also like to point out that this is not a simple extra feature, it is very important especially for servers (like it's mad that it works fine in sigle-player where it is useless... and not in servers where it is vital if you wanna bring your server to something more than a world to play in with a few friends).

Comment by jpg [ 07/Mar/21 ]

Just to add, one effect of this bug is that "Code Connection for Minecraft" can't be used on a Bedrock Dedicated Server (because it relies on the /connect command).

Comment by Dreamedc2015 [ 24/Feb/21 ]

This would be amazing to have
i was working on my own chat logging system
and now cant finish it

Comment by IonicEcko [ 11/Apr/20 ]

Expand Bedrock Dedicated Server (BDS) Configuration/Customization Options is probably the best worded one,.

Comment by Justin D [ 10/Apr/20 ]

There's a feedback post over at https:// feedback.minecraft.net for more administrative options that I would suggest going and giving an upvote if management and functionality expansion are things you would like to see in BDS! (and I'm totally in that boat  )

Is there a specific link you can post for that?

 

 

Comment by IonicEcko [ 10/Apr/20 ]

Volunteers man the bug tracker so we know as much as you do unfortunately.

Its been raised but its also important to remember that the functionality has never been available and was only logged because the console commands (at one point) indicated it was available but was subsequently removed. So its very possible this could get closed as a feature request. Not that it will, just best to keep expectations in check

There's a feedback post over at https:// feedback.minecraft.net for more administrative options that I would suggest going and giving an upvote if management and functionality expansion are things you would like to see in BDS! (and I'm totally in that boat )

Ionic

Comment by Justin D [ 10/Apr/20 ]

Just wanted to chime in here: do we know when this will be slotted to be fixed (in terms of release versions)? If you cannot comment on a specific release, it'd be great to know if this is intended to be picked up soon in the future.

In terms of impact for any prioritization: this makes it impossible to add any server-side interactions, outside of behavior packs, that integrate with outside systems. I was also looking at using this to make chat commands for my dedicated server (and also hook it up to Discord to sync chat to encourage playing on the server when people start joining). Having this command working will help immensely to letting the community start building integrations with the Bedrock Edition, and hopefully will help migrate people from the Java Edition.

(Hope you all are staying safe with COVID-19 going around!)

Comment by IonicEcko [ 06/Mar/20 ]

Importing comments from BDS-1206:

BPS:
What I expected to happen was...:
The connection will be established, which BDS will notify us of, and the WebSocket server will receive messages from the game chat.
[singleplayer as example, /connect 127.0.0.1]

What actually happened was...:
No reaction to command input from the server side.

Steps to Reproduce:

  1. Run any WebSocket-server software;
  2. Run BDS;
  3. Insert command connect [uri] or wsserver [uri].

DigitalClark:
BPS Thanks for the example pictures!
When executing the "help" command in BDS v1.14.32.1, it now seems that there are only 3 help-pages instead of 18 (like back in v1.12). The connect or wsserver command isn't even listed anymore, but executing one of them doesn't result in an error like
"Unknown command: example. Please check that the command exists and that you have permission to use it."
that pops up when trying to run any non-existing arbitrary command.

Comment by Joshua Greenlaw [ 05/Mar/20 ]

Both issues are describing the same issue, as far as I can tell.  Both issues were fairly verbose, but I think they contain the same information. One report should be good. 

Comment by IonicEcko [ 05/Mar/20 ]

Thank you very much NibbleNinja.

One last question if I may, do you believe that this and BDS-1206 are describing the same issue?

I believe they do (they both just seem to be regarding the lack of websocket support) but just want a second set of eyes more verse in the websocket stuff because I've never looked at it so am out of my depth

And following on from that is there anything there not covered in this one that, if moved over to here, covers the missing functionality and can be put forward as one report?

Ionic

Comment by Joshua Greenlaw [ 04/Mar/20 ]

Thanks for your response! I've uploaded a zip file with several things.

  • SinglePlayer-ConnectCommand.png shows me using the connect command in single player
  • SinglePlayer-ConnectSuccess.png is the success message, plus me sending a chat message
  • SinglePlayer-WebsocketOutput.png shows the websocket listener I have receiving the message
  • BDS-ConnectCommand.png is me trying to use the same command from a BDS instance in game
  • BDS-ConnectFailure.png is the failure message that I received
  • BDS-Console-ConnectFailure.png shows me trying to use the commands directly from the BDS console
    • Yellow highlight is the command as used previously, with a valid listener address
    • Blue highlight shows the command used with no arguments
  • Finally, the MC_WSS folder contains a barebones Node.js application which I used for a websocket listener

My expectation is that on a BDS instance, I should be able to use the connect command to connect to the same websocket listener as in single player. Please let me know if you have additional questions. 

Comment by IonicEcko [ 04/Mar/20 ]

Hi Josh,

Is this still an issue in 1.14.32.1?

Are you able to provide steps to reproduce your issue including what you're expecting should happen?

Ionic

Comment by Joshua Greenlaw [ 06/Aug/19 ]

Because it might help, code is here: https://pastebin.com/SpJPj6s1

It uses Node.js and MS SQL Server Express, all secrets have been scrubbed. Again, it works in single player, but not in BDS or Realms.

Comment by Ruben Adema [ 04/Aug/19 ]

Can you send me the scripts you used to create the WebSocket server, I have tried many different scripts but I haven't managed to get it working yet

Generated at Sat Jan 11 07:16:13 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.