In-World Setup & Objects

Everything that rezzes: the venue server, tip jars, donation jars and the stream swapper — how to set them up the first time, and how they behave day to day.

What's in the box

Setup path

New to the system? Start with the XTech Venue Setup prim — it sorts out the one thing the system can't guess: who will own the venue on the web.

1. Rez XTech Venue Setup at the venue. It asks: "Will you own/manage this venue on the web (this account)?"
   • Yes — you own the venue and the objects. Carry on with step 2 below.
   • No — the objects live on a management/club account but someone else runs the venue. The prim records this account as the system owner and you hand it over — jump to split ownership.
2. Rez the XTech Server somewhere out of the way at your venue. A back room or skybox corner is fine — visitors never touch it. It needs to stay rezzed, so don't put it somewhere it will get returned.
3. Answer its dialogs. The server registers itself with the web, then works out which venue it belongs to:
   • If this parcel already matches one of your venues, it asks you to confirm.
   • If you have venues elsewhere, it shows a picker — choose one, or + New venue.
   • If you're brand new, it offers to create the venue right here, named after your parcel.
4. Open the setup link. When a new venue is created you're IM'd a one-time web link (valid ~15 minutes — just rez again if it expires). It signs you straight into your venue page: set a username and password, your default stream, and your tip split. That's the whole web setup.
5. Rez and pair a tip jar. Put a jar within 20 m of the server and touch it as the owner. It finds your server and pairs. Move it wherever you like afterwards.

Split ownership — venue owner ≠ object owner

Common with estate or management setups: a management account owns and hosts the objects, but a different person should own the venue on the web. The no-transfer server can't carry identity between accounts — the transferable XTech Venue Setup prim does it instead:

1. Management account: rez XTech Venue Setup at the venue and answer No when it asks whether you'll own the venue on the web (step 1 of the setup path). It records this account as the system owner and tells you to pass it on.
2. Transfer the prim to the venue owner. They rez it at the venue. It creates the venue under their name, hands them their one-time web setup link, and deletes itself.
3. Back on the management account: rez the XTech Server at the venue. It finds the freshly created venue waiting and binds to it. Pair jars as normal.

Living with the server

The server is deliberately boring once it's up. A few rules keep it that way:

• Keep it rezzed. It's the only object that talks to the web. Jars, swappers and donation jars all go quiet without it.
• Never deed it to a group. Deeding changes its owner and breaks its secure identity. If you need stream control on deeded land, that's exactly what the StreamSwapper is for.
• It should be no-modify and no-transfer. It checks this itself and warns on boot if something is off.
• Touch it (as owner or manager) for the admin menu — status, force a web retry, spawn a StreamSwapper, and other maintenance.
• Web outage? Relax. The server caches your venue config. Jars keep working, staff can still log in against the cache, and tips queue up and reconcile when the web comes back. Jars show a red OFFLINE note in their hover text while this is happening.
• Hard reset: if the server ever wedges completely, the owner can press and hold it to trigger a factory reset, then set up again. This is the recovery of last resort — you'll re-run the setup dialogs.

Tip jars

Pairing

Rez the jar within 20 m of your server and touch it as the jar's owner. It scans for servers you own, pairs to yours (it asks if there's more than one), and is ready. Pairing survives moving the jar, taking it to inventory and copies — each copy pairs itself on first touch.

Staff login

• A staff member touches the jar and gets a picker of the jobs they hold at your venue. They choose one and they're logged in — the jar renames itself, shows their profile, and their session starts.
• If someone is already on the jar, the toucher can queue as up next — the handoff is automatic when the current session ends.
• Logout is a touch away, and the jar also auto-logs-out a DJ who leaves the region (with a grace period, so a crash-and-relog doesn't lose the slot).
• Who may log in is governed by your venue's access settings and job assignments on the web — the jar just shows what the server allows.

Tipping

• Visitors Pay the jar and pick an amount (your venue's configured tiers, or a custom amount).
• The split happens instantly, in-world — the staff member and the house each get their share the moment the money lands. No waiting on the web.
• Every tip is also logged to the web for the tip history and dashboards. If the web is down, tips queue in the jar and are delivered when it's back — nothing is lost.
• Thank-you messages, hover text and jar naming are configured per-venue on the Manage Venue page.

Display plugins

The jar can drive extra prims in the same linkset: the GetProfilePic plugin shows the logged-in staffer's profile picture, and OmniDisplay shows event posters. Drop the plugin script into a face-sized prim, link it to the jar, done.

Streams — who controls the music

The server sets your parcel's music stream to follow the session:

Default and club streams are set on Manage Venue; each staffer manages their personal stream on My Profile.

StreamSwapper — deeded & group land

On group-deeded land, only group-owned objects may set the parcel music — and the server must never be deeded. The StreamSwapper is the safe middleman:

1. Spawn it from the server. Touch the server, choose Spawn Swapper. It rezzes a pre-paired swapper next to the server.
2. Move it onto the parcel that needs music control and deed it to the land group (About Land → the usual deed flow). Its floating text tells you what it needs until it's happy.
3. That's it. From now on the server broadcasts stream changes and the swapper applies them to its parcel. One venue can run several swappers across several parcels.

Donations & fundraisers

Donation jars are an optional, per-venue feature — completely separate from tips:

1. Enable donations on your server by adding the XTech Server Donations script to it (it ships alongside the server; drop it in the server's contents). Without it, donation jars pair but politely report that donations aren't enabled here.
2. Create a fundraiser on the web — the Fundraisers page: name, the recipient of the donations, goal, and the info shown to donors.
3. Rez the Donation Jar and pair it (owner touch, same as a tip jar). A manager then touches it and picks which fundraiser it runs — the same way a DJ picks a job.
4. Donors pay the jar. The donation splits between the fundraiser's recipient and the house cut you configured, progress is tracked on the web, and donors get an Info menu (website, about, optional freebie item).

Troubleshooting