s&box libraries list
Browse public s&box libraries by recent updates, favorites, votes, momentum, and Terry Score.
Simple dockable notepad widget for s&box. Allows creating, saving and editing notes in the editor.
Dockable inspector search that scans the current selection
A set of classes and components to juice up procedural animations! Try the demo scene!
Simple S&box editor tool that lets you quickly select all child objects from the current hierarchy selection.
No summary provided.
copy position and/or rotation from one gameobject to another
Auto re-connects your testing client instance when you create a lobby
One-click restart for the s&box editor. The editor will automatically relaunch your project.
Restores project settings to it's own window, that can have items dragged and dropped onto it.
MongoRest transforms MongoDB into a generic RESTful API for simplified CRUD operations
Adds an attribute that allows you to embed game resources in components.
A editor tool that adds a [TypeSelector] attribute, enabling easy selection of inherited types in the inspector.
Command palette for searching assets, scene objects, code, evaluating math, and converting colors.
No summary provided.
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.