SQD Lib Mod (26.3) – Stop Copying Code Between Your Plugins and Fabric Mods

SQD Lib Mod gives coders a small set of shared tools for building plugins and mods. It saves you from copying and pasting the same code again and again. The library also helps you move your plugins over to mods.

Features:

• Tiny Size: Has only about 10 classes. The built file is just 21.1 KB, so it barely changes the size of your jar.
• Shared Helper Code: Adds common tools that plugins and mods can reuse, so you write less of the same code.
• Many Platforms: Comes in versions for Paper, Velocity, Bungee, Spigot, and Fabric.
• Plugin to Mod Move: Helps coders turn their plugins into mods.
• Lets server admins get the library from GitHub Releases when a plugin says it needs it.
• Changes fast between versions, so one version may work while another breaks plugins that use an older or newer one.

How to Use:

1. Add the maven repository https://maven.chamosmp.net/releases to the repositories block in your build file.
2. For the recommended bundling way in a plugin, add the shadow plugin com.gradleup.shadow. Then add implementation("com.sqdstudios.sqdlib:sqdlib-paper:3.2.0-BETA"). Swap paper for velocity, bungee, or spigot if you need them.
3. In the shadowJar task, use relocate("com.sqdstudios.sqdlib", "(your plugin group).libs.sqdlib") to move the library into your own package.
4. For a Fabric mod, add implementation("com.sqdstudios.sqdlib:sqdlib-fabric:3.2.0-BETA"). Replace 3.2.0-BETA with the latest version.
5. If you want the library as a separate mod or plugin instead (not recommended), use compileOnly with the same names. With a paper-plugin.yml, set join-classpath: true or you get class not found errors.
6. When you move from v3 to v4, replace every net.chamosmp with com.sqdstudios. Do the same in the dependency line.
7. If you come from an older version like v2, delete the packages that are not found. Let your IDE suggest the new ones.

SQD Lib Mod Download Links