Skip to main content
Check this page against your server before you buy. Almost every product that fails to start on a new server is missing one of the requirements below, not broken.

​
What every product needs

​
What some products need

Each product’s overview page lists exactly what it needs. These are the possibilities: The resources each of those can be, by exact folder name, are in Supported resources.

​
Frequently asked

Only if the product needs one, and its overview page says so. Any of the three works: no product is written for one of them in particular. A server that runs its own framework can connect it with Use your own framework or resources.
Notifications, help text, progress bars and fuel fall back to the product’s own version when none of yours is recognised. Inventories, databases, menus, text input and targeting have no fallback. If yours is not listed, it can still be connected by a scripter with Use your own framework or resources.
No. The product’s scripts are protected. Everything meant to be changed is in its configs folder (settings) and locales folder (text), and both are documented key by key on the product’s own pages.
On the servers your Cfx.re account is allowed to run it on. See Licensing.
No. When a newer release exists, your server console says so once at start, and you install it when you choose. See Update a product.
element_sdk checks once per start whether a newer release exists, and reports errors raised inside Element Labs resources. Both can be turned off. Exactly what is sent, and what never is, is in Privacy and data.
Yes. Every piece of text is in a language file you can edit, and you can add a language the product does not ship. See Languages.