AWS Loading Screen

A configurable connection/loading screen with background video, server branding, ticker messages and framework-aware shutdown.

Installation

Requirements

• FiveM
• Optional QBCore, Qbox or ESX for framework-aware load completion

Startup order

This example selects one framework and target. Use the resources matching your configuration and start dependencies first.

ensure aws-loadingscreen

Setup steps

1. Disable competing loading-screen resources to avoid overlapping screens.
2. Place your configured video and logo in ui/assets/ and keep filenames identical to Config.BackgroundVideo and Config.Logo.
3. Select the framework or use auto. Review Config.FallbackTimeout so the loading screen can close if the expected framework event is unavailable.

Gameplay and usage

1. Reconnect through the normal server connection flow to test the actual loadscreen lifecycle.
2. Check the logo, video audio, progress and eventual return to gameplay.

Configuration

• config.lua: Config.Headline, TickerItems, Theme and Locale control the visible content.
• Config.BackgroundVideo, BackgroundVideoVolume and Logo select the media.
• Config.Framework and FallbackTimeout control shutdown.
• shared/locale.lua and the included locale files provide translation handling.

Exports and integrations

• aws-loadingscreen.Hide — see aws-loadingscreen/client/cl_main.lua for its arguments and client/server context.

Troubleshooting

• No background: verify the exact media path under ui/assets/ and use a browser-supported codec.

• Screen stays open: inspect framework selection and fallback timeout.

• Two screens appear: disable the other loading-screen resource.

• Include the package version, framework and exact server/F8 error when requesting support. Remove private tokens and player data.

Package reference

Database files

No standalone SQL file is included. Check the installation steps above for tables created by server code.

Configuration reference

• aws-loadingscreen/config.lua: Theme, Locale, TickerItems, Headline, AutoTemp, Temperature, Celsius, Framework, FallbackTimeout, BackgroundVideo, BackgroundVideoVolume, Logo

Frequently asked questions

Does this need Keymaster or an escrow key?

The Lua sources in this delivery package were readable in the static audit. No /assetpacks requirement is added by this package. Required framework, inventory and map resources still need to be installed separately.

Can I change the folder or database table names?

Keep the supplied folder names. Historical event, SQL and KVP identifiers are retained to protect existing integrations and saved data. Renaming a table or event requires a separate migration.

Why is an interface or item missing?

Check the startup order, selected framework/target adapter, inventory item definitions and the server/F8 console. The package does not install an entire framework or inventory for you.

Has this been tested on my server?

ZIP integrity, source readability, script syntax and manifest references were checked locally. Multiplayer gameplay, your framework version and integrations require a FiveM server acceptance test before a public release.