Configuration

EndCore is configured with plain Lua files inside each resource. There is no web panel or database settings table: open the file, change the value, restart. Content that admins place in game (traders, garages, zones) is the exception; it is stored in the database by the content registry.

#How config files work

• Config files return or define plain Lua tables. Keep the syntax valid: a missing comma stops the resource from starting, and the console shows the line.
• Files named shared are sent to players' game clients. Files named server never leave the server, so put anything sensitive (webhooks, ban hooks) there.
• Files are read when a resource starts. Restart the resource after editing. For en-core, a full server restart is the safest option because every other resource depends on it.

#en-core

en-core has four config files and three shared data files.

#Most-changed settings in config/server.lua

Every survival key and its effect is listed in Survival system.

The ban hook runs when a player connects. Return true and a reason to reject them:

-- en-core/config/server.lua (excerpt)
bans = {
    -- ...
    checkForBan = function(license)
        local row = MySQL.single.await('SELECT reason FROM my_bans WHERE license = ?', { license })
        if row then
            return true, ('Banned: %s'):format(row.reason)
        end
        return false, nil
    end,
},

#Most-changed settings in config/shared.lua and config/client.lua

See Player data, Money and cash, Jobs, Groups, XP and levels and World and death for the full tables.

#Gameplay resources

Each resource keeps its settings in its own folder. Paths are relative to resources/[encore]/.

#Content placed in game

Traders, vehicle dealers, garages, quest NPCs, quests, crafting benches, barbers, spawn points and zombie zones can also be placed from the Build tab of the en-admin panel (F10). Placed entries are stored in the encore_content table and go live immediately.

• A placed entry with the same id as a config entry replaces it.
• Deleting the placed entry restores the config version.

This means you can keep sensible defaults in config files and let your staff adjust the live world without restarts. See en-admin and Content registry.

#Convars

setr encore:disablebridge true

en-core reads no other convars.

#ACEs and principals

Some resources let you change the principal: Config.principal in en-admin, ServerConfig.adminPrincipal in en-inventory, and Config.adminPrincipal in en-doorlock. See Commands for the full list.