Base Resource
loadingscreen
The supplied manifest describes this resource as “VCore - Loadingscreen”.
Introduction
The supplied manifest describes this resource as “VCore - Loadingscreen”.
1Client Lua
0Server Lua
3Exports
3Events
0SQL tables
UI/web files detected.
Dependencies & References
| Resource | Detected as | Package status |
|---|---|---|
| — | No dependency/reference detected | — |
Cross-resource export calls
| Resource | Functions called |
|---|---|
| — | No cross-resource export calls detected. |
Installation / Start Order
The supplied server.cfg enables this resource in the FiveM base stage at enabled-resource position 7. Base installation also depends on the global prerequisites and consolidated VCORE_INSTALL.sql documented in Getting Started.
server.cfg
ensure loadingscreenConfiguration
Config files
web/config.json
Top-level config keys detected
No Config/VCOREConfig keys detected by the audit.
Events, Exports & Callbacks
Exports
Client exports3
BeginShutdownShutdowncloseLoadingScreen
Callbacks
No Vcore callback registrations were detected.
Registered network events
Client registered events3
vcore-loadingscreen:client:closevcore-loadingscreen:client:handoffvcore-loadingscreen:client:shutdown
Commands
Client commands1
closeloading
Database / SQL
No resource-local SQL file was detected.
No CREATE TABLE statements detected inside this resource.
The root Base package also ships the consolidated VCORE_INSTALL.sql.
Source Layout
| Area | Detected files |
|---|---|
| Client Lua | 1 |
| Server Lua | 0 |
| Other/shared Lua | 1 |
| JavaScript | 1 |
| HTML | 1 |
| CSS | 1 |
| SQL | 0 |
Troubleshooting
- Confirm all manifest dependencies are started before
loadingscreen. - Check the supplied start-order note above; resources absent from server.cfg need an explicit decision before enabling.
- If database queries fail, import the consolidated Base SQL and any resource-local SQL listed above.
- If the UI fails, verify the resource's NUI files and
ui_pagewhen one is declared.