scratch-gui
scratch-gui copied to clipboard
TurboWarp
TurboWarp not connecting to cloud_host URL parameter
Expected Behavior
Opening a project with cloud variables enabled and the cloud_host parameter set should connect to that cloud variable server and start syncing cloud variables.
I'm testing older projects of mine that use Cloud Variables.
I'm also testing my Python-based reimplementation of the Cloud Variable protocol (source).
My Cloud variable host is wss://cl4-test.meower.org/, which autodetects the protocol whenever the handshake method is made.
Actual Behavior
TurboWarp doesn't attempt to connect to the cloud variable host.
My cloud variable host is working, as it connects and syncs fine using Sheeptester's mod. I open the project editor and use the "Set test to #" block and it synchronizes the variable state just fine.
However, when I test the same project using TurboWarp, it never connects to the server.
Steps to Reproduce
Using this test project,
- Load TurboWarp with cloud_host url parameter set to
wss://cl4-test.meower.org/ - File > Load from your computer > test.sb3
- Check inspect console, no attempted connections to
wss://cl4-test.meower.org/ - Toggle "Enable/Disable Cloud Variables"
- Move the Test cloud variable slider - Still no response
Operating System and Browser
Windows 10.0.19044, Google Chrome 107.0.5304.106
Note
This is more of a suggestion, but I think TurboWarp should allow editing projects with Cloud Variables enabled if it detects a custom cloud variable host.
Here's what I'm considering:
- Projects from files will be able to use cloud variables (project ID generated by project title)
- You will be able to use cloud variables in any project in the editor, but you will be put into a different "room" from people who haven't opened the editor
Would that work for you?
Here's what I'm considering:
- Projects from files will be able to use cloud variables (project ID generated by project title)
- You will be able to use cloud variables in any project in the editor, but you will be put into a different "room" from people who haven't opened the editor
Would that work for you?
That sounds fine. I think it would actually be beneficial to separate users who have/haven't opened the editor.
Sorry for delay on this.
Please test the experiment: https://experiments.turbowarp.org/cloud-variables-anywhere/