Перейти к содержимому
Furbol — How It Works

Editing a Game

Это содержимое пока не доступно на вашем языке.

Editing a Game

This page walks through changing a game you’ve already created — opening the editor, which fields are editable at each moment, and what the save does. The rules behind it (what’s locked vs. open, constraints, fee-raise rules) live on Editing a Game (rules).

1. Find the Edit button

Open the game. In the top-right of the game detail page, tap the three-dot overflow menu.

Among the host-only entries, tap EDIT GAME.

Same menu that hosts cancel from — the EDIT GAME and CANCEL GAME rows sit side by side. Both disappear once the game reaches the results stage; edits are no longer possible past that point.

2. The editor opens as a fullscreen screen

Tapping EDIT GAME opens the full editor — same widget the creation flow uses, but pre-filled with this game’s current values. It’s a regular screen with a close button in the top-left and an UPDATE GAME button at the bottom. Not a modal, not a bottom sheet.

It’s the same editor you saw when you first created the game — the shape is identical. The difference is what’s editable and what’s locked.

3. The lock banner, if you see it

At the top of the editor, if another player has already joined the game, a banner reads:

“Other players have joined. Venue, schedule, and payment amounts below are locked.”

This is the single most important signal in the flow. The moment someone else is on your roster, a big block of fields flips read-only — and the banner is how you know why.

Until the first external booking lands, the editor is wide open. Once one shows up, the lock kicks in and stays locked for the rest of the game’s life.

4. What stays editable even after others join

Even with the lock banner on, you can still change:

  • Name, description, notes — the text fields.
  • Min and max players — the player-count bounds.
  • Teams count — from one team up to eight. See Teams.
  • Age, level, experience, solidity bounds.
  • Facilities — indoor, astro turf, showers, bar, parking, ball, bibs, goal posts.
  • Visibility flags — anonymous allowed, external allowed, guests allowed, goalkeeper required.
  • Game on, no matter what — but only until the last hour starts (see below).

5. What locks once others join

With the banner on, these fields go read-only — you can see the values but can’t change them:

  • Venue — you can’t re-point the game at a different pitch.
  • Kick-off and finish time (and the duration field).
  • Payment method (cash / online / free) — this one is actually locked at publish, not at first booking, but the editor shows it as read-only either way.
  • Fee amount — read-only too, not just constraint-limited.
  • Goalkeeper hiring fee — locks in the same cluster as the main fee, even though visually it sits further down the editor in its own “GOAL KEEPER” block.

The rule page discusses fee-editing with a “can’t raise if someone self-booked” nuance — in practice it’s simpler: once anyone joins, the fee field is read-only. That nuance would only matter if the editor ever let you re-open the field, which it doesn’t.

Why “others” and not “anyone”

You booking yourself into your own game doesn’t trip the lock — only someone else joining does. It’s specifically another player on the roster — followers you booked, guests, self-bookers — that flips the switch.

6. The “game on” toggle’s extra window

Even when the lock banner isn’t on, one toggle has its own window:

  • Game on, no matter what can be flipped up until one hour before kick-off.
  • Inside the last hour, the toggle is frozen. Trying to flip it gets rejected with an error.

The rest of the editor’s fields don’t have this extra window — they follow the “locked once others joined” rule, period.

7. Save

At the bottom of the editor, tap UPDATE GAME.

  • On success: a green snackbar, “Game was edited successfully!”, and the editor closes. You’re returned to the game detail page with the updated values.
  • On error: a red snackbar with the error message. The editor stays open — fix the field and tap update again. Common errors you might see:
    • “Payment method cannot be changed after the game is published.”
    • “Cannot increase the fee while players have self-booked.”
    • “Game on can only be changed until one hour before kick-off.”

These error messages come from Furbol’s rules check, not from the app. The UI doesn’t pre-validate them — it’s only on UPDATE GAME that they surface. If the editor seems to let you change something, but the save bounces, it’s likely one of these.

8. What reaches the players

  • A game update notification lands on everyone in the lineup, but not immediately — it batches to roughly an hour before the new kick-off. Players don’t get spammed every time you touch a field.
  • The game’s activity log picks up a “game edited” entry. Visible to anyone on the game.
  • If you flipped the game on, no matter what toggle, an extra log entry records the switch.

9. What you won’t see in this flow today

Worth naming:

  • No save-and-continue, no auto-save. Every edit is explicit — UPDATE GAME, close, reopen to edit again.
  • No “this will re-notify everyone” warning. You won’t see a popup warning you that your edit triggers a push. It just does (at the batch time).
  • No diff preview before save. The editor doesn’t show “you changed kickoff from 20:00 to 20:30” before you commit. What you see in the fields is what you’re saving.
  • No inline error while you type. Even when a field is constrained (like fee-raise-with-self-booked-players), the editor doesn’t grey the row out as you edit — the error only shows after you tap UPDATE GAME. In practice, when the lock banner is on, the field is already read-only, so this is mostly a moot point.
  • No way to convert cash→online or vice versa. Payment method is strictly immutable after the game is published. The only path is to cancel and create a new game.