Treasure Hunt
ZMG TreasureHunt Find a treasure map, follow the marked spot, survive the infected guarding it and unlock the chest with the key hidden in the map. A dynamic treasure hunt event for DayZ servers - no other mods required. How it works Treasure maps spawn as normal loot. Study the map (hold it in your hands). The treasure event starts, the map now shows a red cross and you receive an old key. Travel to the marked… (more)
ZMG TreasureHunt Find a treasure map, follow the marked spot, survive the infected guarding it and unlock the chest with the key hidden in the map. A dynamic treasure hunt event for DayZ servers - no other mods required. How it works Treasure maps spawn as normal loot. Study the map (hold it in your hands). The treasure event starts, the map now shows a red cross and you receive an old key. Travel to the marked location. Depending on the map you will find a stranded ship wreck, an abandoned subway car, a ruined wooden hut - or nothing at all, because the treasure is buried. For the last few metres the treasure detector helps: switch it on, hold it in your hands and follow the beeping as it gets faster. The distance in metres is shown on the display. Deal with the infected guarding the spot, unlock the chest with your key and loot it. Features Different event types: ship wrecks, abandoned subway cars on the railway, ruined houses, chests in existing map buildings and buried treasures you have to dig up with a shovel or pickaxe Locked treasure chest: every event has its own key, only the matching key opens the chest Treasure detector: beeps faster the closer you get to the chest and only works for the player who studied the map. Needs a 9V battery, the display lights up when switched on and you can raise it in first person like a GPS Infected guards: amount, radius and classes configurable per event type. They even spawn and walk on ship decks and inside buildings Loot pools: weighted loot with min/max items per chest and a max count per item Race mode (optional per map): all other players get a hint where the treasure is hidden. The player who studied the map has a head start 10 treasure maps for Chernarus included, each with its own location and its own map texture with a red cross Multiple events at once: different maps can run in parallel (configurable amount), but each map only once at a time and never two events at the same spot One active event per player: players can only follow one treasure trail at a time (configurable) Restart safe: if the server restarts during an event, the key turns back into an unread treasure map. Nothing is lost Server friendly: staggered clean-up, no global broadcasts, event objects are not persistent Fully configurable via JSON: every file contains notes explaining all settings Multilanguage: stringtable with 13 languages Detailed log: one log file per server session for easy troubleshooting Included assets Treasure map (retexturable via hidden selection "camo") 4 different keys Treasure chest (cannot be picked up) Treasure detector (GPS device with glowing display, 9V battery) Ruined wooden house Abandoned subway car with interior (fits the DayZ railway) Installation Load the mod on server and client like any other mod. Start the server once. All config files are created in profiles/ZMG_TreasureHunt/ Add the treasure maps and the detector to your types.xml (found in the Extras folder). Config files FileContent config.jsonruntime, number of simultaneous events, despawn, detector, debug, player messages Variants.jsonevent types: objects, chest spots, infected LootPools.jsonloot pools with weights and limits TreasureMaps_<map>.jsontreasure maps of a map: event type, key, loot pools, locations The default setup is made for Chernarus and uses vanilla items only. Other maps can be added with their own TreasureMaps_<mapname>.json. Modded items can of course be used a
Not analyzed yet
modperf has not read this mod's scripts, so there is no report and it is left out of any stack it appears in. 2 live servers in the crawl publish it.
The worker downloads the mod from the Workshop and reads its Enforce Script — nothing is executed. Usually a few minutes. This page then shows the report.