s&box libraries list

s&box libraries list.

Browse public s&box libraries by recent updates, favorites, votes, momentum, and Terry Score.

libraries
307
favorites
1.2k
upvotes
1.3k
Filter
Sort by
02
Source 1 BSP Import thumbnail
Source 1 BSP Import doc.bsp_import

Editor Tool for importing bsp. Creates appropriate GameObjects with their components. Makes use of the mapping MeshComponent.

+0 24h
8favorites
9upvotes
65%Terry score
03
Source Movement thumbnail
Source Movement noclipstudio.sourcemovement

No summary provided.

+0 24h
5favorites
6upvotes
69%Terry score
04
Matrix Rain Shader thumbnail
Matrix Rain Shader quack.matrix_rain

Matrix Rain Shader library version w/ sources

+0 24h
3favorites
3upvotes
53%Terry score
05
Project Settings thumbnail
Project Settings coomzy.projectsettings

Singleton based GameResources that have a custom dockable window for easy access!

+0 24h
2favorites
0upvotes
--Terry score
06
Resource Embed thumbnail
Resource Embed fdd.resourceembed

Adds an attribute that allows you to embed game resources in components.

+0 24h
0favorites
2upvotes
43%Terry score

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.