Nasdara rental presets are pending verified mission data; do not use another map’s preset as a substitute. Map coverage →

Free tools · No sign-in required

Build your shop’s
next rental.

Create DayZ event entries for vehicle deliveries or dynamic gas-event requests. Paste coordinates from your server’s Discord bot, generate XML, and prepare a shop message.

File generator, with operator fulfillment.

This tool does not connect to Discord, fetch player coordinates, link game accounts, charge currency, or deploy to your server. Your existing bot/operator handles those steps. Event lifetime is a Central Economy setting, not a guaranteed rental-expiry timer. An active event may replenish or repeat until disabled.

1. Shop request

The price and rental term describe your shop offer; they do not charge a player or set a vehicle deletion time.

Reference vehicle parts apply by classname to all spawns of that variant, not just this rental. Fuel, fluids and final vehicle condition are not guaranteed. No modded vehicles are included.

2. Delivery coordinates

Three-number vectors are read as X Y Z; elevation Y is ignored for CE event positions. Coordinates are range-checked only. Check roads, terrain, water, buildings and players yourself.

3. Event behavior

Default is inactive for staging. Enable only when ready to fulfill a request. Removing the event stops future scheduling but may not remove an already spawned vehicle.

Advanced Central Economy settings
Loading reference catalogue…
Matching event ID

Enter coordinates to generate

Snippet downloads contain only this request. Do not replace your full server files with snippets. Use the merge tool below or append the entries manually.

Optional vehicle parts

Discord shop / order message

Copy this into your shop or ticket. It is a message template, not an executable bot command or bot-specific shop import.

Merge into your current server files

Your uploaded files stay in this browser. Existing events and positions are preserved; duplicate event names are rejected. Both files must merge successfully before downloads are offered.

Operator workflow · Console & PC

From shop order to server event

  1. Have the player use your existing server bot’s account-link and coordinate commands. Confirm their linked player, map, order, price, location and server rules. This site does not verify those details.
  2. Generate a unique request ID. Stage the event inactive, then activate when your operator is ready to fulfill it. CE availability and safe-radius rules affect spawn timing.
  3. Stop the server and back up db/events.xml and cfgeventspawns.xml. Merge this request into both current files using the tool, or paste matching event entries inside their existing root elements.
  4. Optional: replace the matching vehicle type entry in cfgspawnabletypes.xml with the parts snippet. Do not duplicate it or replace the whole file. This affects every spawn of that vehicle variant.
  5. Upload the reviewed merged files to the active mission folders through your host’s file browser/API, then restart as required by your host. Test on a staging server first.
  6. For a single delivery, have the operator/bot disable or remove the request event and its position after fulfillment. A live CE event can replenish. At rental expiry, the operator/bot must perform the required vehicle cleanup separately.

No production bot is connected. Automated purchases, coordinate lookup, secure server uploads, timing and cleanup require a separately configured bot with authorized server access. Never paste bot tokens or hosting credentials into this generator.

Reference: Bohemia’s official event, position and vehicle attachment files; dynamic contaminated areas. Checked October 9, 2026. XML format checks do not verify live game behavior.