Page cover

FAQ

These are the most frequently asked questions regarding CB-GangSystem!

chevron-rightI own V1, do I get V2 for FREE?hashtag

Yep! Make a ticket in my Discord and send your Transaction ID and CFX Username. We'll verify the purchase and send V2 straight to your Keymaster account!

chevron-rightDoes this script work with Lation Drugs?hashtag

YES! This script works with Lation Drugs! We added a config variable called ServerConfig.LationDrugs that allows you to enable this feature!

chevron-rightDo I have to use the Community Bridge?hashtag

Yes! Community Bridge is a required dependency. Instead of creating my own library, like a lot of other creators are doing, I'm using a free and open source library created and maintained by the community. This means better compatibility across different frameworks—and most importantly, faster development on my end. The bridge streamlines a lot of the backend work, so I can push out new features and updates more efficiently.

chevron-rightCan I use my current drug script for the Gang System, or am I bound to the system that comes with the script?hashtag

You absolutely have the power to use your own drug script. Virtually everything in the gang system can be turned off/removed if you want it to be. If you have any questions or even need something changed for you, we are happy to help. Please open a ticket in our Discord for assistance!

chevron-rightIs there be a conversion system in place to migrate from V1?hashtag

Gang System V2 is not directly compatible with data from V1. However, with some SQL knowledge and a little effort, it’s possible to migrate most of your existing data. Please note that I do not offer support for this process. V2 is a significant upgrade from V1.

But why? Gang System V2 was built from the ground up with performance, scalability, and flexibility in mind. As a result, the underlying data structures and logic are significantly different from V1. Maintaining native compatibility would have forced me to limit innovation or carry forward outdated design decisions. Instead, I focused on delivering a modern, more efficient system—even if it meant breaking compatibility. This approach allows me to offer a more stable and feature-rich experience moving forward.

Last updated