# _eh Rezzer Payload Templates

Use these payload formats when sending JSON to _eh after rez.

## Channel Behavior

The _eh script listens on the integer value stored in object description after rez.

Typical rez flow:
1. Generate a private negative channel for this session.
2. Rez _eh with start parameter equal to that channel.
3. Send one JSON payload to that channel with command and fields.

## Outgoing Payload

```json
{
  "command": "outgoing",
  "address": "ATL-CTRL",
  "destination": "Atlantis Command",
  "grid": "pegasus.example:8002",
  "cords": "<128.0,64.0,25.0>",
  "rot": "<0.0,0.0,0.0>",
  "size": 4.5,
  "unstable": 0,
  "iris": 0,
  "remote_iris": 0
}
```

## Incoming Payload

```json
{
  "command": "incoming",
  "address": "MIDWAY",
  "destination": "Midway Relay",
  "grid": "pegasus.example:8002",
  "size": 4.5,
  "unstable": 0,
  "iris": 0,
  "remote_iris": 0
}
```

## Close Payload

```json
{
  "command": "close"
}
```

## Failure or Interference Visual

If you want a rough unstable visual for roleplay events, use unstable 1:

```json
{
  "command": "outgoing",
  "address": "UNKNOWN",
  "destination": "",
  "grid": "",
  "cords": "<0.0,0.0,0.0>",
  "rot": "<0.0,0.0,0.0>",
  "size": 4.5,
  "unstable": 1,
  "iris": 0,
  "remote_iris": 0
}
```

## Field Notes

1. destination should be a simulator/region name for OpenSim teleport targets.
2. cords and rot are vectors encoded as strings because _eh parses them from JSON string values.
3. remote_iris should be set by your destination gate authorization state.
4. address and grid are optional but recommended for status display and logging context.