<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Active framework adapter
    |--------------------------------------------------------------------------
    |
    | Which FiveM framework convention the App\FiveM\Adapters layer should
    | target. One of: "qbcore", "esx", "qbox". See docs/database-analysis.md
    | for the table/column assumptions each adapter makes.
    |
    */
    'framework' => env('FIVEM_FRAMEWORK', 'qbcore'),

    /*
    |--------------------------------------------------------------------------
    | Database connection
    |--------------------------------------------------------------------------
    |
    | The Eloquent connection name (see config/database.php) that points at
    | the live FiveM server's oxmysql database.
    |
    */
    'connection' => 'fivem',

    /*
    |--------------------------------------------------------------------------
    | Table names per framework
    |--------------------------------------------------------------------------
    |
    | Server owners with non-default table names can override these without
    | touching any model or controller code.
    |
    */
    'tables' => [
        'qbcore' => [
            'players' => 'players',
            'vehicles' => 'player_vehicles',
            'houses' => 'player_houses',
            'gangs' => 'gangs',
            'jobs' => 'jobs',
        ],
        'qbox' => [
            'players' => 'players',
            'vehicles' => 'player_vehicles',
            'houses' => 'player_houses',
            'gangs' => 'gangs',
            'jobs' => 'jobs',
        ],
        'esx' => [
            'players' => 'users',
            'vehicles' => 'owned_vehicles',
            'houses' => 'properties',
            'gangs' => 'jobs', // ESX has no native gang concept; maps to a job entry.
            'jobs' => 'jobs',
        ],
    ],

    /*
    |--------------------------------------------------------------------------
    | UCP-owned tables on the fivem connection
    |--------------------------------------------------------------------------
    |
    | Bans/warnings aren't shipped by any of the three frameworks, but they
    | need to live next to player data so FiveM Lua resources can read them
    | directly via oxmysql without round-tripping through this app's API.
    | Migrations for these two tables run against the `fivem` connection.
    |
    */
    'ucp_tables' => [
        'bans' => 'ucp_bans',
        'warnings' => 'ucp_warnings',
    ],

];
