NOTWENNODE
Notwen interactions product scene
IN DEVELOPMENTnot_interactions
NOTWEN / GAMEPLAY

Notwen Interactions

A shared interaction language for world actions while the underlying product remains authoritative for the real gameplay decision.

FRAMEWORK BRIDGESESXQBCoreQboxCustom
STATUSIn development
RUNTIMEFiveM / CFX
MODELNotwen native
DOCSIncluded
CURRENT STATEIn development

The resource page is public for architecture and integration context. Purchase will open when the product is ready.

Open documentation
PRODUCT SCOPE

What this resource owns.

Context actions for entities, zones and world interactions with reusable conditions.

INCLUDES

Core capabilities

  • Entity/world actions
  • Context menus
  • Conditional actions
  • Reusable registration API
  • Theme consistency
  • Bridge friendly permission checks
USE CASES

Where it fits

  • NPC interactions
  • Doors and world actions
  • Vehicle actions
  • Job interactions
INTEGRATION MODEL

Own the domain. Bridge the server.

Framework-specific access stays at the integration edge so product behavior can remain consistent across server stacks.

FRAMEWORK BRIDGE

ESX · QBCore · Qbox · Custom

Standalone interaction layer with adapters/hooks for ESX, QBCore, Qbox or custom permissions and job state.

RUNTIME APPROACH

Predictable responsibilities

Conditions are intended to remain explicit and scoped so the system avoids broad expensive polling patterns.

BEST FIT

Where it makes sense

Servers that want consistent context interactions across jobs and world systems.

TECHNICAL CONTEXT

Read the contract before deployment.

Purchase and delivery will be enabled when the resource is ready. Documentation covers dependencies, installation, configuration, APIs and troubleshooting.

Open documentationSupport
PRODUCT DETAILS

Notwen Interactions

Context interaction layer for world objects, entities, zones and action menus.

WHAT IT INCLUDES

Core capabilities

  • Entity/world actions
  • Context menus
  • Conditional actions
  • Reusable registration API
  • Theme consistency
  • Bridge friendly permission checks
WHERE IT FITS

Typical use cases

  • NPC interactions
  • Doors/world actions
  • Vehicle actions
  • Job interactions
FRAMEWORK MODEL

Own the domain, bridge the server.

Standalone interaction layer with adapters/hooks for ESX, QBCore, Qbox or custom permissions/job state.

PERFORMANCE APPROACH

Predictable runtime behavior.

Conditions are intended to remain explicit and scoped so the system avoids broad expensive polling patterns.

BEST FOR

Where this resource makes sense.

Servers that want one interaction language across world systems and jobs.