What is the library and why is it encrypted?

This page explains the purpose of our shared library system, why it exists, and why it's encrypted — even in open-source scripts.

🤔 What is the library?

Our library (lib) is a core module used in many of our scripts to centralize shared logic and streamline development. It includes essential functions like:

• Framework detection and abstraction (QBCore, ESX, etc.)

• Utility functions (notifications, money checking, etc.)

• Reliable event registration and wrappers to keep your code clean and maintainable

• UI helpers and more

---

⚙️ Why do we use a shared library?

✅ Centralized maintenance: Fix or improve one place, and every script benefits immediately. No more patchwork updates or duplicated fixes. ✅ Cleaner scripts: Smaller, leaner scripts that focus on their core purpose — making development faster and debugging easier. ✅ Framework-ready: Seamlessly supports multiple frameworks without manual rewrites or hacks, future-proofing your projects. ✅ Consistency: Guarantees uniform behavior and user experience across all scripts, making your server feel polished and professional. ✅ Scalability: As your project grows, the library adapts — adding features once and having them instantly available everywhere. ✅ Community-friendly: Enables easier collaboration and onboarding, since everyone works with the same trusted foundation.

---

🆕 What’s changing in new scripts?

In newer versions of our scripts, the library is now bundled directly inside the script itself.

• This means you don’t need to start multiple resources for one script to work.

• Everything you need is packaged together for easier installation and management.

• No more “missing lib” errors when setting up a single script.

---

🔔 Important notice

Older scripts may still require starting the library as a separate resource. Newer scripts already include the library inside the main resource — so do not start an extra lib file unless specifically stated. We make this clear in every product description, but we want to mention it here as well to avoid confusion and extra tickets.

---

🔒 Why is it encrypted, even in open source?

To protect the structure, logic, and prevent abuse or unauthorized redistribution. It also ensures script stability across updates and prevents tampering that could break compatibility.

---

📦 Why not always include it inside each script?

We are moving toward that approach for convenience — but some older or more modular systems still benefit from having a shared external library.

---

🙋 Still confused?

No problem — open a ticket, we’re happy to help. We also welcome feedback through polls and suggestions — most improvements came directly from our community.