Hi!
I run a Python cloud server (scratchattach 2.2.3, Python 3.12) for my projects (IDs 1333999788 and 1235793796). The server listens to both clouds:

Scratch: session.connect_cloud(id).requests() → works, requests arrive live.

TurboWarp: sa.get_tw_cloud(id, purpose=…, contact=…).requests() → connects fine, but never receives anything.

Diagnostics already done:
A raw WebSocket listener on wss: //clouddata.turbowarp.org/ (valid User-Agent with contact info, correct handshake) receives the stored value of ☁ TO_HOST on join, but never any new set when I click in the project on https://turbowarp.org/<id>. So the web player itself never sends updates.

Adding “ ?username=–SupraCode– ” to the URL changes nothing.
The exact same server code worked a few months ago, and still works on scratch.mit.edu today.
Other servers (e.g. RedOS10 by KROKOBIL) receive TurboWarp cloud requests normally, so the TurboWarp cloud server itself is fine — it seems specific to my browser/setup.
What could prevent the TurboWarp web player from sending cloud variable updates? A setting, a username requirement, a browser block? Any idea welcome, I've been stuck for days.
Thanks!

I'll move this over to the Advanced Topics section for you - that's a better fit for this kind of topic

--SupraCode-- wrote:

Hi!
I run a Python cloud server (scratchattach 2.2.3, Python 3.12) for my projects (IDs 1333999788 and 1235793796). The server listens to both clouds:

Scratch: session.connect_cloud(id).requests() → works, requests arrive live.

TurboWarp: sa.get_tw_cloud(id, purpose=…, contact=…).requests() → connects fine, but never receives anything.

Diagnostics already done:
A raw WebSocket listener on wss: //clouddata.turbowarp.org/ (valid User-Agent with contact info, correct handshake) receives the stored value of ☁ TO_HOST on join, but never any new set when I click in the project on https://turbowarp.org/<id>. So the web player itself never sends updates.

Adding “ ?username=–SupraCode– ” to the URL changes nothing.
The exact same server code worked a few months ago, and still works on scratch.mit.edu today.
Other servers (e.g. RedOS10 by KROKOBIL) receive TurboWarp cloud requests normally, so the TurboWarp cloud server itself is fine — it seems specific to my browser/setup.
What could prevent the TurboWarp web player from sending cloud variable updates? A setting, a username requirement, a browser block? Any idea welcome, I've been stuck for days.
Thanks!

I don't quite understand the issue necessarily other than getting the cloud variable works fine but trying to update its value doesn't.. What are you trying to put into the variable and also can you send a small portion of your terminal logs and I might be able to help you out.

Thanks for offering to help!

I actually just solved the issue a few hours ago.

The problem: I had added a custom User-Agent patch to the websocket connection for TurboWarp, thinking it was required. This caused scratchattach's internal reconnection logic to fail silently, creating a loop where the connection would establish but then immediately drop.

The solution: Remove the User-Agent patch entirely. scratchattach already handles the TurboWarp User-Agent correctly internally - no custom patch needed.