How libraries work
Libraries live inside your project’sLibraries/ folder. Each library has its own Assets/, Code/, and Editor/ subfolders.
Your game code and editor code can access every class defined in an installed library. The library cannot access your game code directly.
Libraries are not compiled assemblies. When you share a library, you share its source code — everything inside the library folder is included.
Libraries are not downloaded automatically. You download a library to
<project>/Libraries/ and commit it to your source control. This means you always have a copy and can modify or delete files as needed.Why it works this way
Distributing source instead of binaries gives you full control:- You can read the code before running it.
- You can edit or delete files you don’t need.
- The library won’t disappear because an author unpublished it.
Installing a library
Browse available libraries
The Library Manager shows libraries you can install. Find the one you want.
Creating a library
To create a new library, add a new project insideLibraries/ with its own Assets/, Code/, and Editor/ folders. Structure it the same way you would a game project, keeping the code self-contained.
Publishing a library
Publish a library the same way you publish any other s&box package:- Right-click the library in Library Manager.
- Select Publish Project.