AWS DEVELOPMENT / DOCUMENTATION

Your server. Our expertise.

Everything you need to install, configure and build.

114 guides • 12 collections • Always here to help
Documentation/AWS Loading Screen
Installation notes

Use the exact folder, SQL file, dependency and startup order shown for your downloaded package. Some resources contain FXAP-protected runtime files, so their guides cover only the source and configuration that can be inspected.

AWS Loading Screen

A FiveM loadscreen with configurable server branding, background video, gallery, music, news ticker, and an optional Discord staff-sync bot.

Install

  1. Keep the resource name rio-loading and copy the complete folder, including gallery images, video files, and logos referenced by fxmanifest.lua.
  2. Edit config.js: set serverName, serverLogo, video paths, volume, gallery, social links, news, and staff list.
  3. Add the resource after any anti-cheat integration it references:
ensure rio-loading

There is no SQL file. Every configured image/video path must exist and be included by fxmanifest.lua.

Optional Discord staff sync

The public discord.config.js now contains placeholders and starts with enabled set to false.

  1. Create a bot in Discord Developer Portal, enable Server Members Intent, and invite it with permission to view the server and member roles.
  2. Set token, guildId, and roleMapping to your own values.
  3. Set enabled to true only after those values are valid. Keep this file private; never publish the token.
  4. Run npm install in this folder if node_modules is not present. package.json declares discord.js; the manifest starts bot.js as a server script.

The token previously present in this working copy must be rotated in Discord before use. Treat it as compromised.

Troubleshooting

  • Black video: use an H.264 MP4 and check videoUrl/fallback paths.
  • Missing gallery image: verify its name in config.js and that the file exists in gallery/.
  • Staff not syncing: check token, guild ID, role IDs, bot membership, Server Members Intent, and server logs.
  • Wrong server branding: replace sample values in config.js and the logo/media assets.