Placeholder files and Config "enum" like changes

[adweex]

Description

Created the shared and modules folder as placeholder. Also changes to the config based on previous conversations.
#23

Checklist

• I have personally loaded this code into an updated Qbox project and checked all of its functionality.
• My code fits the style guidelines.
• My PR fits the contribution guidelines.

[Manason]

What modules do you plan to provide for vehicle keys?

[adweex]

What modules do you plan to provide for vehicle keys?

Truth is i have no idea. You said this in the previous pull request.

" Consider further modifications to config similar to qbx_core:
Split into client, server, and shared files
Make into modules"

Still trying to decode that. These modules are new to me :D

[Manason]

What modules do you plan to provide for vehicle keys?

Truth is i have no idea. You said this in the previous pull request.

" Consider further modifications to config similar to qbx_core: Split into client, server, and shared files Make into modules"

Still trying to decode that. These modules are new to me :D

Oh. Take a look at the qbx_core/config folder and copy the way core does configs. You can delete the modules/ folder

[adweex]

What modules do you plan to provide for vehicle keys?

Truth is i have no idea. You said this in the previous pull request.
" Consider further modifications to config similar to qbx_core: Split into client, server, and shared files Make into modules"
Still trying to decode that. These modules are new to me :D

Oh. Take a look at the qbx_core/config folder and copy the way core does configs. You can delete the modules/ folder

Oh. I see. So you sort the configs to client only, server only and shared config values. That's sort of new. I've seen this return {} config thingy on ox scripts, so qbx implemented these as well. How do i refer to these config values? So it's not Config.x anymore.

Like this?
local config = require 'config.client'

[Manason]

What modules do you plan to provide for vehicle keys?

Truth is i have no idea. You said this in the previous pull request.
" Consider further modifications to config similar to qbx_core: Split into client, server, and shared files Make into modules"
Still trying to decode that. These modules are new to me :D

Oh. Take a look at the qbx_core/config folder and copy the way core does configs. You can delete the modules/ folder

Oh. I see. So you sort the configs to client only, server only and shared config values. That's sort of new. I've seen this return {} config thingy on ox scripts, so qbx implemented these as well. How do i refer to these config values? So it's not Config.x anymore.

Like this? local config = require 'config.client'

Yep