# Changelog

> **Files Changed**
>
> Not every update requires replacing the entire folder, as we understand it’s a hassle to redo configs for each update.

* **All Files:** Delete the old `cd_doorlock` folder, download the latest version, reconfigure the configs folder, and restart your server.
* **All Files Except config.lua:** Follow the steps above, but first back up your existing `config.lua` file. After downloading, replace the new `config.lua` with your backup.
* **Specific Files:** Simply copy and paste the specific updated files over the old ones, then restart your server.

{% hint style="danger" %}

#### **Skipping Updates**

If you’ve skipped previous updates, it’s best to update all files to ensure compatibility. For example, if you're on v4.0.1, skipped v4.0.2, and now want to update to v4.0.3, use the "All Files" method for safety.
{% endhint %}

***

{% hint style="danger" %}

#### Important Notice (cd\_bridge dependency)

`cd_eventcalendar` requires `cd_bridge` to function, ensuring better compatibility and easier future updates.
{% endhint %}

***

#### v1.0.1

18/2/2026 *(dd/mm/yyyy)*

**Files Changed:** 

* [ ] All Files
* [ ] All Files Except config.lua
* [x] Specific Files

```
fxmanifest.lua
client/client.lua
server/server.lua
html (FULL FOLDER)
```

**Changelog:**

{% hint style="warning" %}
**Fixes**

* Fixed error when updating gift packs.
* Optimised confetti for claiming rewards.
* Image fallback now displays properly in every interface.
  {% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.codesign.pro/paid-scripts/event-calendar/changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.