s&box libraries list
Browse public s&box libraries by recent updates, favorites, votes, momentum, and Terry Score.
A simple way to interact with gameobjects
Editor Tool for importing bsp. Creates appropriate GameObjects with their components. Makes use of the mapping MeshComponent.
Simply add the "Simple Text Chat System" component to a GameObject with a "Screen Panel" component and customize.
Split mesh files (.fbx, .obj and .dmx) into their submeshes/children/parts and combine them in a prefab file.
Objective marker that stays on the edge of the screen, plus an optional arrow
Simple S&box editor tool that drops selected GameObject(s) straight down onto the first surface below them.
A raycast system that lets the player interact with tagged objects, with cooldown control and enter/exit/interact events.
A component that allows the player to raycast, grab, hold, smoothly move, and rotate tagged physics objects
Pickup, Throw, and Drop props or GameObjects. Inspired by Half-Life 2, Garry's Mod, etc.
A lightweight code library that provides a basic Contract/Mission system for games and addons.
Simple S&box editor tool that lets you quickly select all child objects from the current hierarchy selection.
copy position and/or rotation from one gameobject to another
Command palette for searching assets, scene objects, code, evaluating math, and converting colors.
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.