Gaming PCs (ggLeap)

Selling passes and seeing the PCs from the till, so the day-to-day stops needing the ggLeap admin site at all.

How do I sell ggLeap passes from the till?

Game passes go on the menu like anything else, except CoinOp fills them in from ggLeap's own catalogue rather than you retyping them. When the sale is paid the pass goes onto the customer's ggLeap account; if the line is voided, the pass comes back off.

What this is for

ggLeap runs the gaming PCs: the accounts, the time on them, what a machine will let somebody do. CoinOp runs the money: the sale, the tax invoice, the drawer, the Z report. Without the two connected, selling an hour of PC time is the same job done twice — rung up on the till, then typed again into the ggLeap admin site, with a customer standing there while somebody finds the right window.

Connected, it is one action at the till. The customer pays, the pass lands on their account before they have walked back to the machine, and the sale is in your books like any other.

What this means day to day: once it is set up, nobody opens admin.ggleap.com during service. Selling passes, finding customers, seeing which PCs are free, refunding a pass and checking that one arrived are all here. The admin site is for two things after that: making a new kind of pass, and issuing the API token below.

Connecting it, once

Settings → ggLeap → Connection

The ggLeap connection panel: an API token box, the environment, and a test that reports what it can see — The token comes from admin.ggleap.com → Settings → API. Paste it here and press Test: CoinOp reports what it can actually see through it — how many accounts, how many machines, how many passes — rather than a green tick that means the request did not error.

Granting is a separate switch from the token. A venue can connect, look at everything, and leave CoinOp unable to change anything on an account until they are ready. That is the setting to turn off first if you ever want to sell passes without them being delivered.

Passes

Straight from ggLeap’s own catalogue. Nothing is retyped, so there is no second price list to keep in step — and the page counts what is not on the till yet.

Settings → ggLeap → Game passes

Every pass in ggLeap, in one table, whether or not it is on your till yet. Press Refresh from ggLeap after making a new one there and it appears here.

The game passes table with each pass's time, price, restrictions and the till button it is sold as, and a dialog explaining exactly what one pass does — Each row is one pass: the time it carries, its price, the restrictions it was given, and the button it is sold as on the till. Putting a pass on the menu is one press — no price retyped, no second list to keep in step.

How it behaves is the part that saves the trips. A pass is not just a number of hours: it can expire at a fixed time, expire after a duration, work only on certain days, work only in certain zones, and start on first use or immediately. This screen reads all of that out of ggLeap and, underneath, shows exactly what CoinOp will send when the pass is bought — the same request, assembled the same way, so the screen cannot drift from what actually happens.

It also lists passes that exist in ggLeap and are on no button, because “I made a pass and cannot find it on the till” is precisely the question this page should answer.

The PCs

Settings → ggLeap → PCs

The PC map: zones drawn as boxes with each machine placed inside, showing free, in use and switched off — Zones come from ggLeap’s own groups; the names and the arrangement are yours, set here rather than in somebody else’s admin panel. Free, in use and switched-off-but-free are three different colours, because a machine nobody has turned on is sellable and needs somebody to walk over.

Drawn once, the map answers “what have you got free?” by pointing rather than by reading out a list — and it is the same picture the customer-facing screen can show.

Selling a pass

The whole job. The pass is rung up like any other item, CoinOp asks who it is for, and the customer is found by the machine they are already sitting at — no username, and no second system to type it into afterwards.

The moment this is built around: somebody is already playing and wants another hour. They do not know their username, and asking them to spell it at the counter is the slow way.

Ring the pass up like any other item — it is a button on the menu.
Pick the customer. Either search the name — the directory is kept locally, so it is instant and works with the internet down — or pick the PC they are sitting at, which shows who is logged into each machine and what is on screen.
Take the money the normal way: cash, card, split, whatever.

The register with a day pass and a cola on one bill, tagged to PC-07 and the account sitting at it — A pass and a cola on one bill, going to one account and one machine. The customer pays once and gets one receipt.

The pass is granted when the sale is finalised — not before, because nobody should get time they have not paid for. Passes are sent with the offer’s own settings, so a pass sold at the till behaves exactly like the same pass given out any other way.

Passes on a tab

A pass added to a tab reaches the account straight away, before anybody has paid — which is what a tab is for.

A pass rung up onto a tab is not paid for yet, which leaves a customer standing at a machine that will not let them in. Two things deal with that.

Whose pass is it. Sending a pass to a tab asks who it is for before it lands, rather than at the end when whoever settles the bill gets everything on it. A tab held for three people can carry a pass each, and each goes to the right account.

Settings → ggLeap → Connection

Granting before the bill is paid. Switched on, a pass reaches the account the moment it is named on the tab, and comes back off if the line is voided — with the reason your staff typed. Switched off, which is how it arrives, nothing is granted until the tab is settled.

It is a real decision rather than a convenience: on, a customer plays before the money is taken, and a tab that walks out has already had its passes. That suits a venue that runs tabs for regulars and does not suit one that does not, which is why CoinOp does not choose.

Making sure it arrived

Settings → ggLeap → Passes granted

The granted passes list: what has reached customers' accounts, what is waiting, and what failed — The one screen here that is a daily concern. A failure means somebody paid and did not get their pass, so it is counted, named and retryable rather than logged somewhere nobody looks.

A grant that cannot get through — the internet is down, ggLeap is having a bad morning — waits and goes when it can. CoinOp checks whether a pass already landed before retrying, so a request that timed out after ggLeap had already acted on it does not become two passes.

Refunds

Refunding a sale that included a pass offers to take the pass back off the account as part of the refund, and says what it is about to do before doing it. The money and the entitlement stay in step, which is the whole reason for connecting the two systems.

Food for somebody at a PC

A sale can carry a machine without carrying an account — somebody at PC-34 buying a burger and no game time. The order routes to the kitchen with the PC number on the ticket, so it reaches the right desk.

What still lives in the ggLeap admin

Being straight about it, since the difference matters when you are deciding whether staff need a login for it at all:

Creating a new kind of pass — its hours, price and rules are ggLeap’s. CoinOp reads them and sells them.
Accounts — customers register themselves; CoinOp finds them, it does not create them.
Which PCs are in which group, and the API token above.

Everything a night actually consists of — selling, finding, seeing, refunding, checking — is here.