s&box libraries list
Browse public s&box libraries by recent updates, favorites, votes, momentum, and Terry Score.
Simple S&box editor tool that drops selected GameObject(s) straight down onto the first surface below them.
An AI chatbot integrated directly into the S&box editor. Chat with a local AI assistant trained on S&box
https://github.com/KivinDev/InstancedGoodPerformingTerrainScatterer
Create and animate a crosshair easely with this tool.
Basic library for streaming grid-based worlds
Easy creation of a splash screen for the game
Raycast-wheel vehicle physics for s&box: slip-curve tires, full drivetrain, assists and a chase camera. No art required.
Drag-and-drop UI editor for S&Box
No summary provided.
copy position and/or rotation from one gameobject to another
shrimple postprocessing shader
A 2D tilemapping toolkit with brushes, collision, layers and chunking.
Async RPC Callback for s&box – Call server methods with await, [RpcCallback] handles the round-trip automatically.
test available clothes
Quickly convert EXR, PNG, etc to RAW supported by terrain import
Aims to mimic the behavior of WorldPanels, while being unaffected by Post Processing effects.
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.