No summary provided.
s&box libraries list
Browse public s&box libraries by recent updates, favorites, votes, momentum, and Terry Score.
No summary provided.
test available clothes
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~
No summary provided.
A library to import libraries into your project/other libraries
LichessNET API Wrapper which features a board integration API.
Time series metrics collector for s&box
No summary provided.
Dockable picker with sorting by query distance and popularity. Hold modifier keys to copy [Icon("...")]
A MoveMode to make players look and feel handcuffed!
No summary provided.
Provides a way to represent optional values that may or may not exist clearly.
No summary provided.
Runs the inbuilt s&box MCP server on Linux under Proton.
No summary provided.
A simple extension of the rect editor that allows you to export grayscale templates of rect files for use in external programs
A Core Library to manage data
Allows drag and drop of sboxshare assets into the engine to automatically download them. Also allows for easy zipping of assets
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.