Architecture Overview

Envi-Pawnshop uses a client-server setup with a computer-based UI layer.

Main areas

Client

The client side handles:

• targets and zones

• menus

• mission flow

• vehicle and shop interactions

• NUI state handoff

Server

The server side handles:

• shop state

• worker data

• funds

• pawns

• exports

• supplier offers

• vehicles

• database reads and writes

Shared

The shared layer holds:

• config

• language strings

Web UI

The management UI runs through the Envi computer system.

That gives Pawnshop a consistent desktop-style management experience.

File responsibilities

Typical files include:

• client/client.lua

• client/client_edit.lua

• client/nui_management.lua

• server/server.lua

• server/server_edit.lua

• shared/config.lua

• shared/lang.lua

Dependency role

Pawnshop relies heavily on:

• envi-bridge for framework abstraction

• envi-computer for UI systems, workers, and email features

• envi-zone-tool for in-world placement and interaction zones

Custom integration advice

• keep server-specific replacements inside editable helpers

• prefer public exports and events over internal hooks

• treat the Envi computer layer as part of the product flow, not a separate add-on

Related pages

• Database Schema

• Exports and Events

• Customization Guide