en-admin

en-admin puts developer and admin tools in one panel, opened with F10:

• Players: goto, bring, heal, revive, freeze, kick, give item, give cash.
• Vehicles: spawn from quick picks or any model, and give owned vehicles through en-garages.
• World: weather, time, time freeze and blackout (through en-weathersync), and clearing zombies.
• Announcements to the whole server.
• Self tools: noclip, god mode, invisibility, teleport to your waypoint or to coordinates, copy coordinates in several formats, and an "entity laser" to inspect, copy or delete entities.

It also hosts the Build tab, an in-game content editor. Admins place and edit traders, vehicle dealers, garages, quest NPCs, quests, crafting benches, barbers, spawn points and zombie zones without touching config files. Each owning resource describes its own form and validates the data; en-core's content registry stores it and makes it live.

#At a glance

#How it works

#Permissions

Commands are granted to Config.principal (default group.admin). Every panel action is checked on the server against the ACE command.admin, and the server console (source 0) always counts as admin. Other resources can reuse the same check with the IsAdmin export.

# server.cfg: make someone an admin
add_principal identifier.license:xxxxxxxxxxxxxxxxxxxxxxxx group.admin

With Config.log on, every admin action is printed to the server console.

#Noclip

• WASD moves, E goes up, Q goes down.
• Shift is fast (x3), Ctrl is slow (x0.25), and the mouse wheel cycles speeds.
• Noclip moves your vehicle when you are driving.
• You are invisible and have no collision while active, with a few seconds of fall damage grace when you leave it.

#Entity laser

#Spawned vehicles

/car and the Vehicles tab spawn the car and put you in it. Your previous admin car is deleted if it is empty. Spawned cars get a plate like ADMINnnn, full fuel (Entity(vehicle).state.fuel = 100.0) and are hotwired through en-vehiclekeys when it is running.

#The Build tab

Each kind in Config.builder belongs to a resource. Kinds whose resource isn't started are hidden.

When an admin saves, en-admin calls the owning resource's BuilderValidate, then encore.content.save(kind, id, data, author). Delete calls encore.content.remove(kind, id). If a placed entry was overriding a config entry with the same id, deleting it brings the config version back. The owning resource picks up changes with encore.content.watch(kind, onAll, onChange). See Content registry and Content API.

#Builder contract

To make your own kind editable, the owning resource exports these on the server:

In a schema field, key is a dotted path into the data. Field types used by the shipped resources include 'text', 'select', 'coords' and 'number'.

#Configuration

config.lua:

-- config.lua
Config.principal = 'group.admin'
Config.log = true

Config.vehicles = {
    { model = 'rebel', label = 'Rebel', class = 'Off-road' },
    { model = 'technical', label = 'Technical', class = 'Off-road' },
    { model = 'mule', label = 'Mule', class = 'Commercial' },
}

#Exports

Server exports on exports['en-admin']:

#Commands

All restricted to Config.principal.

#Events

Client net events the server sends to an admin or a target player:

The panel sends its actions through the en-admin:action callback: goto, bring, heal, revive, freeze, kick, giveItem, giveCash, spawnVehicle, giveVehicle, fixVehicle, deleteEntity, setWeather, setTime, freezeTime, blackout, clearZombies, announce, and the builder actions builderList, builderGet, builderNew, builderSave, builderDelete.

#Examples

Gate your own admin feature on en-admin's permission check:

-- server
RegisterNetEvent('my-res:wipeLoot', function()
    local src = source
    if not exports['en-admin']:IsAdmin(src) then return end
    -- ...
end)

Make your own resource's content editable in the Build tab. First add the kind to en-admin's config.lua:

-- en-admin/config.lua, inside Config.builder
{ kind = 'cache', label = 'Supply caches', singular = 'supply cache', resource = 'my-caches' },

Then export the builder contract from my-caches:

-- my-caches/server.lua
exports('BuilderSchema', function(kind)
    if kind ~= 'cache' then return nil end
    return {
        { key = 'label', type = 'text', label = 'Name', max = 60, required = true },
        { key = 'coords', type = 'coords', label = 'Position', required = true },
        { key = 'respawn', type = 'number', label = 'Respawn (min)', min = 1, max = 240, default = 30 },
    }
end)

exports('BuilderTemplate', function(kind)
    return kind == 'cache' and { label = 'New Cache', respawn = 30 } or nil
end)

exports('BuilderValidate', function(kind, id, data)
    return data.coords ~= nil, 'A cache needs a position.'
end)

-- plus BuilderList and BuilderGet, and pick up saved caches with
-- encore.content.watch('cache', onAll, onChange)

#Related

• Content registry
• Content API
• Commands
• en-weathersync
• en-zombies