Skip to content
Blixt

Blixt Tablet

Blixt Tablet is the free companion tablet for Blixt Phone. It ships its own NUI and client bridge, while forwarding server-side data work through the core blixt resource.

Status and price

Section titled “Status and price”
  • Status: available.
  • Price: free.
  • Folder name: blixt-tablet.
  • Resource name: blixt-tablet.
  • Requires: Blixt Phone installed and started first.
  • Download: items.tebex.io.
  • Support: Blixt Discord.

Add the tablet to your Tebex cart at $0. There is no separate tablet license.

What it does

Section titled “What it does”

The tablet gives players a wider device surface for Blixt apps. It shares the phone’s database, framework adapter, player records, and config, but uses its own home layout and tablet-specific shell behaviour.

Good tablet use cases:

  • Management, mail, notes, marketplace, and calendar-heavy roleplay.
  • Jobs or departments that need a bigger screen.
  • External Blixt apps that benefit from a wider layout.

Install order

Section titled “Install order”

Install and start blixt before blixt-tablet.

ensure oxmysql
ensure screenshot-basic
ensure pma-voice


ensure blixt
ensure blixt-tablet

The folder must stay named blixt-tablet; its manifest depends on blixt.

Dependencies

Section titled “Dependencies”

The tablet depends on the phone resource for server data. It does not need its own database connection or framework adapter.

  • Required first: blixt.
  • Inherited through blixt: oxmysql, framework adapter, config, and migrations.
  • Recommended: keep screenshot-basic and pma-voice installed because the phone suite expects them.

Configuration

Section titled “Configuration”

The tablet uses the same blixt/config.json file as the phone.

Common fields:

  • tablet.branding.deviceName: visible tablet status-bar name.
  • tablet.disabledApps: hide apps that do not make sense on tablet.
  • tablet.homeOrder: default home-screen app order.
  • tablet.featuredApps: featured App Store apps for tablet users.
  • tablet.toggleKey: default keybind for /tablet.

Example:

{
  "tablet": {
    "disabledApps": ["dialer", "bump"],
    "homeOrder": ["calendar", "mail", "notes", "marketplace", "garage", "jobs"],
    "branding": { "deviceName": "Blixt Tablet" },
    "toggleKey": "F2"
  }
}

See Configuration for the full schema.

Important convars

Section titled “Important convars”

Tablet has no special convar layer. Configure shared Blixt convars before ensure blixt, especially:

set mysql_connection_string "mysql://user:password@127.0.0.1:3306/blixt"
set blixt:framework "auto"

If external tablet apps need privileged Blixt exports, add them to blixt:trusted_resources. See Convars.

Privacy and roleplay rules

Section titled “Privacy and roleplay rules”

Tablet uses the same character account as the phone. Messages read on tablet are read on phone too.

The tablet should follow the same roleplay constraints as the phone: do not expose hidden framework metadata, unknown numbers remain unknown, and data should be scoped to what the character can reasonably know.

Usage

Section titled “Usage”
  • Open: /tablet command or the bound key.
  • Close: same key or Escape.
  • External apps: app authors can use useWideAppLayout() and useDeviceKind() to render tablet-aware layouts.
Section titled “Related resources”