Handle top down view camera with player controller.
s&box libraries list
s&box libraries list.
Browse public s&box libraries by recent updates, favorites, votes, momentum, and Terry Score.
- libraries
- 355
- favorites
- 1.3k
- upvotes
- 1.5k
A set of post-process shaders which simulate various realistic lens and image effects.
An easy-to-use crosshair builder inspired by your favorite competitive FPS.
Tool for procedural terrain generation
Library for quickly building interior room layouts, corridors, doors, windows.
Citizens motivate you every 15-30 minutes
Easily create damage numbers or other floating text
Let AI build in your editor. MCP server with 154 tools for scenes, assets, code and more.
Split mesh files (.fbx, .obj and .dmx) into their submeshes/children/parts and combine them in a prefab file.
A tool for importing UE5 meshes, maps, and materials
Adds persistent custom asset-browser locations with filters, you can jump to curated asset sets fast.
A simple system to create dialogue with a custom editor!
An s&box implementation of CAMI.
Tells your IDE about blacklisted code.
Simple addon that adds Discord Rich Presence to your s&box Editor. Restart the Editor after installation
s&box libraries list
What are s&box libraries?
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.
Reading the library list
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.