SAN ANDREAS · CUSTOM ENGINE

Push MTA:SA beyond its original limits.

Neon is an experimental engine fork for larger worlds, higher limits, deeper GTA systems, custom models, story tools, and new Lua APIs. It also brings FiveM-style shared NPCs and traffic into MTA, powered by GTA:SA's original single-player AI.

Download for Windows See what Neon changes Explore synchronized AI

144documented API entries

122client entries

20server entries

2shared entries

SYSTEM MAP

What Neon changes under the hood

01

Synchronized NPCs & traffic

Server-owned peds and mission actors driven by GTA's native AI, with one simulator and multiplayer presentation.

02

PS2-style visuals

Selected SkyGFX color, blur, radiosity, depth-bias, and YCbCr effects integrated into the Neon client.

03

Neon client & servers

A GTA-style menu, live server discovery, favorites, artwork, localization, and an integrated join flow.

04

Story runtime

Native cutscenes, ped tasks, script cameras, mission audio and text, recorded cars, and co-op building blocks.

05

Custom vehicle audio

Resource-owned engine sound configurations, synchronized opt-in modes, lifecycle cleanup, and backfires.

06

Neon Identity

Optional verified Neon and Discord identities for server policy, Lua resources, and stronger bans.

07

Extended world

A 20 km world range, extended water and radar, a dynamic F11 map, and large city resources.

08

Native world packs

Server-delivered static worlds, strict auditing, one-shot authorization, native activation, and server isolation.

09

Custom models

Stable server model IDs mapped to local GTA slots, with native-parent fallback and resource cleanup.

10

Rendering & limits

Larger native pools, live renderer stats, distant lights, editable CULL zones, and marker diagnostics.

START WITH A REAL PATH

Explore the mission checkpoints.

Tagging Up Turf and Drive-Thru connect the reusable story primitives into substantial paths exercised in game. Nines and AK's maps the next mission graph but still has an incomplete end-to-end matrix. The runtime provides building blocks for multiplayer coordination, while several multi-client barriers still need dedicated validation.

See validated paths and open branches →

API GROUPS

Extended native radar3 entriesServer-authoritative models11 entriesRenderer and distant lights6 entriesNative CULL zones6 entriesMarker diagnostics2 entriesProcedural seabed3 entriesModel-native walking styles2 entriesSynchronized ambient pedestrians5 entriesResource-owned streaming leases2 entriesNative ped tasks and gang tags40 entriesNative story vehicle state6 entriesNative scene primitives3 entriesNative script camera14 entriesNative file cutscenes11 entriesNative mission and frontend audio6 entriesResource-owned vehicle audio4 entriesNative mission text7 entriesNative vehicle recordings5 entriesVerified Neon identity and bans6 entriesExisting API extensions2 entries

Compatibility: Do not assume Neon APIs or network extensions exist on an ordinary MTA installation. Servers using current Neon-only model, native-world, or task-presentation protocols must keep client and server packages on the same network epoch.