basicly the situation thats going on in scratch

Instructions

for people who dont know: The "Question Mark Glitch" (or Question Mark Bug) in Scratch is a widely documented server-side asset corruption issue where sprite costumes and backdrops fail to load and are permanently overwritten by a placeholder image of a black question mark inside a gray or white box. While it first made major waves during a massive server outage, community reports on platforms like the Scratch Subreddit indicate it continues to spike intermittently due to server-side asset rendering and loader strain. Technical Root Cause: Asset Server Timeouts: When the Scratch editor loads a project, it fetches vector (.svg) and raster (.png/.jpg) files from Scratch's dedicated asset servers. If the server fails to deliver the file in time due to heavy load, a network timeout, or processing errors, the editor fallbacks on a default placeholder: the question mark box. SVG Loader / Rendering Strains: The bug frequently triggers during server-side maintenance, such as when the Scratch Team attempts to bulk-reprocess or re-save vector assets. This spikes server load and results in intermittent download failures for complex projects .Asset Overload: Massive projects featuring a high volume of costumes (e.g., thousands of assets or large file sizes) have a significantly higher risk of triggering the bug due to the sheer number of simultaneous asset requests hitting the server. The "Perma-Damage" Mechanism The real danger of this bug is not the loading failure itself, but how Scratch handles auto-saving: The project opens, and the server fails to fetch a costume. Scratch substitutes the missing image data with the question mark graphic in the editor's RAM. If the user makes a change or if Auto-Save triggers, the project writes this temporary placeholder data directly into the project's permanent file structure (.sb3).The original asset data is permanently wiped out on the user's project file, meaning the project remains ruined even after server connection stabilizes. Common Community Workarounds Because it is an engine-level and server-side bug, users have developed strict protocol rules to protect their work: Immediate Page Refresh: If a user opens a project and spots a question mark box, they are advised to never save the project and immediately refresh the browser tab or close it. Utilizing TurboWarp: Many advanced creators copy their project IDs over to TurboWarp, a third-party Scratch mod compiler. TurboWarp handles asset fetching aggressively by retrying broken links repeatedly until they safely load, avoiding the placeholder fallback entirely. Local Backups: The absolute best safeguard is for creators to regularly download local copies of their projects (File > Save to your computer). If the asset server corrupts the cloud version, they can simply re-upload the uncorrupted .sb3 file.