To ban a player during a live Squad match, join as an administrator with the ban access level, press the tilde key (~) to open the in-game console, and run AdminBan <NameOrSteamId> <BanLength> <BanReason>. For example, AdminBan PlayerOne 1d Repeated teamkilling applies a one-day ban. Use 0 as the length for a permanent ban.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Squad servers with free DDoS protection and up to three free backups a day.
If the server player ID is more reliable than a name, use AdminBanById <PlayerId> <BanLength> <BanReason>. Manual bans are stored in SquadGame/ServerConfig/Bans.cfg; an expiration value of 0 in that file is permanent. The sections below show the safe procedure, duration choices, unban process, and moderation practices that keep a server compliant with Offworld Industries policy.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Raven Squad - PC | $3.95 | Buy on Amazon |
| 2 |
|
Laser Squad Nemesis - PC | $21.48 | Buy on Amazon |
| 3 |
|
Mass Effect 2 - PC | $9.95 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What you need before issuing a ban
You must be connected to the server as an administrator whose access configuration includes ban. Without that access level, the ban commands will not execute. The separate immune access level protects an administrator from kick and ban actions; it is not a substitute for granting the ban permission to the person who moderates players.
Identify the target precisely before acting. A display name can be ambiguous, can change, or can contain characters that make console entry awkward. A SteamID gives you a persistent account identifier, while a server player ID is the short identifier shown for the current connection. If two players have similar names, choose the SteamID or the player-ID command instead of guessing.
#1 Best Overall
- Combined RTS vs. FPS multiplayer experience opportunity. Jungle Atmosphere.
- Intuitive command and camera system. 8 Controllable Units with unique weapons and skills.
- 11 Campaign Missions with Co-Op Support
- Online and Local 2 player Co-Op
- 5.1 Atmospheric Dolby Digital Sound Experience
Have your server rules and the incident details available. Offworld Industries says licensed servers may set their own disciplinary standards when those standards align with the Squad Code of Conduct. Its policy also says, “Servers may ban players to protect the integrity of their server.” A clear rule and a factual incident note make a later appeal easier to resolve.
Choose the right ban command
| Command | Identifier | When to use it | Example |
|---|---|---|---|
AdminBan |
Player name or SteamID | Use when the name is unique or you have the account identifier. | AdminBan PlayerOne 1d Repeated teamkilling |
AdminBanById |
Current server player ID | Use when the player list or console gives you a clearer numeric server ID than the display name. | AdminBanById 42 0 Exploiting a server bug |
Both commands accept the same duration and reason fields. The distinction is only how the target is identified. A player ID is tied to the current session, so confirm it immediately before executing the command; a SteamID is preferable when you are documenting a ban for future reference.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Ban someone from the live server
- Confirm your permission. Log in with an administrator account that has the
banaccess level. If the command is rejected, ask the server owner to correct the access configuration rather than repeatedly retrying. - Verify the target. Compare the player’s name, server player ID, and SteamID where available. Check the incident against the published rule that was allegedly broken.
- Open the console. While connected to the server, press the tilde key (
~). The in-game console is the quickest route because the action is applied while the match is running. - Enter the command. Use the name or SteamID form when that identifier is unambiguous:
AdminBan PlayerOne 1d Repeated teamkilling
Use the player-ID form when the server ID is clearer:AdminBanById 42 1d Repeated teamkilling - Check the result. Confirm that the player is removed or denied access and record the exact duration, reason, identifier, map, and approximate time. Keeping the command output or a screenshot is useful if the player appeals.
- Publish or communicate the outcome as your rules require. Do not disclose private account information in a public chat channel. A concise message naming the violated rule and the appeal route is generally enough.
The reason field should describe an observable action, not an insult or speculation. For example, use Repeated intentional teamkilling after warning rather than a vague label. The policy requires a valid reason and evidence; evidence is specifically recommended for mass bans.
Set a timed or permanent duration
The ban-length field controls how long the account is blocked. A value of 0 means permanent. Timed values use a number followed by a unit; the documented examples are 1d for one day and 1M for one month. Keep the capitalization exactly as supported by your server build: d denotes days and an uppercase M denotes months in the documented syntax.
| Length value | Effect | Example |
|---|---|---|
0 |
Permanent ban | AdminBan PlayerOne 0 Cheating confirmed by server evidence |
1d |
One day | AdminBan PlayerOne 1d Mic abuse after warning |
1M |
One month | AdminBan PlayerOne 1M Repeated rule violations |
Use the shortest period that protects the server and is consistent with comparable cases. A permanent ban is appropriate only when your published standards justify it and the evidence supports the decision. If you need a different interval, use the duration notation accepted by your server’s current administration reference and test it with a non-punitive moderation workflow before relying on it.
Make a permanent ban persist in Bans.cfg
Manual bans are recorded in SquadGame/ServerConfig/Bans.cfg. Each ban occupies its own line. The documented core format is the banned player’s SteamID, a colon, and a Unix expiration timestamp:
<SteamID>:<UnixExpirationTimestamp>An expiration value of 0 represents a permanent ban. Existing entries may also contain the issuing administrator and a comment. Because the exact optional-field formatting can vary with the server version or management interface, preserve the structure already used in your file when adding or reviewing those fields.
Rank #2
- Pick your squad by spending 'Force Points'
- Choose Laser Marines, Greys, Machina or Spawn - 4 different races with unique unit types and special abilities
- Alter the landscape with grenades, rockets and other deadly weapons, in the fully-destructible terrain
- Play single player campaigns for each of the four races, then challenge anyone, anywhere in the world
- World league rankings - progress through the Rookie, Veteran and Elite divisions
When editing manually, follow these safeguards:
- Stop the server before changing the file. Editing while the process is running can be overwritten or read only partially.
- Make a backup copy of
Bans.cfgbefore removing or changing an entry. - Put one ban on each line and retain the colon between the SteamID and expiration value.
- End the file with a newline so the final entry is written cleanly.
- Use the complete SteamID, not a display name or a temporary server player ID.
- Restart the server and verify that the entry is still present and effective.
The in-game AdminBan command is safer for a quick action because it avoids direct file manipulation. Direct editing is useful for maintenance, importing a documented list, or correcting a persistent entry while the server is offline.
Unban a player from Bans.cfg
For a control-panel or file-based unban, remove the matching line rather than changing it to an arbitrary date. Follow this sequence:
- Stop the server completely and wait until the control panel reports that the process has ended.
- Open
SquadGame/ServerConfig/Bans.cfgin the file manager or control-panel editor. - Locate the line containing the player’s SteamID. Check the complete identifier so that you do not remove another player’s ban.
- Delete that entire line, including any administrator or comment fields attached to it.
- Save the file with a trailing newline, then close the editor.
- Start the server again and test with the affected account or confirm the ban list through your administration tools.
Keep an audit note explaining who approved the unban and why. If the original ban was issued in error, correcting the record promptly is preferable to leaving an invalid entry in place.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Troubleshoot a command that does not work
The console says you lack permission
Check that the account running the command has the ban access level, not merely a generic moderator role. Ask an owner to reload or correct the administrator configuration, then reconnect if your server requires a fresh permission session. The immune flag only protects an administrator from kick or ban actions; it does not grant other administrators the ability to ban.
The wrong player is selected
Stop using a name when names are duplicated or difficult to parse. Copy the SteamID for a durable account-level action, or use AdminBanById with the current server player ID after checking the player list. Recheck the identifier before pressing Enter.
The ban length is wrong
Review the duration token exactly. 0 is permanent, 1d is one day, and 1M is one month in the documented examples. Do not substitute a lowercase m for the documented month form. If a value is rejected, consult the administration reference for the server version rather than guessing a unit.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe player returns after a restart
Inspect SquadGame/ServerConfig/Bans.cfg while the server is stopped. Confirm that the SteamID is complete, the expiration value is correct, and the line is not malformed. Restore the backup if a manual edit removed or damaged entries, then restart and verify again.
Rank #3
- Improved NPC conversation system where Commander Shepard can take matters into your own hands – interrupting or using force to get the answer required.
- The second act of BioWare's epic sci-fi RPG trilogy continues the story of Commander Shepard and humanity's first steps onto the galactic stage.
- Integration with the original Mass Effect game allows players to import saved files and contiue play with those files in Mass Effect 2.
- Choose from 19 different weapons, including devastating heavy weapons that can end a battle in seconds.
- New location based damage system allows for targeting of key weak points, blasting off limbs, igniting enemies, or cripple and disable enemy troops.
An unban appears not to take effect
Ensure the server was stopped before the line was deleted and restarted afterward. If the control panel maintains a separate cached configuration, repeat the check after a full stop/start cycle and verify that the line has not been recreated by a synchronization process.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Apply bans consistently and provide an appeal route
Technical access does not replace a moderation policy. Offworld Industries requires licensed servers to publish accessible in-game rules and provide a way for players to appeal bans. The policy also says that bans require a valid reason and evidence, with evidence recommended for mass bans.
A workable moderation record includes:
- The player’s SteamID and, for the incident, the server player ID if it was used.
- The rule number or wording that was violated.
- A short factual description of what happened.
- The date, approximate time, map, and administrators involved.
- Available evidence, such as logs, screenshots, or recordings, stored according to your privacy and retention rules.
- The ban length, command used, and the appeal contact or form.
Use the same escalation pattern for comparable conduct. For example, if your rules distinguish warnings, short suspensions, and permanent removals, apply those stages consistently unless the evidence shows an exceptional threat to server integrity. Tell the player how to appeal and what information to include; an appeal process is part of the policy requirement, not an optional courtesy.
Free tools Windows power users keep installed
One-click scans. No signup required.
Console command or file edit: which route fits?
| Decision factor | In-game command | Bans.cfg edit |
|---|---|---|
| Speed | Takes effect during the running match. | Requires a stop, edit, save, and restart. |
| Identifier | Name, SteamID, or current player ID, depending on the command. | SteamID-based line in the persistent list. |
| Duration | Enter 0 for permanent or a supported timed value such as 1d or 1M. |
Use a Unix expiration timestamp; 0 is permanent. |
| Operational risk | No direct file editing, so fewer chances to corrupt the list. | Requires a backup, a stopped process, correct line syntax, and a trailing newline. |
| Best use | Immediate response to a live incident. | Persistent maintenance, review, or carefully managed bulk changes. |
Whichever route you choose, record the same evidence and reason. The command path changes how the ban is applied, not the standard of conduct you should use to justify it.
Server-owner capacity figures that are easy to misread
Offworld Industries’ 2024 licensed-server guidance lists 8 GB of RAM as a minimum per server and 4 GB of additional RAM per game instance. It also lists a limit of 10 administrators per Squad server and a seven-day period to address reported violations. These figures concern licensed-server operation and administration; they are not hardware requirements for issuing an individual ban and do not change the command syntax.
If you operate several instances, account for the additional memory and keep administrator roles limited to people who need them. A smaller, accountable admin group makes it easier to maintain consistent decisions, preserve evidence, and answer appeals within the policy time frame.
Quick Recap
A practical moderation checklist
- Is the rule published and accessible in game?
- Do you have the
banpermission? - Did you verify the SteamID or current player ID?
- Did you choose a proportionate duration, with
0reserved for a justified permanent action? - Did you enter a factual reason and preserve supporting evidence?
- If you edited
Bans.cfg, was the server stopped, backed up, and restarted? - Did you tell the player how to appeal?
- Can another administrator understand and audit the decision from your record?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
