> For the complete documentation index, see [llms.txt](https://bit.lockyzdev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bit.lockyzdev.com/docs/2024.1/updating.md).

# Updating

{% hint style="warning" %}
This version of Bit will enter End of Support the 23rd of April 2025.

This means it will only receive major bug fixing and security updates!
{% endhint %}

### Bit 5.2 to Bit 2024.1

#### Things to remember

* Make sure ALL plugins are updated to 2024.1
  * Bit 2024.1 makes MAJOR changes to the bots command handler. Things WILL break
* Make sure to delete all the Bit and Bit Core files. This means EVERYTHING bar the /plugins folder and then everything inside the /plugins/bit-core folder!

#### Updating config.json

All config options are in snake case now. Please see the example below!

The config now requires a guild\_only, language and dev\_only field, you can follow the format below (using their default values)

```
"guildOnly": false,
"language": "en",
"devmode": false
```

Currently, language can only be "en".

Example

```json
{
    "embed_colours": {
        "positive": "#00FF1C",
        "negative": "#FF0000",
        "neutral": "#9013FE",
        "main": "#86C1FD",
        "secondary": "#50E3C2"
    },
    "botIDs": {
        "logs": "LOGGING ID",
        "guild": "GUILD ID",
        "client": "CLIENT/APPLICATION ID",
        "owner": "OWNER ID"
    },
    "activities": {
        "type": "custom, playing, listening or watching",
        "state": "The text that displays as the status",
        "status": "online, idle, invisible or dnd"
    },
    "guildOnly": false,
    "language": "en",
    "devmode": false,
    "token": "BOT TOKEN"
}
```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://bit.lockyzdev.com/docs/2024.1/updating.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
