Skip to content
Eureka Phone: iPhone-style

Overview

The iPhone-style phone is a second interface on the same phone core as the Duo. Install it alone, or next to the Duo on one server.

The iPhone-style phone is a familiar, single-screen interface: clean layouts, fluid transitions and navigation players already know. It runs on the same core as the Duo, so everything the core provides is the same on both designs: numbers, messages, calls, every app, the database and the server settings.

Resource What it is Scripts
eureka_phone The phone core, shared by every Eureka phone design. Server and client
eureka_iphone The iPhone-style page: its interface, its client settings and its items. It runs the core's bridge and has no server script. Client only

If you already run the Duo, you already have the core. You add only the page resource and its item; nothing in the database or your settings changes except duo_phone_items. See Running both designs.

What is the same as the Duo

  • Every server setting (duo_* convars), the apps and what they need, the database schema and migrations, staff moderation and the exports for your own resources. Those are documented once, in the Duo section: Server settings, Apps and what they need, Exports and integrations.
  • The key that opens the phone (F1, "Phone: open or close") belongs to the core and opens whichever design the player carries.
  • Players on the two designs text and call each other: it is one phone network.

What differs

  • One screen, no fold. The iPhone-style page has no fold key; it defines no keys of its own.
  • Its own item. The page shows the phones whose inventory item it lists in models (iphone by default). The server records the item name as the device's model, which is how the core finds the page for a phone.
  • Its own origin. The page's NUI origin is https://cfx-nui-eureka_iphone; your object store's CORS rule must allow it too if you use media.

Requirements

The same as the Duo's: see Requirements. In short, oxmysql with MariaDB 10.11+ or MySQL 8.0+, a framework with an adapter (Qbox, QBCore, ESX or standalone), ox_inventory, pma-voice for calls, and optionally an S3-compatible object store for media.

Last updated October 2, 2026