> For the complete documentation index, see [llms.txt](https://lng.gitbook.io/lng-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lng.gitbook.io/lng-docs/zenith-drops/readme.md).
# Welcome to Zenith Drops
Welcome to the official documentation for Zenith Drops.
Zenith Drops is an advanced, server-sided event framework that completely overhauls how loot is distributed. Instead of relying solely on static map spawns, this system allows you to create highly customized loot drops, live entity spawns, and deadly trap events triggered dynamically by AI deaths (Infected and Animals).
Unlike standard DayZ loot tables, Zenith allows you to build complex rules based on location, the player's weapon type, killstreaks, and even their Expansion Hardline reputation.
***
### ✨ Core Features
* 🎯 Precision Targeting: Target specific zombie/animal variants, or use base classes to target entire groups (e.g., `AnimalBase` or `ZmbM_SoldierNormal`).
* 🗺️ Zonal Restrictions: Restrict drops to specific XYZ coordinates with a defined radius, or set the radius to `0.0` for a global map-wide rule.
* 🎲 Double-RNG System: Roll a master probability for the event to happen, and then roll individual probabilities for every single item inside the drop container.
* 🧘 The "Docile" Mechanic: Spawn live AI as drops that act completely docile. They will ignore players entirely until they are attacked—perfect for surprise encounters!
* 🎆 Loot Beacons: Automatically spawn an active colored smoke grenade, chemlight, or flare directly on top of successful loot drops to create an unmissable "Loot Pillar."
* 📢 Custom UI Notifications: Broadcast beautiful custom UI pop-ups to the killer or the entire server when a boss is defeated *(Requires Community Framework)*.
* 📈 Progression Mechanics: Require a specific killstreak before an item drops, and utilize a built-in "Pity System" that incrementally increases the player's drop chance every time they fail a roll.
* 🧹 Smart Garbage Collection: Built-in deletion timers safely clean up empty bags, full bags, and their visual beacons to protect server FPS.
***
### ⚙️ How The `ResultType` Engine Works
You are not limited to just dropping loot bags. The `ResultType` variable dictates the entire outcome of the event:
1. `ITEM`: Spawns the container defined in `ContainerClass` (like a Sea Chest or the custom Zenith Bag) and fills it based on your `LootPayload` probabilities.
2. `ENTITY`: Instantly spawns a live creature (defined in `SpawnEntityClass`). Combine this with `AggroKiller` to decide if it spawns angry or docile.
3. `TRAP`: Spawns and unpins the live grenade classname defined in `TrapClass`. *(Tip: Set `SpawnOnPlayer: 1` to drop a live POX vial directly at the player's feet instead of on the zombie corpse!)*
***
1. Navigate to `$profile:LNGStudio/ZenithDrops/admins.txt`
2. Add your Steam64 ID to the file (one ID per line) and save it.
3. In-game, press `Ctrl + Z` (default keybind, rebindable in your DayZ settings under the LNG Studio tab).
The server will dynamically read your updated JSON rules and immediately apply them to the live environment.
***
### Jump right in
---
# 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://lng.gitbook.io/lng-docs/zenith-drops/readme.md?ask=&goal=
```
`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.