Crackle is a modding SDK for Snap!. The SDK is managed by @Tethrarxitet and @codingisfun2831t.
If you would like to contribute/collaborate, please add to your message:
## Collaboration request: <GitHub username/link>
This is where development for Crackle will be logged and recommendations will be crowdsourced.
Move requested by @codingisfun2831t
Real quick - maybe edit the post to include the GitHub repo (GitHub - CrackleTeam/CrackleSDK: CrackleSDK - a modding SDK for Snap! @ snap.berkeley.edu)? Also add the Crackle logo (after you’ve updated the colors).
Ngl I don’t think this thread needs to exist.
I’m guessing you mean having the previous thread archived and this one being made? I think the separation is important since basically all of the previous thread was me trying to get a repo to push my copy to. Also, the previous was using tethrarxitet’s account, and this one uses the “crackleteam” account (the one we plan to have updates for Crackle). What exactly makes you think this thread shouldn’t exist?
Either way, bh was fine with archiving it, so I think it should be fine.
@crackleteam doesn’t have permission to send links yet. 
Oh.
I think I’m going to do some updates to Crackle. Some more events, more APIs maybe.
My original intention for the CrackleMods is, like Windhawk Mods, to have each mod be a single file in a “mods” directory, where the mod browser parses each of those files to get the information. For the changelog, it’ll read the commits for that mod and get each of the “extra” descriptions. I don’t exactly like the folder method, as it’ll require you to write two copies of the mod manifest - one in manifest.json and in the mod itself (the return object). This single file method also is better since when mods are loaded, it can just read from the mod data for info. Of course I could provide a way to add a logo, banner, or seperate README.md for the mod (“extra” folder with “[mod-id]_logo.png”, “[mod-id]_readme.MD”, etc). Of course that’ll be for later.
I think you’re kinda doing too much for such a early version of Crackle. Make it exist first, and THEN make it good.
gitman-cyber (Git ‘em) · GitHub Here’s my GitHub I’d like to help or submit a application
Usually most mods use folders with this file structure. I was just following suit 
src/
- main.js
- moreSourceFilesHere.js
changelog.md
icon.png
mod.json
readme.md
Also, I kinda wanted a readme for what the mod actually does, and a changelog for, you know, what changed.
May I help?
We can put a comment at the start of the file and that’ll be the readme.
Simple: Read the commit history of the mod file to get each change and compile that into a changelog. If needed, we could make a override folder for that.
Eh, I mean we could do that “use seperate folder for each “extra” mod file” idea I described:
I think we should just start with getting the mods repo to work, then (again) make it better eventually.
Little update - I have combined all of the files into one index.js, it just works better. I have also rebased the Git history (squash commits into one, rename commits) so we can use Conventional Commits from now on. I also did a couple other changes in mod loading, REQUIRING ID, but also auto-generating name from ID (e.g. example-mod = Example Mod). Hopefully this project can get a little more, stuff added to it now? This topic has been dry for a while.
Another update: I have added a new API to modify built in menus. Currently I have the project cloud and settings menu, the script menu, the palette menu, the snap logo menu. Can this topic please get back on people’s minds? Not trying to be needy here! Also, I havent seen @tethrarxitet in a while, and owlsss hasen’t responded: