Skip to main content
When boot fails, ug-core prints every error it found, then Boot aborted: N error(s)., then stops. Players who try to connect see “The server is not ready. Try again later.”
A convar in server.cfg has a value of the wrong type. Fix the set line. Booleans take true, false, 1 or 0.
A value in a config file has the wrong type or is out of range. The message says what’s expected. ug config <name> shows the current values.
A Lua syntax error in a config file. The number after the file name is the line. Delete the file to restore the defaults if you’re stuck.
oxmysql did not connect. Check that oxmysql starts before ug-core and that mysql_connection_string is right.
Your database server is too old. Upgrade it.
You disabled a module another enabled module needs. Follow the message in config/modules.lua.
A table could not be created or changed. The message includes the MySQL error. Fix the cause, often permissions of the database user, and restart.
Every character falls back to unemployed, so it must exist in your jobs. The same applies to none in config/gangs.lua.
Add add_ace resource.ug-core command allow to server.cfg. Boot continues, but permission grants cannot be applied.

​
Resources that use UgCore

Your resource starts before ug-core. Add dependency 'ug-core' to its manifest and ensure it after ug-core.
The resource needs a newer ug-core. Update ug-core.
The resource uses a module you disabled. Enable it in config/modules.lua, or don’t use that resource.
The resource used a module before ug-core finished booting. Developers wait with UgCore.Lifecycle.Await('Ready').