Resource Starting Sequence

To ensure our resources run smoothly, we have to explicitly verify that our resources are being correctly started. This is not always needed, it entirely depends on your server and the resources you are running.

Below you will find various common issues and our fixes for your server.cfg structure.

Starting Entire Directories

First up, a very common practice to start a lot of resources. Starting an entire directory, also known as a folder, can prove problematic. It attempts to start the resources in an alphabetic order, meaning any resource alphabetically before the l in zyke_lib will attempt to start first. This can cause various issues. Make sure that you are starting every resource manually in the server.cfg.

This means that if you are currently starting your resources something like this:

ensure [zyke]

You have to instead run them like this:

ensure zyke_lib
ensure zyke_sounds
ensure zyke_smoking
...

Starting Before Dependencies

If you are using resources such as ox_inventory or perhaps some death system, such as wasabi_ambulance, our library needs to be started afterwards to ensure the dependencies are correctly recognized.

Our best recommendation is that you start zyke_lib at the end of your starting sequence, and all of your other resources from us after that. This ensures that everything is propertly started before.