Skip to main content
All overlay configuration happens within your codebase, which gives full flexibility. The following properties can be passed into the overlayed function:

electron

The electron instance to use for the overlay. Note this should be globally imported from the electron package.
  • Type
  • Example

applicationId

The id of the application, this can be found in the Overlayed Dashboard
  • Type
  • Example

modules

The modules to load.
  • Type
  • Details Modules allow you to subscribe to a specific game, including:
    • Game Events
    • Overlay Events like when the game launches
  • Example

keybinds

The app’s keybinds
  • Type
  • Details Keybinds require the array of KeyboardEvent#code and the mode of the keybind.
    • “Hold” will trigger the callback when the keybind is held down.
    • “Toggle” will trigger the callback when the keybind is toggled on and off.
    Read more here.
  • Example

init

  • Type
  • Default: true
  • Details Whether to initialize the overlay right when the function is called. Read more here.
  • Example

universal

  • Type
  • Default: false
  • Details When true, the overlay will be loaded and attempt to render inside of all supported games. When false, only games registered under the modules array will be loaded. Read more here.
  • Example

debug

  • Type
  • Default: false
  • Details When enabled:
    • logger.debug() logs will be printed and saved to the log file
    Warning: Debug mode should be disabled in production environments as it can impact performance and generate large log files. Read more about logging here.
  • Example

featureFlags

A record of feature flag names to their default values. Keys provide typed access to remotely managed flags, values are used as defaults before the API responds or when a flag is missing.
  • Type
  • Default: undefined
  • Details Registered flag names enable type-safe access via overlay.featureFlags.get(flagName) and overlay.featureFlags.on(flagName, cb). Warnings are logged if a registered flag is not found in the API response. The featureFlags module also exposes a ready promise that resolves once the initial fetch completes. Read more here.
  • Example

site

  • Type
  • Default: { manualUpdates: false }
  • Details Configuration for site (frontend) updates. When manualUpdates is true, your site will not automatically update when a new version is deployed. Instead, you can listen for the siteUpdateReady event on overlayed.updater.site and prompt users to update. See Site Updates for more information.
  • Example