s&box libraries list
Browse public s&box libraries by recent updates, favorites, votes, momentum, and Terry Score.
A component library to try enhance the particle system a bit
No summary provided.
Split mesh files (.fbx, .obj and .dmx) into their submeshes/children/parts and combine them in a prefab file.
No summary provided.
Objective marker that stays on the edge of the screen, plus an optional arrow
Provides a git version control interface within the s&box editor.
Let AI build in your editor. MCP server with 154 tools for scenes, assets, code and more.
Simple MCP server for AI tools
The missing layer between s&box's raw networking API and your gameplay code. Every common networking task in one line.
A clone of the stock one with massive extended features
Simple S&box editor tool that drops selected GameObject(s) straight down onto the first surface below them.
Simple camera system similar to Unity's Cinemachine.
No summary provided.
WIP, on big development
A raycast system that lets the player interact with tagged objects, with cooldown control and enter/exit/interact events.
Utilities and extensions used by Wacky Wizards
Uses noise to generate a forest using prefabs (trees, shrubs, grass etc.)
Quick way to add VSCodium as a supported code editor
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.