Troubleshooting
Find the message you see or the problem you have, why it happens and how to fix it. Signing in, cloud servers, in game, matches and the Community hub.
Each entry below is a problem or the exact message Grindhouse shows. Open it for the cause and the fix. Search with Ctrl K and a few words of the message to find its entry.
Signing in & account
Email codes
Email codes don't arrive
- Cause
- Codes for resetting your password, verifying or changing your email and deleting your account come by email from [email protected]. They can land in spam or a promotions tab, the address may be mistyped, or a newer code already replaced the one you're looking at. For a password reset, Grindhouse only says "If … has an account, we sent it a code", so a typo in the address looks the same as a sent code.
- Fix
- Search your mailbox, spam included, for "Grindhouse". The code is in the subject line too, for example "Reset your Grindhouse password: 123456".
- Check the address you typed. On the reset screen, Use a different email starts over.
- Wait a minute, then Send again. Only the newest code works, except for a password reset or a sign-up, where every code from the last 15 minutes does.
- Codes are 6 digits and expire after 15 minutes. See How email codes work.
- "We couldn't send the email right now. Try again in a few minutes."
- Grindhouse's email service didn't take the email. Nothing was sent; try again later.
"That code isn't right. Check it and try again." / "That code has expired. Send a new one."
- Cause
- The code was mistyped, it's older than 15 minutes, it was tried 5 times already, or you asked for a newer one (which replaces it).
- Fix
- Use the code from the newest email. If it has expired, ask for a new one and enter it within 15 minutes.
"Too many attempts. Wait a minute and try again."
- Cause
- Grindhouse limits how often one network can try to sign in or ask for codes. Code emails are limited to a few every 10 minutes.
- Fix
- Wait a minute or two and try once, carefully. Don't keep pressing Send again: the last code you got still works for 15 minutes.
Email and password
"Wrong email or password."
- Cause
- The email and password don't match an account. Caps Lock is a common reason: the password field shows "Caps Lock is on" when it is.
- Fix
- Try again, or press Forgot password? to set a new one with an email code. If you made your account with Steam, Sign in with Steam works too. In Settings the same problem reads "That password isn't right." or "Your current password isn't right."
"That email already has an account — sign in instead."
- Cause
- Someone, probably you, already made a Grindhouse account with that email. When changing your email in Settings the message is "That email already belongs to another Grindhouse account."
- Fix
- Press Sign in in the message and use that account, or use Forgot password? if you don't remember its password.
"Use at least 8 characters." / "That doesn't look like an email address."
- Cause
- Passwords need 8 to 128 characters and can't be digits only ("Use something other than only numbers.", "Use at most 128 characters."). The email needs a normal address shape, like [email protected].
- Fix
- Fix the field that's marked. The meter under the password says Too weak, Okay or Strong.
Steam
"That Steam account is already linked to another Grindhouse account."
- Cause
- Every Steam account can belong to one Grindhouse account. Usually you made one account with Steam and another with email.
- Fix
- Sign out and use Sign in with Steam: that takes you to the account that has your Steam. If you'd rather keep the other account, delete the one with Steam (Settings → Privacy → Delete account), then connect Steam to the account you're keeping. See Your Steam account.
"You can change your linked Steam account again on …" / "You can change your linked Steam account once every 30 days. Next change: …"
- Cause
- After Steam is linked or changed, it can't be changed again for 30 days. Settings → Connections shows the date: "You can change it on …".
- Fix
- Wait until that date. See Changing it.
Steam sign-in doesn't finish
Messages you may see: "The Steam sign-in expired. Try again.", "That sign-in expired or was started in another tab. Try again.", "That sign-in didn't come from this tab. Try again.", "That Steam sign-in expired or was already used. Try again.", "The browser came back without a sign-in code. Try again.", "Steam sign-in didn't complete. Try again.", "The Grindhouse server sent an unexpected answer. Try again."
- Cause
- Each Steam sign-in is tied to the tab that started it and works once, for 10 minutes. It fails when you take longer than that on Steam's page, start in one tab and finish in another, or press Back and reuse an old page. "Steam sign-in was cancelled." isn't a failure: you backed out on Steam's page, and nothing changed.
- Fix
- Start again from the Grindhouse tab you want to use and finish on Steam's page straight away.
"Your Steam sign-in timed out. Sign in with Steam again."
- Cause
- After a Steam sign-in with a Steam account that's new to Grindhouse, you finish by adding an email and password (One last step). That step has to happen within 15 minutes of Steam's page.
- Fix
- Sign in with Steam again and fill in the form right away.
"Connect your Steam account first."
- Cause
- Your account has no Steam account linked. Grindhouse needs it to find your matches, to save your training on servers and to show your name on what you publish.
- Fix
- Press Connect Steam on the Connect your Steam account screen or in Settings → Connections.
Sessions and connection
"Your session ran out. Sign in again." / "Your session has ended. Sign in again."
- Cause
- Sign-ins last 60 days from the last time you used Grindhouse on that device. Changing your password signs out your other devices ("Password changed. Other devices were signed out."), and deleting your account signs out everywhere.
- Fix
- Sign in again. Nothing is lost: your training, matches and settings are kept. See Sessions, tabs and signing out.
"Can't reach Grindhouse right now…" / "You're offline…"
- Cause
- Your device can't reach grindhouse.gg: no internet, a firewall or VPN in the way, or Grindhouse is briefly down. Variants: "Can't reach Grindhouse right now. Check your connection, then try again.", "Can't reach Grindhouse right now. It reconnects by itself." and "Can't reach the Grindhouse server right now. Try again in a moment."
- Fix
- Check your connection. Grindhouse keeps checking and reconnects by itself; you don't need to sign in again. While offline, account changes are disabled ("You're offline. Account changes come back when Grindhouse reconnects."). See When Grindhouse can't be reached.
"Grindhouse didn't answer. Try again."
- Cause
- A sign-in or account change got no answer within 20 seconds.
- Fix
- Try again. If it keeps happening, check your connection.
FACEIT and other account messages
Linking FACEIT fails
- "We couldn't find a FACEIT player with that nickname."
- Check the spelling. Copy the nickname from your FACEIT profile.
- "That FACEIT account plays CS2 on a different Steam account than the one linked to Grindhouse."
- Grindhouse checks that the FACEIT account uses the Steam account you linked. Link the FACEIT account you play CS2 with on that Steam account.
- "That FACEIT account has no CS2 profile, so there's no Steam account to match with yours. …"
- The nickname belongs to a FACEIT account that has never added CS2, so Grindhouse can't check it against your Steam account. Check the spelling, or link the FACEIT account you play CS2 on.
- "FACEIT is limiting how often Grindhouse can look players up right now. Try again in a minute."
- FACEIT is rate limiting Grindhouse's server, not you. Wait a minute and press Link FACEIT again.
- "That FACEIT account is already linked to another Grindhouse account."
- Unlink it there first: Settings → Connections, then Unlink FACEIT in the FACEIT row's ⋯ menu.
- "Couldn't reach FACEIT: …" / "FACEIT answered …" / "FACEIT sent something unexpected: …"
- FACEIT is down or busy. Try again in a few minutes.
- "That isn't available on this server yet."
- FACEIT linking isn't switched on. Nothing to do on your side.
More in FACEIT.
"Grindhouse isn't taking new accounts right now. Try again in a little while."
- Cause
- New sign-ups are paused for the moment. Existing accounts sign in as usual.
- Fix
- Try again later.
"This account is switched off. Contact Grindhouse if you think that's a mistake."
- Cause
- The Grindhouse team switched this account off.
- Fix
- Contact us (see Getting help) with the email of the account.
Other account messages
- "Please check the highlighted fields."
- Something in the form is missing or in the wrong shape. The field says what.
- "That isn't available on this server yet."
- That feature isn't switched on yet. Nothing to do on your side.
- "We couldn't find that." / "You don't have access to that."
- The thing you asked for is gone, or belongs to another account. Reload the page.
- "Sign in first."
- Your session ended in the background. Sign in again.
- "Still connecting to Grindhouse…"
- The page is still loading your account. Try again in a few seconds.
Cloud servers
How cloud servers work is on Cloud servers. The server pill at the top right (and its panel) and the server bar on Play (along the bottom of the mode's picture) show every message below.
Play is greyed out
Play is greyed out: "Connect Steam to play"
- Cause
- A server is started for your Steam account, and your account has none linked.
- Fix
- Press Connect Steam in the server bar.
Play is greyed out: "Early access only"
- Cause
- "Cloud servers are in early access, and your account isn't in it yet. Everything else works as usual." Matches, the coach, Progress, the Library and Community all work without a server.
- Fix
- Nothing to fix. Play becomes available once your account is in.
Starting a server
Stuck on "Creating server…"
- Cause
- A server is usually ready in about 30 seconds. After about a minute and a half the bar adds "taking longer than usual". If a server isn't up after 5 minutes, Grindhouse gives up on it: "Your server didn't start", with "It couldn't start: The server didn't start in time. Try again in a minute. Press Play to try again."
- Fix
- Press Cancel (or wait for it to give up) and press Play again. If it happens again, pick another Region in the server panel when more than one is offered.
"Your server didn't start"
- "The server couldn't be started. Try again in a minute."
- The server host refused to start it. Wait a minute and press Play.
- "The server disappeared at the host. Try again."
- The host lost the server while it was starting. Press Play for a new one.
- "Cloud servers aren't set up on this site any more."
- Servers were switched off while yours was starting.
Nothing you saved is lost: your settings and training are in your account, not on the server.
Joining
Connect does nothing (the steam:// link doesn't open CS2)
- Cause
- Connect is a
steam://link. It needs the Steam client running on this computer, and your browser asks once whether it may open Steam. If you dismissed that, or Steam isn't installed here, nothing happens. - Fix
- Start Steam, press Connect again and allow the browser to open Steam.
- Or press the copy button next to Connect ("Console command copied. Paste it in the CS2 console (~)."), open CS2, press ~ and paste. If ~ does nothing, turn on the developer console in CS2's game settings.
- If copying fails ("Couldn't copy. Select the text and press Ctrl+C."), open the server panel from the pill, press the eye button to show the password, and copy the console line by hand.
"Your server is still starting. Connect works once it's ready." and "Your server isn't running. Press Play to start one." mean what they say. See Joining your server.
CS2 says the password is wrong
- Cause
- Every new server gets a new password. A connect line from an earlier server, or one from your CS2 console history, no longer works. The console command needs both parts:
connectwith the address, thenpasswordwith the password. - Fix
- Use Connect, or copy a fresh console command from the server panel. The eye button there shows the password if you want to type it.
"No Steam game server token was free, so players outside the server's network may not get in."
- Cause
- Your server started without a Steam server token, which can stop you from joining.
- Fix
- Try Connect. If you can't get in, press Stop server and Play again: each new server tries for a token again.
Can't join right after a CS2 update
- Cause
- After a CS2 update your game and the server have to be on the same version. If Steam hasn't updated your game yet, or the server was started from an older copy, CS2 refuses the connection.
- Fix
- Close CS2 completely so Steam installs the update, then start it and join again. If your game is already up to date, stop the server and start a new one a little later.
Stopping
My server stopped
The server bar and a toast ("Your server stopped. …") say why:
- "Nobody was on it for 10 minutes, so it shut down."
- The idle stop. It counts from the moment nobody is on the server, so it also stops 10 minutes after you leave. Just press Play again.
- "It reached the 6-hour limit for one session."
- One session has a maximum length. Press Play for a new server.
- "Grindhouse's server time for this month is used up."
- Servers start again on the 1st.
- "Something went wrong with it: The server stopped answering. Press Play for a new one."
- The server stopped talking to Grindhouse, so it was closed. Press Play.
- "The Grindhouse team stopped it. Press Play for a new one."
- Stopped by us, usually for maintenance.
- "You stopped it."
- You pressed Stop.
The limits shown are the defaults; the server panel shows the current ones. Your training is saved while you play (every 15 seconds or so), so a stop loses at most the last few seconds. Start again in the panel starts the same mode and map.
"Your last server is still shutting down. A new one starts right after."
- Cause
- You can have one server at a time, and the last one hadn't finished stopping.
- Fix
- Nothing: the new one starts on its own once the old one is gone. If you see "Your last server is still shutting down. Press Play again in a few seconds.", do just that.
"… isn't available on cloud servers. Pick another map." / "That map isn't available on cloud servers."
- Cause
- Cloud servers carry a fixed set of maps. A map from a Community item or an old setting may not be one of them.
- Fix
- Pick another map on Play.
"Couldn't stop your server. Try again."
- Cause
- The stop didn't go through. With no connection the message is "Can't reach Grindhouse right now, so your server couldn't be stopped. It stops by itself once nobody's on it."
- Fix
- Press Stop again. If you can't, leave the server: it stops by itself after the idle time.
In game
Commands
Commands do nothing
- Cause
- Grindhouse commands start with
.,!or/and are typed in chat. In the console, a bare.aimisn't a command. A typo is just sent as a chat message. - Fix
- Type it in chat:
.help.!helpworks too and stays visible in chat;.helpand/helpare silent. - In the console, put
sayin front (say .help), or use thecss_name (css_help). Binds use thecss_names too. .helpshows what you can do right now, and.helpplus a topic (.help bots) lists one section.
See How to type commands.
- Type it in chat:
- "… doesn't apply in Deathmatch. …"
- The command belongs to another mode. The message names the mode you're in and what to do instead, like "Use .deathmatch first." or "Use .recoil first."
- "The mode is loading; wait for the map."
- A mode or map change is under way. Wait for the map to load, then type it again.
Bots, spots and the HUD
Aim: the bot didn't appear
- "Join T or CT first, then type !aim"
- You're a spectator. Pick a team, then type
.aim. - "This map has no spawn spots. Walk around and use !fov_addspot."
- The map has fewer than two spots to place you. Walk around and save a few with
.addspot. See the next entry. - "Couldn't get a bot to join."
- The server couldn't add a bot. Type
.restart, or.aimtwice to stop and start again. - No message, no bot
- At a cone over 180°, each new spot starts with a 3-2-1 countdown first. Bots are only placed where the game says you can really see them; if one ends up somewhere awkward,
.skipmoves it to a new spot..botswith a number sets how many appear at once. See Aim.
A new map has no spots, routes or lineups
- Aim
- Spots come from the map's deathmatch spawns plus the T and CT spawns, and Grindhouse learns new spots while you walk around. On maps without enough, save your own with
.addspot. See Aim → spots. - Spray and spray transfer
- About eight spots are made the first time you play a map.
.sprayspotadds, removes and tests your own. - Gunfights
- A map's arenas are found the first time a gunfight needs them there.
.arena genlooks for more and.arena herebuilds one where you stand. The peeks, Team Hold and Defusal use the same arenas. Site Hold, Endless · Defend, Team Hold, Defusal and Retakes need a map with bombsites. See Arenas. - Pop, Movement
- Pop finds an open spot for its targets the first time (
.pop herepicks one where you stand); Movement's jumps are found from the map's layout too. - Prefire, lineups and strats
- Those start empty on every map: build your own, or add some from Community.
The stats HUD is missing
- Cause
- The on-screen stats under the crosshair are part of Aim training only, and
.hudswitches them off and on. In other modes you get ".hud doesn't apply in … The stats HUD is part of Aim training." - Fix
- In Aim, type
.hud(it says "Stats on screen.")..hud biguses CS2's larger box, which sits higher and pulses about once a second;.hud textgoes back to the steady one..statsprints your numbers in chat any time. See Aim → HUD.
Recoil control and utility
Recoil control: "this weapon isn't measured yet"
Variants: "Stand still and fire one full spray without E to measure the … pattern (saved for next time).", "Pattern ON, but this weapon isn't measured yet. Stand still and fire one full spray without E (nospread on).", "Release E and fire a full stationary spray with nospread ON first; the demo needs a measured point for the next bullet."
- Cause
- The purple path and the hold-E demo need the weapon's pattern, which the trainer measures from the server's own recoil the first time you spray it.
- Fix
- Stand still, aim at a wall and fire one full spray without holding E, with spread off (the default;
.nospreadtoggles it). You get "Measured … recoil points for the …". The pattern is saved with your account, so every cloud server you start has the guns you've measured. See Recoil control → measuring. - "This CS2 build has no nospread control. …"
- After some CS2 updates spread can't be switched off. Spray feedback still works, but patterns can't be measured until that's back.
Utility: the lineup aim dot doesn't show
- Cause
- The red aim dot only shows when all of this is true: you're in utility mode, the markers are on, you're standing inside the lineup's throw circle with both feet on the ground (not jumping or in noclip), and, if you're holding a grenade, it's the lineup's grenade type. It also waits while the camera follows a grenade, and a running
.timertakes over the center text. - Fix
- Type
.markersif the circles are gone (".markers works in utility mode (.util)." means you're not in utility mode). .nadewith the lineup's number puts you exactly on the spot, grenade in hand. It also picks the right lineup when circles overlap.- Put your crosshair on the center dot until the hint says "Aim aligned".
See Utility → aim dot.
- Type
Cloud server: "Couldn't rethrow …" for a smoke, or a strat's smokes don't show up
- Cause
- Cloud servers throw recent and recorded grenades the way CS2 itself does, and check at start that they still can. Right after a CS2 update that check can fail, and the server falls back until Grindhouse catches up:
.rethrow 0 1 2can't throw smokes again ("Couldn't rethrow 0 (its flight wasn't captured or the grenade can't be spawned).") and strat playback skips recorded smokes. Flashes, HE grenades, molotovs and decoys are still thrown. - Fix
- Nothing to fix on your side. Plain
.rethrowand.replaythrow your last smoke again in the meantime. See Utility and Strats.
Other messages
Other in-game messages
- "No lineup "…" on de_mirage. .nades lists them."
- There's no lineup with that number or name on this map.
.nadeslists them. - "No kills yet this session."
.statsin Aim before your first kill.- "No finished prefire runs yet this session. …"
.statsin prefire before you've cleared a route or died in one. Restarts and skips don't count. See Prefire → .stats.- ".stats doesn't apply in utility mode. Utility practice keeps no session stats. …"
- Utility isn't scored, so there's nothing to sum up.
.nadeslists the map's lineups. - "Not training – type .aim or .prefire."
- You typed
.nextor.prevwhile no training is running, for example after.aimstopped aim training. Start a mode first. - "Aim spots are random, so there's no previous one. …"
.previn Aim. Each spot is picked at random;.nexttakes you to a new one.- "Deathmatch is continuous; fight now. .aim / .prefire / .util changes modes."
.startisn't needed in deathmatch.- "Following grenade · .end returns to the player"
- The utility camera is following your throw.
.endbrings it back at once.
Matches
Where matches come from and how to set each source up is on Bring in your matches.
Match sharing
Match-sharing codes are rejected
- "Steam didn't accept that authentication code. Create a new one on Steam's page."
- The authentication code is wrong, or belongs to another Steam account than the one you linked. On Steam's match history page, under Access to Your Match History, press Create Authentication Code and copy it again. It looks like
AAAA-AAAAA-AAAA. - "That match code isn't valid. Copy your most recent one from Steam's page."
- The match code has the wrong shape. It starts with
CSGO-and has five groups of 5 characters. - "Steam doesn't recognise this share code for your account (codes older than about 30 days stop working). Use the code of your most recent match."
- Paste the code next to Your most recently completed match token on Steam's page.
Tip: select that whole section on Steam's page, copy it, and press Paste from clipboard in Settings → Match history: Grindhouse finds both codes. See Match sharing.
Match sharing stops: "Needs a newer match code" or "Authentication code rejected"
- Cause
- Codes that worked can stop working: Valve forgets old match codes ("Valve no longer accepts the saved match code. Paste your most recent one."), and Steam can stop accepting your authentication code, for example after you made a new one on Steam's page ("Steam rejected the authentication code. Create a new one and save it again.").
- Fix
- In Settings → Match history, press Update codes and save fresh ones.
No matches yet after saving my codes
- Cause
- The first check runs within a few minutes of saving. It brings in the match whose code you pasted, then every match after it. Matches older than the pasted one can't be fetched with match-sharing codes.
- Fix
- Wait a few minutes, or press Get recent matches at the top right of the Matches page. If the status says waiting for the server or shows an error, see below. Upload the demos of older matches you want.
Match sharing is "waiting"
- "Waiting for first sync" / "Match sharing: waiting for first sync"
- Your codes are saved and the first check runs in a few minutes. It brings in the match whose code you pasted.
- "Match sharing is waiting for the Grindhouse bot, which isn't switched on yet. …" / "Waiting for the server" / "Match sharing: waiting for the server"
- Background sync isn't running on Grindhouse's side yet (another variant: "This server has no Steam Web API key, so new matches can't be fetched automatically."). Your codes are saved and matches come in once it is. Upload demos meanwhile.
- "Steam is busy. Trying again later."
- Steam asked Grindhouse to slow down. It retries by itself.
- "Sync error"
- "The last background sync failed." Your saved codes can't be used: save them again. (When Steam itself is down you see no error; new matches come in on a later sync.)
Scoreboard only
A FACEIT match shows "Scoreboard only"
- Cause
- FACEIT shares the scoreboard of your matches, not the demo. Without the demo there are no rounds, aim or utility stats.
- Fix
- Download the demo from the FACEIT match room and add it with Import demo file on the Matches page. Keep the file name FACEIT gives it (it starts with
1-), so it lands on the same match, which then gets the full breakdown and a 2D replay.
A Valve match shows "Scoreboard only": "Valve deleted the demo"
- Cause
- Valve keeps match demos for about a month. A match imported later only has its scoreboard.
- Fix
- If you downloaded the demo in CS2 (Watch → Your Matches) or saved it elsewhere, import it with Import demo file. Turning on match sharing gets new matches while their demos still exist.
Demo files
A demo upload or import fails
The Matches status line says Import didn't finish (or Offline, can't import right now) with one of these under it.
- "Pick a CS2 demo: a .dem file (.dem.gz, .dem.bz2 and .dem.zst work too)." / "This file isn't a CS2 demo. …"
- The file isn't a demo. Pick the
.demfile itself (or a.dem.gz,.dem.bz2or.dem.zst). - "This is a CS:GO demo. Only CS2 demos can be imported."
- Old CS:GO demos can't be read.
- "That demo is over 1 GB, too big to upload."
- Demos can be up to 1 GB.
- "The file couldn't be unpacked. Check that the download finished, then upload it again."
- The compressed file is cut off or damaged. Download it again.
- "This demo couldn't be read. It may be damaged, or from a CS2 version Grindhouse can't read yet."
- Try a fresh download. A demo from a brand-new CS2 version may work after a Grindhouse update. The match shows Failed: "The demo couldn't be read."
- "You're not in this match. Only matches you played in can be imported."
- Grindhouse matches demos to you by your linked Steam account. Check that the demo is yours and that the right Steam account is linked.
- "Connect your Steam account first: a demo is matched to you by your Steam account."
- Link Steam in Settings → Connections.
- "A demo is still uploading. Pick the next one when it's done." / "You already have … demos uploading. Wait for them to finish."
- Wait for the current uploads to finish.
- "The upload was interrupted. Check your connection and try again." / "The upload stopped for over an hour and expired. Upload the demo again."
- Upload it again.
- "Demo uploads are paused for a moment. Try again a bit later."
- Uploads are briefly switched off. Try again later.
- "Reading the demo is taking very long. It shows up in Matches once it's done."
- Nothing to do: it keeps going in the background.
All upload messages: Bring in your matches → upload messages.
No Get recent matches: "Upload a demo, or turn on background sync"
- Cause
- Your account has no automatic source yet: no match-sharing codes and no FACEIT. The Matches page's Get recent matches button only gets recent matches once one is set up.
- Fix
- Press Set up sync at the top right of the Matches page and add your match-sharing codes in Settings → Match history, link FACEIT, or upload a demo with Import demo file.
- "Upload a demo to import a match"
- Your match-sharing codes are saved, but background sync isn't running on Grindhouse's side yet (see Match sharing is "waiting" above). Upload demos meanwhile.
2D replays
"No 2D replay for this match"
- Cause
- The line under it says why. A scoreboard-only match has no demo, so no replay. Otherwise the match was read before 2D replays existed and can't be rebuilt from Valve's copy of the demo ("This match was imported before 2D replays existed."), or no replay was stored when its demo was read ("No 2D replay was saved when this match's demo was imported.").
- Fix
- Upload the demo again with Import demo file on the Matches page and the match gets a replay. Every message is on 2D replays → Replay messages.
Sight is dimmed, or the grenade card has no "Blinded" or "Damage"
- Cause
- The match was imported before Grindhouse recorded those details. The replay says so: "Sight lines come with matches imported from now on", "Who it blinded is shown for matches imported from now on." On a map Grindhouse has no geometry for, Sight says "No sight lines for this map".
- Fix
- Nothing to fix: the rest of the replay works as usual. See Details in newer replays.
Community hub
Adding items
"That's yours: it's already in your library."
- Cause
- You published this item, so it's already in your Library. You can't add a copy of your own item.
- Fix
- Play it from your Library ("That's yours: play it from your Library.").
Adding fails: "This map already has 100 spray spots. Remove some first."
- Cause
- A map holds at most 100 spray spots. Other messages from the same step: "Your spray spots file for this map can't be read, so nothing was added to it." and "Your training files couldn't be written. Try again."
- Fix
- Remove some spots (
.sprayspot delin game, or a spray spot pack with Remove from library in its ⋯ menu in the Library), then add the pack again. If your training files couldn't be written, just try again.
A lineup I deleted from a pack came back
- Cause
- A lineup pack from the hub is one copy: taking the author's update puts the whole pack in again, including a lineup you deleted in game with
.delnade. That's also why a pack lineup's ⋯ menu in the Library offers Remove the whole pack, not a single delete. - Fix
- Keep the pack and skip that throw, or remove the pack (Remove from library in the ⋯ menu of its row under From the Community hub) and save the throws you want as your own lineups. See Removing a copy.
"This routine has no steps that can be played here."
- Cause
- None of the routine's steps is a mode Grindhouse can run.
- Fix
- Pick another routine, or build your own warm-up (see Daily warm-up).
Publishing
Publishing fails
- "Connect your Steam account first: your Steam name and avatar show on what you publish."
- Link Steam in Settings → Connections.
- "You can publish or update 30 times a day. Try again tomorrow."
- Each account can publish or update 30 times per day (UTC). See Community hub → limits.
- "Only the author can change this."
- You can only edit your own items.
- "A route's title is 48 characters at most: it becomes the route's name in game." / "A strat's title is 40 characters at most…"
- A player's copy of a route or strat is named after your title, so it has to fit a route or strat name. Shorten it; other kinds take up to 60 characters. An item you published with a longer title can keep it as long as you don't change it ("This title is longer than … It can stay as it is; a changed one has to fit.").
Getting help
Still stuck? Message us at @grindhousecs. To help us help you fast, include:
- Your browser and whether you were on a PC or a phone.
- What you did and what you expected, step by step.
- The exact message, ideally a screenshot of it.
- When it happened, with your time zone.
- The mode and map for in-game problems. For cloud servers, the region and what the server panel said.
Careful: Never send these
Your password, email codes or your match-sharing authentication code. Nobody from Grindhouse will ask for them.