#Daphne Core - Framework Bridge

1 messages · Page 1 of 1 (latest)

river forge
#

Daphne Core - Framework Bridge

A flexible, high-performance framework bridge system for FiveM that uses the Adapter Design Pattern to support multiple frameworks seamlessly. Built with performance in mind, following the 0.00ms policy and utilizing FiveM's Lua 5.4 state bag mechanism.

Features

  • Adapter Pattern Architecture: Easily extensible to support multiple frameworks
  • State Bag Integration: Leverages FiveM's Lua 5.4 state bag mechanism for efficient data synchronization
  • Performance Optimized: Batch updates, throttling, and change detection for minimal CPU usage
  • Framework Agnostic: Clean abstraction layer that works with any supported framework
  • Currently Supports: Qbox/QBCore, ESX frameworks
  • Future Ready: Easy to add support for ESX, OX Core, and other frameworks

See daphne-core repository for more details.

GitHub

A flexible, high-performance framework bridge system for FiveM that uses the Adapter Design Pattern to support multiple frameworks seamlessly. - daphne-studio/daphne-core

honest quartz
#

So i can use nd_mdt white qbox instead of nd core?

river forge
#

you can try, i'll wait your results

cedar tinsel
river forge
#

if you want to use nd mdt without nd core, you must update nd mdt’s nd core references to the daphne core exports

#

it will be probably working

coarse spire
#

esx,nd, qbcore in qbox? 😮