Saltearse al contenido
Furbol — How It Works

Game Invitations

Esta página aún no está disponible en tu idioma.

Game Invitations

A game invitation is a direct nudge to another Furbol user asking them to join a specific game. Unlike placing, invitations don’t book the person for them — they get to decide.

When you’d use an invitation over a placement

  • If the person isn’t a follower of yours, you can’t place them. An invitation is the only way to reach them directly.
  • If you want them to decide for themselves (because of their own schedule, budget, or preference), an invitation leaves the call in their hands.
  • If you want to reach several people at once for the same game, invitations are the natural tool.

The three states of an invitation

  • Pending — sent but not responded to.
  • Accepted — the invitee took the spot and is now on the roster. An accept is effectively a booking; everything that applies to a normal booking applies here.
  • Declined — the invitee passed. Their seat doesn’t get held, and the host sees that they said no.

Who can invite

Who can send an invitation depends on the game’s visibility:

  • Public games. The host invites; players can also send nudge-invitations to other Furbol users. The invitation doesn’t grant access (the game is public already), it just brings it to their attention.
  • Private games. The host invites, and anyone already connected to the game — invitees (pending or accepted) and players the host placed onto the roster — can invite another Furbol user. That’s how the invitation chain grows past the host’s direct contacts.
  • Secret games. Same as private — the host plus anyone connected to the game can extend the chain. A secret game only becomes visible to someone the moment they’re invited (or placed). Each new invitee sees the game, which means they can invite in turn — the chain grows one hop at a time.

In private and secret games, the invitation is what grants access — so inviting someone really does open the game up to them.

How the chain actually reaches somebody the host doesn’t know

Worked example for a secret game:

  1. Host creates the game. Only the host sees it.
  2. Host invites A. A gets a push, sees the game, can accept/decline. A also now has the Invites tab unlocked for the game.
  3. A invites B. B gets a push from A (not the host), sees the game for the first time. B can accept/decline and now also has the Invites tab.
  4. B invites C. Same shape, one more hop.

Being placed onto the roster as a guest by the host works the same way for the placed person: the game becomes visible to them, and their Invites tab lights up so they can extend the chain.

A decline isn’t forever — they can be invited again

If someone you invite taps Decline, that closes your invitation to them — but it doesn’t mark them as off-limits for the game. Anyone else in the invitation chain (the host, another invitee, another placed player) can still send them a fresh invitation for the same game, and they’ll get a new push. Even you can invite them again later if you want.

There’s also no limit on how many times this can happen. A person who keeps saying no will keep getting fresh invitations until the chain stops sending them, or until the host takes the separate step of excluding them (see below).

If you personally don’t want to see any of their games again — declined or not — that’s a different control: blacklisting them from your side. Declining an invitation and blacklisting a host are separate actions that do different things.

Host-only: excluding a player

The host has an extra power tucked into the same screen: they can mark a specific user as not welcome for their game. From the excluded user’s side this looks like a declined invitation they never knew existed — but it also prevents that user from showing up on the roster. This is how a host can keep a specific person out of a private or public game without changing the game’s visibility.

The exclusion is global, not per-inviter

Once the host has excluded user X, every future invitation targeting X for that game bounces — regardless of who sends it. A different chain member (B in the worked example) can’t work around the exclusion by sending their own invite; Furbol blocks it with a “blocked by host” reason. Only the host can undo the exclusion.

Non-host declines don’t exclude anyone

If a non-host chain member taps the red X on the invites tab, that just declines the invitation they sent (or would have sent). It doesn’t block the person globally. The host, or another chain member, could still invite the same person later. Only the host’s decline creates a persistent exclusion.