chipmunkmc wrote:

Also if you know how to make my scratch-paint properly link with my scratch-gui (and perhaps other scratch-editor package forks), and have all of that link w/ scratch-www, without causing weird NPM issues, please let me know!
Sorry I'm basically asking for free work here, I'm just sort of stuck on that…

I'll see what I can do after I'm done decompiling the 2.0 online editor (even if we decide to implement 3.0 compatibility on the server and not the frontend or something, we still have to change the colors to match the rest of the website and fix hard-coded urls in the embed player, and binary patching is kinda hacky)

Also, I noticed that the WWW is currently broken. That's my fault, I moved the urls that correspond to hosts on the real Scratch website to a new /hosts path:

In bin/set-env.sh, this:

becomes the following:


Also, when Codeberg gets back up, I'll add support for the 2.0 media libraries, which require their assets to be in APIClone's assets directory. As such, to make it work, you should copy every asset from the Scratch 2.0 Offline Editor's /media directory to /files/assets.

chipmunkmc wrote:

Also if you know how to make my scratch-paint properly link with my scratch-gui (and perhaps other scratch-editor package forks), and have all of that link w/ scratch-www, without causing weird NPM issues, please let me know!

I managed to link scratch-paint and scratch-editor's scratch-gui using npm install –save ../../../scratch-paint, but when I open the paint editor, it just crashes

Well you see, I've been neglecting to re-compile scratch-www until I get the forks working properly. I mean I could just revert it to vanilla scratch-gui but that's not ideal…