Update readme.md

This commit is contained in:
Remco Epicnabbo
2026-05-18 21:13:58 +02:00
parent cf3897f09e
commit 82a34d83ad
+10 -1
View File
@@ -9,7 +9,7 @@ EpicNabbo Catalogue v2 is a heavily optimized evolution of our catalog system, s
## 🚀 Key Improvements & Objectives ## 🚀 Key Improvements & Objectives
* **Massive 52k+ Furni Database:** An increase of over 21,000 items compared to the internal v1 target, optimized for high-performance indexing. * **Massive 52k+ Furni Database:** An increase of over 21,000 items compared to the internal v1 prototype, optimized for high-performance indexing.
* **Native Nitro v3 Support:** Tailored to support all modern Nitro UI elements and packet structures. * **Native Nitro v3 Support:** Tailored to support all modern Nitro UI elements and packet structures.
* **High Quality Standards:** Re-engineered framework to eliminate the performance bottlenecks found during internal testing of the previous unreleased version. * **High Quality Standards:** Re-engineered framework to eliminate the performance bottlenecks found during internal testing of the previous unreleased version.
* **100% Verified Layout:** Merging development data into a superior base ensures zero missing pages or broken assets. * **100% Verified Layout:** Merging development data into a superior base ensures zero missing pages or broken assets.
@@ -40,6 +40,15 @@ Please be aware that this framework currently has an **enormous amount of bugs**
--- ---
## ✨ Planned Nitro v3 Features
Once the stability phase is complete, this catalog will fully support:
* **Advanced Catalog Page Layouts:** Native rendering of all specialized Nitro UI tabs and styles.
* **Dynamic Search & Caching:** Fast indexing to handle the 52k+ items without delaying packet responses.
* **Front-end JSON Hooks:** Ready-to-go configurations for your Nitro client assets.
---
## ⚙️ Technical Requirements ## ⚙️ Technical Requirements
To handle the 52k+ item dataset, ensure your database configuration is optimized. You **must** increase the packet size in your `my.ini` or `my.cnf` before importing: To handle the 52k+ item dataset, ensure your database configuration is optimized. You **must** increase the packet size in your `my.ini` or `my.cnf` before importing: