📥Bundle Metadata

Metadata attached to every bundle item generated by the script.

This section is for developers who want to read, log, modify, or integrate bundle data with other systems (economy, black market, logs, etc.).

Each bundle contains a structured metadata table when created.

---

📦 Bundle Metadata Structure

When a bundle is generated (register, chest, bag, safe), it includes this table:

{
  rid = "robbery-unique-id",
  serial = "unique-bundle-id",
  source = "register",   -- register, bag, chest, safe, etc.
  size = "M",            -- S / M / L
  worth = 750,           -- payout value
  created = 1710000000,  -- unix timestamp
  expires = 1710180000   -- unix timestamp
}

---

🔎 Field Reference

Field	Description
rid	Unique robbery identifier
serial	Unique bundle UUID
source	Loot source type (register, bag, chest, etc.)
size	Bundle tier (S, M, L)
worth	Value defined by BundleTables
created	Timestamp bundle was created
expires	Timestamp bundle expires
metadata	Used internally for TTL and cleanup

---

🧪 Example (Register Bundle)

local info = {
  rid = "r32f91",
  serial = "uuid-7781-xyz",
  source = "register",
  size = "S",
  worth = 340,
  created = 1709900000,
  expires = 1710080000
}

---

🧰 Developer Usage Examples

✔ Read bundle metadata (QB/OX)

local metadata = item.metadata
print(metadata.worth)

✔ Extend bundle value (custom economy)

metadata.worth = metadata.worth * 1.10 -- 10% bonus

✔ Check expiry

if os.time() > metadata.expires then
    -- expired
end

✔ Add custom fields (safe)

metadata.customTag = "gang-reward"

---

📝 Notes

• Expiry & cleanup are handled automatically by the script.

• Modifying metadata won't break the script as long as required keys remain.

• Use bundle metadata for logging, rewards, discord webhooks, reputation systems, etc.