Skip to content

Bridges to connect scripts from another ecosystem

Fivemon is committed to maintaining high compatibility with existing FiveM ecosystem scripts, ensuring that using our base does not limit server owners. On the contrary, our goal is to enhance what’s already possible by allowing seamless integration with all the systems we provide — including NPCs, missions, and logic through .uri.

To achieve this, we’ve created a system of Bridges, which serve as compatibility layers between our base and widely used frameworks.

What Are Bridges?

A bridge is a module that replicates the external interface and data behavior of another framework or inventory system, allowing scripts designed for those systems to work within the Fivemon base.

These bridges do not merely imitate functions — they aim to mirror the complete functional API of the original system, including:

  • Exports
  • Events
  • Data loading (e.g. items, jobs, shops)
  • Database structure replication (when necessary)

This allows existing scripts to be dropped into a Fivemon-based server with minimal or no modification.

Currently Supported Bridges

We currently maintain two major bridges:

1. es_extended (ESX Compatibility)

Implements the full es_extended interface, including:

  • Client and server exports
  • Items and jobs importing from database
  • Events
  • users table replicated in database

You can refer to the original documentation to use compatible scripts:

➡️ ESX documentation

2. ox_inventory

Implements the ox_inventory API, including:

  • Client and server exports
  • Content support for items, animations, shops, crafting and stashes
  • Some events
  • Not including hooks

You can refer to the original documentation here:

➡️ https://overextended.dev/ox_inventory

Compatibility Scope

Our bridges are designed to work for 99% of standard use cases, but it’s important to understand the limitations:

  • We do not guarantee full compatibility in every possible case.
  • The original frameworks have many edge cases and inconsistent behaviors that may not be fully mirrored.
  • Timing, event order, or rare side effects might cause unexpected issues in certain scripts.

We recommend always testing thoroughly before deploying any third-party script in a production environment.

If you encounter a compatibility issue or error, please report the specific case so we can evaluate and resolve it.

Notes and Best Practices

  • The bridges are not intended to replace official frameworks. They allow compatibility, but do not guarantee future-proofing for scripts updated outside our ecosystem.
  • Follow the original framework’s documentation when using third-party scripts.
  • Keep an eye on our changelog and announcements to stay informed about current compatibility status and updates.