# Core concepts

`qb-core` initializes the framework object, shared definitions, client/server functions, player
state, commands, events, and its built-in DrawText NUI. Treat each API as commit-specific.

## Start here

- [Core object](/docs/core/core-object) — request the whole object or selected sections
- [Player data](/docs/core/player-data) — character state exposed by the framework
- [Functions](/docs/core/functions) — client and server helper map
- [Events](/docs/core/events) — lifecycle and update signals
- [Shared data](/docs/core/shared) — items, jobs, gangs, vehicles, weapons, and locations
- [Shared mutation exports](/docs/core/shared-exports) — server-side runtime additions and updates
- [DrawText helpers](/docs/core/drawtext) — core NUI text exports and events

## Integration boundary

Acquire the object through the `qb-core` export and request only the sections your resource uses:

```lua
local QBCore = exports['qb-core']:GetCoreObject({ 'Functions', 'Shared' })
```

Verify function and event behavior in the current
[qb-core source](https://github.com/qbcore-fivem/qb-core). A client event is a request, not an
authorization boundary; validate identity, permission, state, proximity, and values on the server.
