AWSAWS DOCUMENTATION38 source-matched resource guides
Documentation/Utilities/AWS Hacker Phone
Utilities3 min readUpdated 2026-10-15
AWS Hacker Phone cover

AWS Hacker Phone

An in-game hacker phone for configurable vehicle, prop and media interactions.

Installation

Requirements

  • oxmysql as shipped in fxmanifest.lua
  • QBCore, Qbox, ESX or the configured standalone mode
  • xsound for features using positional audio; optional dispatch/TV integrations when selected

Startup order

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

ensure oxmysql
ensure qb-core
ensure aws-hacker-pro

Setup steps

  1. shared/cfg.lua selects the framework; its default is qb rather than automatic detection.
  2. Register hacker_phone, or the item name configured in cfg.phoneItem, in your inventory. The server includes framework usable-item registration.
  3. For standalone mode set cfg.framework to standalone and use /hackerphone unless standaloneCommand was changed.
  4. Persistent hacker data is stored in server/data.json. Keep it writable and preserve it during upgrades.

Gameplay and usage

  1. Use the hacker phone and test one configured vehicle or prop interaction.
  2. For TV/botnet options, verify supported media URLs and the optional audio/TV resources separately.

Configuration

  • shared/cfg.lua: framework, phoneItem, phoneHackDistance and optional phoneJobs configure access.
  • frameworkHooks.vehicleKeys selects key events after vehicle interactions.
  • dispatch.system, matrixVideoUrl, chaosSoundUrl and laptopAudioOnlyEffects configure optional media/dispatch behavior.
  • client/custom_hack.lua contains examples for adding custom interactions.

Exports and integrations

  • aws-hacker-pro.IsTvHijackedNearCoords — see aws-hacker-pro/client/tv_renderer.lua for its arguments and client/server context.

Troubleshooting

  • Phone does not open: verify framework selection and item registration.

  • Data does not save: inspect server/data.json write permissions.

  • Missing sound/key handoff: check the relevant optional resource and configured event.

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

Package reference

Manifest Version
fxmanifest.lua 1.0.0

Database files

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

Configuration reference

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.