Skip to main content
A product is a single directory under your server’s resources. Knowing what each part of it is tells you what you may edit, what you must keep a copy of, and what an update replaces.

The layout

Some products ship fewer of these. A product with no interface has no ui, a product that adds nothing to the world has no stream, and a product that needs nothing from your other resources has no integrations and no installer scripts.

What an update replaces

An update replaces the whole directory. Everything above comes from the new release, including configs and locales. Keep your edited configuration and language files outside the resource directory and put them back after each update. Update a product or the SDK describes the procedure.

Start order

element_sdk must be running before a product starts. List it first in server.cfg:
At start, a product checks that element_sdk is present, running, and within the versions the product accepts. Any of those failing stops the product before it does anything, with a console line naming the reason. See SDK version requirements. Resources beyond the SDK are different: a product that uses your framework, inventory or database picks one the first time it needs it, from what is running then, so their position in server.cfg does not matter. Once picked, the choice is kept for the rest of the session. See Supported server resources.