WARDENHUB BACK TO TOOLS ↗
DAYZ PLAYSTATION / NITRADO / FILE WORKSHOP

PRA TELEPORTER GENERATOR.

Build a single-direction Player Restricted Area teleporter using the supplied, successfully tested Nasdara structure. The generator validates its own output and creates the matching cfggameplay.json reference. It does not edit your server configuration.

REFERENCE STATUS: USER-VERIFIED EXAMPLE

The structure and defaults below match the successful Nasdara Trader-to-Base test you supplied. This is not a claim that every map or server version behaves identically.

01

TELEPORTER DETAILS

Give this PRA file a clear identity.

02

TRIGGER LOCATION

Where the player enters the restricted area. PRA order is X, Y / Height, Z.

Admin-log order is X, Z, Height. If copying an admin log manually, place its third value in Y / Height and its second value in Z. This form does not silently rearrange values.

03

SAFE DESTINATION

Where the player should arrive.

04

ADVANCED PRA SETTINGS

Defaults match your verified Nasdara test. Change only when you have a reason to test a different setup.

Using tested reference defaults: dimensions [2, 2, 2], rotation [90, 0, 0].

Complete the fields and generate your PRA file.

06

SERVER TEST CHECKLIST

Generation is not proof of live server behaviour. Verify the upload in-game.

  1. Upload the downloaded PRA JSON into the displayed folder under your active mission directory.
  2. Confirm the uploaded filename and folder exactly match the configuration reference.
  3. Add the reference to the existing playerRestrictedAreaFiles array in cfggameplay.json.
  4. Validate that the complete cfggameplay.json remains valid and that unrelated settings are unchanged.
  5. Restart the Nitrado PlayStation server.
  6. Test by entering the trigger location in-game.
  7. Confirm the player arrives at the configured safe position.
  8. Review the admin log and record whether the teleport succeeded.

If it fails, collect the generated PRA JSON, exact config entry, uploaded path, server version, map, admin-log position and relevant startup/RPT errors. Change one variable at a time. Do not randomly alter coordinates, dimensions, rotation or paths.

07

REFERENCE NOTES

What this milestone is and is not claiming.