How to Install Fortress Forever and Join a Server
The first thing anyone does in Fortress Forever is throw a concussion grenade at their own feet. The second is die somewhere unexpected. That is the game.
The first thing anyone does in Fortress Forever is throw a concussion grenade at their own feet, and the second thing they do is die somewhere they did not expect to be.
That is not a mistake. It is the game. Fortress Forever is a free Source-engine remake of Team Fortress Classic built by people who thought Team Fortress 2 had thrown away the movement, and the movement is the reason it still exists. You are meant to detonate grenades under yourself, ride the blast across half a map, and arrive at the enemy flag going considerably faster than anyone can react to.
It is also very small. There are six servers listed here, and that number is not going to surprise anybody who follows Source mods. Read the honest assessment near the bottom of this page before you set aside an evening.
What it actually is
Team Fortress Classic was a Half-Life mod that became one of the most demanding class shooters ever made, mostly by accident. Its movement had exploits in it β bunnyhopping, conc jumping, rocket jumping β and the players who stayed treated those exploits as the point. When Team Fortress 2 arrived in 2007 as a slower, friendlier, art-directed thing, a sizeable group of TFC players decided they had been left behind.
Fortress Forever is what they built. Same nine classes, same flag maps, same grenade rules, running on Source rather than GoldSrc so it renders this century. The Team Fortress Classic servers guide covers the ancestor if you want to see where all of this came from.
It is free. It has always been free. That is worth saying plainly because a lot of people assume any Source mod with this much work in it must cost something.
The nine classes and what each is for
Class limits are set per server, so a full team is a negotiation rather than a free-for-all.
Scout is fast, fragile and the standard flag carrier. Scouts also disarm the traps other classes leave lying about, which makes them more than a delivery service.
Soldier has the rocket launcher and therefore rocket jumps. Slow on foot, extremely mobile once you accept the self-damage.
Demolition deals in explosives you place rather than fire β pipe traps laid across a corridor, and a charge you set, then run away from and detonate. A well-placed trap kills three people who were all sprinting.
Medic heals teammates and does something considerably nastier to enemies. Medics are also quick, which means a good one spends as much time attacking as patching people up.
Heavy carries the enormous rotating gun. Enormous damage, almost no speed, and completely dependent on somebody else deciding where to point him.
Pyro burns things at close range and is at its best in the confined middle sections of flag maps.
Spy disguises as the enemy and stabs people in the back. Playing spy well in this game is a performance β you have to walk like the class you are pretending to be.
Engineer builds. A sentry gun that grows more dangerous as it is upgraded, and a dispenser that hands out ammunition. The engineer's real skill is choosing where, not what.
Sniper does what snipers do, over the long outdoor sightlines the flag maps all include.
If that list reads like Team Fortress 2, it is because TF2 inherited it. The behaviour underneath is completely different.
Grenades change everything
Every class carries two types of grenade, and you prime them before you throw. Hold the key, the fuse starts, release it and it goes. Holding too long kills you.
Concussion grenades do not do meaningful damage. They shove you. Land one under your own feet at the right moment and you cross a gap no class can walk across, and the technique of chaining several together is what separates people who have played this for a week from people who have played it for a decade.
Learn to conc jump on an empty server before you try it in front of anyone. There is no shame in this. Everybody did it.
What a round actually looks like
Capture the flag is the dominant mode, and it is not the polite version of capture the flag you may be picturing.
The classic layout is two mirrored bases joined by a shared middle. Your flag sits deep inside yours, behind a defence that has had time to set up, and theirs sits in the mirror image of that. A successful run is one player moving through the middle at speed, surviving the defenders, grabbing the flag and getting back out along a route the defence has not covered.
ff_2fort is the map everybody knows, because 2fort in one form or another has existed in every game in this lineage. Two forts, a bridge, a basement, and a sniper on each battlement making the direct route unattractive.
The important thing to understand is the shape of the roles. Offence is two or three fast classes running the same route over and over, learning the timings. Defence is an engineer's sentry gun covering the approach, a demolition class trapping the corridor behind it, and somebody heavy standing where the flag is. Neither side wins by out-shooting the other. They win by out-timing them.
Rounds run long. A capture that took eleven attempts is normal, and the eleventh one works because the defence has been slowly ground down rather than because anybody got lucky.
Server settings vary more than you would expect for a game this size. Class limits, grenade rules and whether certain movement techniques are left alone are all things a server owner decides, and two servers running the same map can feel like different games. Spend a round watching before you conclude that you are bad at it.
Getting hold of it
Fortress Forever has had two distribution lives, and which one you meet depends on where you look.
For most of its history it was a manual download that installed into a Source runtime you got separately through Steam β the same arrangement every Source mod of that era used. Later it appeared on Steam as its own free entry, installable from the store page like any other game.
Search the Steam store for it first. If it is there, that is the route to take, because Steam will keep it patched and the server browser will work the way you expect. If you end up with a manual download instead, follow the instructions that come with it rather than anything you read here β the layout of those packages changed several times, and a stale instruction is worse than none.
Either way you need a Steam account.The account comes first, and our Steam guide covers making one properly.
Disk space is modest. This is a 2007 Source mod, not a modern shooter.
Turn the console on before you do anything else
You need the developer console to join a server by address, and every troubleshooting instruction ever written for a Source game starts with opening it.
The setting is in the game's options, under the advanced keyboard settings, in the same place Source games have always kept it. Alternatively, add -console to the launch options through the game's Properties in Steam, which forces it open at startup.
Check that the tilde key opens it before you go looking for servers. Finding out that it does not while you have a copied address on your clipboard is annoying.
Connecting to a specific server
The in-game browser lives under the multiplayer menu and lists what it can find. With a game this size, the whole list fits on a screen.
To join directly, open the console and type connect, a space, and the address:
connect 51.79.148.62:27015
Copy the port along with the IP. 27015 is the Source default and a host running several servers on one machine has moved most of them elsewhere. This catches people constantly, and the failure is silent β the game just sits there and then gives up.
Our Fortress Forever list queries each server directly rather than trusting what it claims about itself, which matters more for a small game than a large one. When there are six servers, one lying about its player count distorts the entire picture. What makes a server listing trustworthy goes into why measured counts and claimed counts diverge.
The browser's Favorites tab accepts an address directly. With a game this size, favourite everything. You are not going to run out of room.
The honest part
Six servers is not a population. It is a handful of machines kept alive by people who care, and on an average afternoon several of them will be empty.
This is not a reason to skip the game, but it is a reason to adjust what you expect from it. Small Source mods do not work like big games. They work on schedules.
What that means practically: the community organises. Games happen because somebody said "9pm Thursday" somewhere and enough people turned up. If you install this, find out where that arrangement is being made and join it, because turning up unannounced at a random hour and finding nobody home is what makes people uninstall a game that is actually fine. Discord did most of the damage and most of the rescuing here β how Discord's changes affected gaming communities covers what happened to small scenes when their forums moved.
Who is this still for? People who played TFC and want it rendered properly. People who like movement shooters and have run out of them. Anyone who found TF2 too slow and Quake too abstract, which is a narrower group than it sounds but a real one.
Who is it not for? Anybody who wants to click a button and be in a game within thirty seconds. That is not what this is.
Problems you will actually hit
Nobody is on any server. Check the time of day and check the region. A six-server game has one busy hour, and if you are in the wrong hemisphere for it you will conclude the game is dead when it is asleep.
The mod will not launch, or launches to a black screen. With a manual install this is nearly always the Source runtime underneath rather than the mod itself. Verifying that runtime through Steam and launching it once on its own fixes a surprising amount.
You connect and immediately fall through the world, or the map looks wrong. Version mismatch between your build and the server's. Small mods do not always update everybody at once.
Your conc jumps go nowhere. Timing, not settings. The grenade has to leave your hand and reach the ground at a specific moment relative to your jump, and the only fix is repetition on an empty server.
Everything feels floaty compared to TFC. Source and GoldSrc do not handle player movement identically and never did. Some TFC veterans never make peace with it.
Where to go next
If the movement appeals but the emptiness does not, the obvious neighbours are all busier. Team Fortress Classic is the original and still has servers running the real thing. Team Fortress 2 is the descendant that went in a different direction and took most of the audience with it.
If it is the Source engine and community servers you have taken to rather than this specific game, Counter-Strike: Source, Half-Life 2: Deathmatch and Garry's Mod all use the identical console, the same connect syntax and the same server culture. Everything you learned here about ports and direct connections works on all of them without a single change.
<!-- joingg-footer -->
---
JoinGG is a live directory of community game servers. Every listing is queried directly every fifteen minutes, so the player count you see was measured rather than reported by its owner, and each one carries a copyable connect address. Fortress Forever servers are listed here, and every game on the site has its own hub. Player counts across every game are on the statistics page, and Fortress Forever's own numbers β servers online, players now, activity by hour β are on its statistics page.
Common questions
- Why does the game fail to connect silently when joining via the console?
- You likely forgot to include the port number with the IP address. While 27015 is the Source default, hosts running multiple servers move them to other ports, causing the game to sit silently and give up.
- How can you fix a black screen when launching a manual install?
- Verifying the underlying Source runtime through Steam and launching it once on its own typically fixes the issue. Black screens on manual installations are nearly always caused by problems with the runtime rather than the mod itself.
- Why do you fall through the world immediately after joining a server?
- A version mismatch between your game build and the server causes this issue. Because small mods do not always update every player and server at the same time, version differences will make maps load incorrectly.
Published Β· 9 min read