s&box libraries list
Browse public s&box libraries by recent updates, favorites, votes, momentum, and Terry Score.
Let AI build in your editor. MCP server with 76 tools for scenes, assets, code and more.
Create custom reusable particle systems and control their parameters from the editor or code!
Connects Claude AI to your s&box editor in real-time. Describe what you want and it creates. Game Dev is open for all!
S&box Codebase Fucker Upper
Tells your IDE about blacklisted code.
The missing layer between s&box's raw networking API and your gameplay code. Every common networking task in one line.
Quick way to add VSCodium as a supported code editor
HaxeBox lets you write code in Haxe that integrates seamlessly with s&box.
A lightweight code library that provides a basic Contract/Mission system for games and addons.
allows the editor to open Linux Code-OSS through proton
A set of classes and components to juice up procedural animations! Try the demo scene!
Command palette for searching assets, scene objects, code, evaluating math, and converting colors.
i will keep my code dry i will keep my code dry i will keep my code dry i will keep my code dry i will keep my code dry i will~
s&box libraries are reusable packages made for creators rather than players. A library might provide editor tools, UI helpers, effects, character controllers, gameplay systems, shaders, or other code and assets that can be used inside another project.
Libraries are not part of the s&box Play Fund. They are still useful to track because they can shape what gets made. A good library can save time, make a common feature easier to build, or let several projects share the same underlying system.
This s&box libraries list tracks public library packages by favorites, upvotes, downvotes, Terry Score, and recent momentum. Terry Score is a confidence-weighted approval score based on upvotes, downvotes, and vote count. The numbers are only public signals. They do not prove that a library is maintained, documented, compatible with every project, or right for a specific use case.
For libraries, the package title and summary matter more than raw popularity. A small library can be useful if it solves one narrow problem well. A larger library can be useful if it becomes part of how several creators build games, maps, or tools.