> For the complete documentation index, see [llms.txt](https://devix.gitbook.io/devix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devix.gitbook.io/devix/devix-core/getobjects.md).

# getObjects

**Side:** Server & Client\
**Source:** [devix-core (GitBook)](https://devix.gitbook.io/devix/devix-core)

## What it does

The devix-core export. Returns the `DEVIX` table; all API functions are called on this table.

## How to use

Call it once at script start, then use `DEVIX.FunctionName(...)`.

{% code title="example.lua" %}

```lua
local DEVIX = exports['devix-core']:getObjects()

-- Server example
local player = DEVIX.GetPlayer(source)
local citizenid = DEVIX.GetPlayerIdentifier(player)

-- Client example
local jobName = DEVIX.GetPlayerJobName_CL()
DEVIX.Notify('Hello', 'inform')
```

{% endcode %}

## Parameters

None.

## Returns

* **table** — The DEVIX table (GetPlayer, AddItem, Notify, Framework, etc.).

{% hint style="info" %}

* The same export exists on server and client; the returned table exposes different functions per side.
* Every other function in the docs is accessed through this table.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://devix.gitbook.io/devix/devix-core/getobjects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.