XTech Lite — In-World Edition

XTech Lite runs a tip jar venue entirely in-world: no web account, no server to host, no database. You configure everything with three notecards and rez it. Staff log in, visitors tip, tips split and pay out on the spot, and the stream follows whoever is on the decks — all without ever touching the web.

Which edition do I want? If you want dashboards, stats, events, notice bots, and cross-venue staff — that's the full XTech Venue System. If you just want a solid, self-contained tip jar you set up once and forget, Lite is for you. You can upgrade to full later without losing your setup.

What you get (and what you don't)

Works in Lite Staff login & job picker · instant tip splits & payouts · personal vs venue stream switching · up-next / take-over at the booth · manager kick · a running tip total on the server · auto-logout · group-only tipping.
Not in Lite The web dashboard · saved tip history, stats & leaderboards · events & reminders · the notice bot (group notices, greets, FAQ) · Discord/Telegram alerts · profile-picture display on jars · fundraisers · web-controlled add-ons (the quiz needs the web; OmniDisplay is standalone and works fine alongside Lite).

In short: the money and the room run exactly like the full system; what you give up is everything that lives on the web — history, dashboards and automation.

Your notecards are yours to edit. The Lite server prim is modify, so you can open its Content and change your config, jobs and managers any time — no web panel needed. (The scripts inside are locked, as with any product; only your notecards are editable.)

Setup — about five minutes

  1. Rez the XTech Lite Server at your venue. Somewhere out of the way is fine — a back room or skybox corner. It must stay rezzed: it's the brain that runs your jars.
  2. Create three notecards inside the server. Edit the server → Content → New Notecard, and name them exactly: XTech Config, Job: DJ (one card per job), and Managers. Paste the templates from the next section and save. The server reloads itself whenever you edit a notecard.
  3. Rez a tip jar within 20m and touch it (as owner). It pairs to the server automatically. Move it wherever you like afterwards.

That's it. Staff touch the jar to log in; visitors use the Pay button to tip.

The three notecards

All configuration lives in notecards you can edit any time. Lines beginning with # or ; are ignored; key = value for settings.

XTech Config — venue settings

# XTech Lite — venue settings
version       = 1
longName      = The Blue Room
loginMode     = list            ; list = only people in the Job cards | open = anyone, any job
defaultStream = http://stream.example/blue
clubStream    = http://stream.example/blue
amountA = 50
amountB = 100
amountC = 250
amountD = 500
splitUUID     =                 ; who gets the venue's cut (blank = DJ keeps 100%)
splitPercent  = 0
jarText       = <name>'s Tips
hoverText     =
thankText     = Thank you <name>!
thankMode     = say             ; say | im
autoLogout    = 3600
logoutRange   = 30
requireGroup  = 0

Templates written with <name> are filled in with the DJ's name (<names> = possessive; <amount> in the thank-you = the tip).

Job: <name> — one card per job, and its roster

The card name after Job: is the job label shown in-world — nothing is hardcoded, so name your jobs whatever you like (DJ, Host, Greeter…). Each line inside is one authorised person: name, uuid, stream.

# Job: DJ
# Optional per-job overrides (blank = use XTech Config):
split   = 20                    ; % of each tip to the venue cut for THIS job
amounts = 50,100,250,500        ; this job's four tip buttons
#   name,            uuid,                                  stream
Xevian,  b1a2c3d4-1111-2222-3333-444455556666, http://stream.example/xevian
DJ Nova, a7b8c9d0-1111-2222-3333-444455556666, http://ice.example/nova
  • name — the DJ/host name shown on the jar.
  • uuid — the avatar allowed to log in as this job (their key).
  • stream — their personal stream. Present → the venue music switches to it when they log in, and they can toggle between it and the venue stream. Blank → no stream change (perfect for a Host).
Keep it simple. You can put everyone in a single card (e.g. Job: Staff) and just give the DJs a stream and the hosts a blank one. Someone listed in several Job cards gets a small role picker; one job = straight in (see below).

Managers — booth control without the owner online

One avatar UUID per line. Anyone listed — plus you, the owner, always — can kick the current DJ and take over a busy booth. Leave the card empty (or delete it) for none.

# Managers — one UUID per line
b1a2c3d4-1111-2222-3333-444455556666

Day to day

Logging in

A staff member touches the jar. If they hold one role they're logged straight in; if they hold several, they pick. Unknown avatars are turned away in list mode, or may pick any job in open mode. Managers touching a busy jar get a Kick option; anyone else is queued as up next and takes over when the booth frees.

Tipping & payouts

Visitors use the jar's Pay button (buttons come from your amounts). The tip is split and paid out instantly in-world — the DJ gets their share and, if you set a splitUUID + splitPercent, the venue gets its cut. Set requireGroup = 1 to accept tips/logins from your venue group only.

Streams

If a DJ has a personal stream, logging in switches the parcel music to it, and their jar menu offers a My Stream / Venue Stream toggle plus Fix Stream to re-assert it. When they log out (with nobody queued) the music returns to your defaultStream. On group-deeded or split land the server can't set the music directly — use a StreamSwapper, exactly as in the full system (server menu → Spawn Swapper). See In-World → StreamSwapper.

Touch the server (as owner or a manager) for:

Tips since resetShown right in the menu title — the running total the server has taken in. (Owner)
Reset TotalZeroes that running total. (Owner)
Set StreamManually set the parcel music URL. (Manager)
ResyncRe-read the notecards immediately. (Manager)
Spawn SwapperRez & pair a StreamSwapper for deeded land. (Owner)
No off-object record. The tip total is the only number the server keeps, and it lives on the object. There's no saved per-tip history in Lite — if you want that, you want the full edition.

Living with it

  • Keep the server rezzed. It runs the jars; take it down and the jars have nothing to talk to.
  • Edit a notecard, and it reloads automatically — no reset needed. Or use the server menu's Resync.
  • Re-rezzing or moving the server is fine. It remembers its venue, and your paired jars re-attach to it automatically.
  • One server per venue. If you accidentally rez a second copy, the older one bows out on its own. To run a genuinely separate venue, hard-reset the copy first (press and hold the server) so it becomes its own venue.
  • Handing the venue to someone else? When the server changes owner it wipes itself clean and reloads from its notecards for the new owner.

Upgrading to the full system

Your jars are the same jars the full system uses, so moving up is straightforward and you don't lose your setup:

  1. Set up your venue on the web with the XTech Venue Setup prim (which can seed the new venue from your Lite notecards).
  2. Swap the Lite server for the full XTech Server at the venue and let it bind.
  3. Touch each jar once to re-pair it to the new server. With only the new server present, each jar re-attaches on a single touch.
Why the re-pair? Going full gives the venue a new identity on the web, so the jars need one nudge to follow. A quick touch each and you're done.

Troubleshooting

Nobody can log in No Job: cards, or the person's UUID isn't listed in one (and loginMode = list). Check the card names start exactly with Job: and the UUIDs are right. The server IMs a warning if it finds no job cards.
A jar won't pair Rez it within 20m of the server and touch it as the owner. Both must be owned by the same account.
Stream won't change On group/other-owned land the server can't set music directly — spawn a StreamSwapper (server menu) and deed it to the land group.
Edited a notecard but nothing changed Save the notecard (it reloads on save); if in doubt, use the server menu → Resync. Jars pull fresh settings on the next reload.
Server totally stuck Owner: press and hold the server for a few seconds to hard-reset it, then it reloads from the notecards.