TrussC addon registry. Lists community and official addons installable via trusscli addon clone.
No pull request needed — addons are discovered automatically by GitHub topic. Just:
- Add the
trussc-addontopic to your repository (GitHub repo → About → topics). - Make the repo public (and not archived).
- Add an
addon.jsonat the repo root.{}is enough to be picked up, but metadata makes it discoverable:{ "description": "Short description of what your addon does", "version": "1.0.0", "author": "Your Name", "license": "MIT", "trussc_version": ">=0.4.0", "screenshot": "screenshot.png", "keywords": ["physics", "2d"] }- No
namefield — the addon name is the repository name (e.g.tcxMyAddon). version: self-reported. Git tags (e.g.v1.0.0) are stored separately aslatest_tag.screenshot: relative path in your repo, or an absolute URL.keywords: helptrusscli addon searchfind your addon.
- No
A daily GitHub Actions crawl finds every public repo with the trussc-addon topic and a readable addon.json, then regenerates the registry. Your addon appears within a day. Topics are not inherited by forks, so a fork only shows up if its owner adds the topic too.
mainbranch —addons_list.json, auto-generated by the crawl from topic search. Do not hand-edit.gh-pagesbranch —registry.json, auto-generated with versions and metadata from each addon'saddon.json, published via GitHub Pages.
trusscli fetches registry.json from GitHub Pages to discover addons (a precomputed file avoids per-user GitHub API rate limits).
trusscli addon search physics # Search available addons
trusscli addon list --remote # List all addons (local + remote)
trusscli addon clone tcxMyAddon # Clone an addon into your TrussC installation
trusscli addon add tcxMyAddon # Add it to your project
trusscli addon pull tcxMyAddon # Update an addon to the latest version
trusscli addon pull --all # Update all cloned addons