#The issue of the resource manifest

1 messages · Page 1 of 1 (latest)

tulip scarab
#

Are there any reasons why many standard resources don't have dependencies written in the manifest, even qb-core is trivial

dire locust
#

Standalone resources don’t have any dependencies, hence the name. Otherwise, it’s just bad practice. If the dependencies aren’t installed and it’s not marked as a dependency in the fxmanifest, the first time the script tries to use an export or anything from the non-existing dependency, it will throw an error. Something like “no such export as addItem in resource qb-core”.

There are some things that don’t really need to be specified as a dependency though. For example, if you download a script made for QB, it should be obvious that you need qbcore for the script to function, so it wouldn’t be too important to add as a dependency in the manifest, but it doesn’t hurt.

Adding as a dependency in the manifest just prevents the script from starting at all if the dependency isn’t present.

#

So good practice is to always add it in the manifest if you are using exports from other resources 👍