Skip to main content

Which configuration is used?

When RoadPhone is running, RoadPad adopts its Lua configuration and keeps a defined set of tablet-specific settings from roadpad/config.lua. The tablet’s frontend catalogue remains in roadpad/public/static/config/config.json. In linked legacy mode, the tablet ownership check uses Config.NeedItem from roadpad/config.lua; RoadPhone’s own phone-item checks use its configuration. Metadata pairing requires a real tablet item independently of the legacy exemption. See Pairing & Metadata.

Tablet controls

roadpad/config.lua
Players can change an existing FiveM key binding in the game’s key-binding settings. Changing Config.OpenKey changes the default rather than replacing every player’s saved binding. Use a tablet item to select a different physical tablet. The key and command reopen the last selection. The client API offers exports for other resources. Config.Tablet controls the prop, bone, offsets, rotation and holding animation. Preserve the supplied defaults unless you are adjusting your server’s hand placement.

Business

The Business app provides the tablet’s company and job-application workflows. Set the minimum grade that can manage each configured company:
roadpad/config.lua
Config.UnemployedJob is the job assigned when an employee is dismissed. Job names and grades must exist in your framework. The companies players can apply to are listed separately in the frontend configuration. This is a fragment to merge into the existing object:
roadpad/public/static/config/config.json

Marketplace

Configure items that cannot be listed:
roadpad/config.lua
RoadPad also excludes recognized tablet/phone device items from the Marketplace to avoid losing their device data through ordinary item sales. Set the inventory image location used by item listings. This example is for ox_inventory; change both fields to match your inventory:
roadpad/public/static/config/config.json
The startup schema in sql/roadpad_apps.sql supplies Business, Marketplace and Vehicle Marketplace tables in both operating modes.

Apps, language and uploads

  • AppStore in the tablet’s config.json defines the app catalogue. Remove entries you do not want to offer; keep route identifiers for built-in apps unchanged. Use light_icon and dark_icon for custom icons.
  • AppInfos holds App Shop descriptions and listing details. Restore entries only for separately sold Custom Apps you have installed and own.
  • Set Config.Locale in the active backend configuration for its default language. Players can choose their interface language in Settings. App display names in config.json are configured separately.
  • Configure uploads in the active backend; see Fivemanage setup.
  • Optionally set Config.RoadPad = true in RoadPhone to list the tablet under Settings > Bluetooth. This listing does not replace the tablet’s device picker.
Restart affected resources after changing Lua settings. Preserve the new defaults and merge your previous configuration when updating.