Fortress-Forever News

Dev. Journal: squeek.

fortressforever@gmail.com (squeek.) — Mon, 03 Apr 2023 16:57:56 GMT

I wrote a blog post about the technical details of movement on downward slopes:

Source vs GoldSrc Movement: Downward Slopes

Here’s a snippet:

The slope-related movement physics in the GoldSrc (Half-Life 1) engine and the Source (Half-Life 2) engine are fairly similar. However, there is one caveat around moving down slopes: in the GoldSrc engine you will bounce down slopes somewhat often, while in the Source engine you will smoothly move down almost any slope unless you collide with them while moving extremely quickly.

Dev. Journal: squeek.

fortressforever@gmail.com (squeek.) — Wed, 29 May 2019 19:30:52 GMT

I wrote a blog post about the technical details of rampsliding:

Rampsliding Is a Quake Engine Quirk in the Same Way That Bunnyhopping Is

Here’s a snippet:

The obvious assumption would be that [rampsliding] is an intentional feature that uses things like the slope of the surface and the player’s velocity to determine when a player is rampsliding, but that is not the case. In fact, in the same way that bunnyhopping was likely an unintentional quirk of the ‘air acceleration’ code, rampsliding was likely an unintentional quirk of the ‘categorize position’ code.

News: 10 Years of Fortress Forever

fortressforever@gmail.com (Fortress Forever Team) — Wed, 13 Sep 2017 00:32:37 GMT

Development of Fortress Forever started in 2004, and version 1.0 was released on September 13, 2007. Today marks ten years since that initial release.

In those ten years, Fortress Forever has seen:

18 patches
88 volunteer developers
Hundreds of community maps
3,948 code commits by 24 different programmers
7,860 asset commits by 59 different developers
8,477 page edits on the FF wiki
17,801 pickup games in #ff.pickup
23,374 threads on the FF forums
146,341 downloads since the Steam release (March 2015), and an unknowable number of downloads before then (download numbers weren't tracked)
Millions of collective hours played

To celebrate, let's take a look back through the years via various videos made by the community in that time:

Thank you to everyone that has played and supported this game--you are what has allowed FF to reach this milestone.

News: FF v2.7 Released: The Pyro Overhaul Patch

fortressforever@gmail.com (Fortress Forever Team) — Sun, 11 Sep 2016 16:36:45 GMT

Some highlights of the patch notes:

Pyro now has a jetpack and an overhauled damage system
Kill assists have been added
Fixed a long-standing collision bug with bullets/projectiles

The full changelog is available here

News: FF 2.7 Teaser: Pyro Overhaul

fortressforever@gmail.com (Fortress Forever Team) — Wed, 13 Jul 2016 15:29:07 GMT

Pyro overhaul patch coming soon. Here is a teaser showing a little bit of what is possible using his new jetpack.

News: Fortress Forever 2.5.0 released!

fortressforever@gmail.com (Fortress Forever Team) — Fri, 27 Mar 2015 10:20:00 GMT

Hello Steam!

Download

Full changelog

Misc Resources

News: Preparing For Release

fortressforever@gmail.com (Fortress Forever Team) — Tue, 24 Mar 2015 20:10:00 GMT

Fortress Forever will be released on Steam in 3 days. Here is some info that will help to prepare for that.

The dedicated server files are publicly available

The Fortress Forever dedicated server is now available via steamcmd with anonymous credentials. Server owners that are running a Fortress Forever 2.46 server should migrate to the Steam version before Friday (preferably sooner, to allow for adequate testing).

See this thread for more details

The Steam Store page and Community Hub have launched

Migrating your settings to the Steam version of the game

For all those with Fortress Forever 2.46 installed, here's a guide to migrating your settings over to the Steam version:

Migrating from Fortress Forever 2.46

News: Yet Another Long Overdue Update

fortressforever@gmail.com (Fortress Forever Team) — Fri, 20 Mar 2015 20:24:15 GMT

As weeks turn into months, we are finally ready to make some more announcements.

Fortress Forever will be released on Steam March 27th

One week from today, Fortress Forever will be available to download (for free) on Steam.

Fortress Forever is now open source on Github

The code, scripts, and maps of Fortress Forever are publicly available and open to contributions. Check out the Contributing to Fortress Forever page to see how you can help.

Additional resources:

Fortress Forever has a new website

fortress-forever.com has been redesigned and updated to be more relevant to the current state of the game.

Mapping Contest: ff_volleyball makeover

ff_volleyball is a fun little map that needs an aesthetic upgrade before it can be included with the game. Check out this thread for all the details.

Dev. Journal: squeek.

fortressforever@gmail.com (squeek.) — Fri, 17 Oct 2014 19:46:01 GMT

Uhh... hello?

So, what has happened in the last year? Well, unfortunately, not a whole lot.

When FF was first Greenlit, we thought it would be best (and also thought it was required of us) to upgrade FF to the latest version of the Source engine. We started work on that, but our enthusiasm faded fairly quickly; porting FF requires a lot of work, and our goal was to fix/improve things as we upgraded. You can gain some insight into what we wanted to do by visiting our never-made-public website about the upgrade. Note also that we'll be open sourcing this upgrade attempt, although it is still in the very early stages.

After development stalled on the port, we weren't really sure what to do. There were talks of waiting for the Source 2 engine or potentially moving to a different engine entirely, but that never really ended up going anywhere.

Since then, there's been a whole lot of nothing. I basically became a hermit and hid away from the forums/IRC/Steam/etc. I didn't think it was possible to release on Steam without doing some sort of engine upgrade, and 'ffded' was becoming a legitimate reality. It's very fortunate that Neotokyo has been able to pave the way with regards to releasing a Source SDK 2006 mod on Steam, as this period of inactivity may have just continued indefinitely without that knowledge (big thanks to KubeDawg for pointing out Neotokyo's Steam release).

On another note, I'm not quite certain what my future with Fortress Forever will entail. I've been working on this mod for 6 years now, and my enthusiasm has (clearly) been waning. However, I'm very curious to see what will come of the Steam release, and, who knows, maybe I'll get a second wind. There were a lot of experimental changes that we tried at one point or another in the closed beta that never made it into a release, and with the public beta that Steam distribution will allow us to run, it might be fun to revisit some of those ideas and get some more feedback on them.

That's about it. Just wanted to try to give everyone some info about what went on during this rather strange period of FF's development.

News: A Long Overdue Update

fortressforever@gmail.com (Fortress Forever Team) — Fri, 17 Oct 2014 19:42:27 GMT

It's been nearly a year since Fortress Forever was Greenlit, and there's been a total lack of updates since then. To remedy that, here are two things that will be happening in the coming weeks:

The current version of Fortress Forever will be released on Steam
The Fortress Forever code will be made open source on Github

Why did it take a year for this to happen?
We didn't think it was possible to release the current version of FF on Steam because we thought that the version of the Source SDK that FF uses was too old. Neotokyo proved otherwise, and we are able to follow their lead and finally release FF on Steam.

What does 'released on Steam' mean?
It means that you'll be able to install Fortress Forever directly through Steam and that you will receive updates automatically. As always, Fortress Forever will be completely free.

Why go open source?
Fortress Forever's development has been largely opaque for a huge majority of the playerbase for a very long time, and the reason for that opaqueness has not always been intentional; attempting to keep everyone informed can be pretty labor intensive. By moving our development entirely into public view, it will be easier for everyone to stay in the loop with what will be happening with the game, and will give everyone a chance to participate directly in the development process.

News: Fortress Forever has been Greenlit!

fortressforever@gmail.com (Fortress Forever Team) — Sun, 27 Oct 2013 12:30:36 GMT

Fortress Forever has been Greenlit by the community! Thank you to everyone that voted and helped to spread the word about our mod. Being Greenlit was considered something of a long shot, and we are thrilled to see it happen.

What does this mean for FF?

It means that sometime in the future, you'll be able to install Fortress Forever directly through Steam and you will receive updates automatically.

When will that happen?

Unfortunately, this is still something we are trying to figure out. It could be soon, or it could be not soon at all, depending on some information we are still waiting to find out. Sorry to be so ambiguous. Once we get more information, we'll be able to let you know with more certainty what will be happening.

For anyone having trouble connecting to servers or having trouble compiling maps, see this thread

News: Steam's New Content System and FF

fortressforever@gmail.com (Fortress Forever Team) — Tue, 15 Oct 2013 21:56:00 GMT

If you try to launch Fortress Forever, you might be prompted to update Source SDK Base 2006 to Steam's new content system. Doing so will move some base Source engine files around (but not mess with your Fortress Forever at all). If you are not prompted, then you'll need to force your Source SDK Base 2006 to update in order to be able to connect to servers:

In Steam, go to Library, select Tools from the dropdown, find Source SDK Base 2006, right click it and go to Properties. In the properties window, go to the Local Files tab and click "Verify Integrity of Tool Cache"

That should update you to the new Steampipe file system and then you should be able to connect to servers.

For server owners, you now need to use SteamCMD to install the Source Dedicated Server files (appid 205). For a tutorial, see How to install a SRCDS. If you don't manually manage your server, you will need your server provider to update your game server to the new content system.

For mappers, you might not be able to compile maps until you copy steam.dll from steamapps\common\Source SDK Base to steamapps\<username>\sourcesdk\bin\ep1\bin. Thanks to Uly for finding this fix.

Dev. Journal: squeek.

fortressforever@gmail.com (squeek.) — Sun, 19 May 2013 01:31:26 GMT

As discussed in a recent dev journal, a client-only bugfix patch (version 2.46.1) has been released using our new auto-updater. You should be prompted to update next time you load the game. Let me know if you have any trouble using it.

Here is the changelog (which can also be found on our changelogs page):

Bug Fixes
Fixed a bug that made the team menu disappear if you joined a server and toggled the scoreboard while still looking at the MOTD

Fixed cloak screen effect being drawn while in a slowfield instead of while cloaked

Reverted cl_ragdolltime fix because it caused unexcepted problems; removed the cl_ragdolltime cvar temporarily

Fixed first-person spectator view going insane if the player you're spectating dies while concussed

Also, for anyone that needs or just prefers it, here is an .exe installer for 2.46.1 (to patch from 2.46 to 2.46.1):

http://www.fortress-forever.com/files/246/FF_2.46.1_Patch.exe

Dev. Journal: squeek.

fortressforever@gmail.com (squeek.) — Mon, 13 May 2013 21:54:24 GMT

Just wanted to write a quick little journal about some bugs found in 2.46 and what we plan to do about them. These are all client-side changes and therefore we are planning to release a client-only hotfix (2.46.1) using our newly implemented auto-updater as soon as we get all the bugs squashed.

Bug: If you join a server and toggle the scoreboard before closing the MOTD, the team menu doesn't show up when you close the MOTD.
Status: Fixed
Bug: While in a slowfield, the cloak screen effect gets incorrectly applied. While cloaked, the cloak screen effect is not applied.
Status: Fixed
Bug: While first-person spectating someone that dies while concussed, your view goes absolutely insane in between them dying and them respawning.
Status: Working on a fix

In addition, the fixed cl_ragdolltime cvar has caused a few new bugs (CL_CopyExistingEntity errors and "cl_ragdolltime 0" spawning floating player models in the center of the map). Unfortunately, the fix for the CL_CopyExistingEntity errors is rather involved and will require some fairly significant changes in how ragdolls are handled. Therefore, we will rollback the cl_ragdolltime "fix" that was put in 2.46 (and temporarily remove the cvar since it will no longer work) and work on a more robust fix for the next patch.

If you are aware of any other bugs in 2.46, let us know.

News: 2.46 Released!

fortressforever@gmail.com (Fortress Forever Team) — Mon, 06 May 2013 13:43:37 GMT

Bug fixes, bug fixes, bug fixes! This patch is long overdue, but it's finally here. Also, don't forget to vote for us on Steam Greenlight if you haven't already.

2.46 Changelog

New gib effect

Download

News: FF on Greenlight

fortressforever@gmail.com (Fortress Forever Team) — Sun, 20 Jan 2013 09:46:00 GMT

First of all, at long last, Fortress Forever has been submitted to Steam Greenlight (read about Steam Greenlight). If FF gets Greenlit, you would be able to install and update Fortress Forever through Steam like you would a commercial game. Because Fortress Forever is still being actively developed, this is actually a big deal. It would both make it easier for players to install and update the game and easier for us to release updates.

Please feel free to encourage your friends to vote for FF on Greenlight.

Also, a new bug fix patch will be coming soon (with many fixes relating to spectating). Be on the look out.

News: 2.45 Released!

fortressforever@gmail.com (Fortress Forever Team) — Sun, 09 Dec 2012 06:57:30 GMT

It has been nearly a year since the last patch, but we're still alive and kicking. This update brings some much needed/long-awaited changes (new class selection screen) as well as bug fixes, balance tweaks, and a large amount of added Lua scripting functionality.

2.45 Changelog

Download

News: 5th Anniversary

fortressforever@gmail.com (squeek.) — Thu, 13 Sep 2012 15:39:47 GMT

Fortress Forever was released 5 years ago to the day. This post is way overdue, but I want to take some time to thank everyone that has helped FF over the years.

A gigantic thanks to all the developers that came and left before I joined the team. Seriously, I don't think I can possibly express the gratitude they deserve. The scope of this mod is truly unbelievable and they did an amazing job.
Thank you to AfterShock, GreenMushy, Dexter, caesium, Crazycarl, Elmo, and all the rest of the current dev team for sticking with the game through some bleak times
Thank you to Bully for providing us with fantastic voiceover work (announcer and training voiceover). Sorry if we didn't show enough appreciation, your contributions have been invaluable.
Special thanks to anyone that has stuck with the game since 1.0
Thank you to everyone that has helped populate public servers all this time
Thank you to anyone that has hosted a FF server
Thank you to Scuzzy and the O-T clan. No matter your opinion on them, they have supported the game since before release and have helped FF countless times over the years (running the FF beta server, hosting the website for a time, etc, etc).
Thank you to []Zer0 and infy for supporting #ff.pickup and helping it survive all these years (and everyone that has hosted a server for #ff.pickup)
Thank you to Dr.Satan and PoC/marxist for running successful seasons of UGC
Thank you to everyone that has stuck with #ff.pickup since it started (the_cake, rodox, Hoopajoo, hadeZ, SiSCoS, GreenMushy, exoskeletaL, WATER, VinnyTheBoss, R00Kie [come back!], BananaHammock) and to everyone that has played in pickups over the years
Thank you to everyone that played in the Quakenet #ff.pickup channel before the channels merged (sadly, I'm not as familiar with these players)
Thank you to anyone that has helped promote FF in any way
Thank you to ryu^ for making Fortress Forever - The Movie
Thank you to anyone that has made a FF video (off the top of my head: 1337CaLeB, FDA, Lateralols [POTMs], SiSCoS, Hoopajoo, caesium, ryu^, Mase)
Thank you to Jiggles and Dr.Evil for helping me out with code edits while I was on the beta team
Thank you to NeoNL, R00Kie, and nine` for being the nicest and most helpful people of all time
Thank you to the_cake and rodox for being tremendous helps while beta testing and giving valuable feedback
Thank you to all current and past beta team members (2.1 beta testing was the most fun I've ever had playing FF; those epic rounds of hunted were amazing)
Thank you to anyone that has made a map for FF (of particular note: zE)
Thank you to anyone that has made custom models/textures/HUD elements/etc for FF (of particular note: Jester)
And finally, thank you to anyone that has done so much as played and enjoyed Fortress Forever in the past 5 years

We've come a long way, but we still have a long way to go. I hope you'll continue to support the mod in any way you can. It means a lot.

Dev. Journal: squeek.

fortressforever@gmail.com (squeek.) — Tue, 26 Jun 2012 16:13:19 GMT

As KubeDawg suggested, since we probably won't get Steamworks support, including our own auto-updater would be nice. I've been looking into doing just that over the past few days and might have found something that could work. Here is a quick test of a dummy update:

This is using wyUpdate, a free, open-source auto-updater. However, the program used to create the actual updates (the development team side of things) is not free. Each license is $86, which we might need only 1 of, but I'm not sure yet.

For now, I'll continue looking to see if there are other options, but I just wanted to share that it definitely seems possible.

News: The Steamworks Situation

fortressforever@gmail.com (squeek.) — Thu, 21 Jun 2012 18:12:47 GMT

Steamworks is an API intended to help with developing and publishing a game or mod. If Valve gives you access, it means that your game/mod will be distributed by Steam and will have access to features like achievements and matchmaking, among other things. Essentially, though, if we were granted access, it'd mean you could update or install Fortress Forever using Steam just as you would update or install a commercial Valve title. Unfortunately, Valve never contacted us about being included when they were inviting other Source mods to be part of the program.

After a lot of uncertainty surrounding the issue, we now have something definitive. This is the last correspondence with Valve we have had regarding Steamworks. I replied and asked for some clarification but have gotten no response.

Originally posted by ValveThank you for submitting “Fortress Forever” for potential Steam distribution. We have taken a look at the information provided and determined that Steam is not a good fit for distribution. It is our company policy not to provide specific feedback on a submission but we would like you to consider Steam distribution for your future products.

The way I see it, this can mean one of a few things:

Fortress Forever is ineligible for Steamworks for some specific reason

Reasons could include things like:
- We need to be on the 2007 engine to be eligible for Steamworks support
  - I don't believe this is a requirement for Steamworks, as I think a mod has gotten Steamworks support while on the 2006 engine
- We are not popular/established enough to be eligible for Steamworks support
  - If the mods that have received Steamworks support are any indication, this (hopefully) shouldn't apply to Fortress Forever. We've been actively developing the game for almost 5 years and have maintained a small but loyal playerbase
Whatever the reason, though, it seems like if there is some requirement that we do not meet, then it'd be nothing but beneficial for them to let us know what that is so that we could work on those specific aspects and re-apply.
Valve has some sort of grudge against this mod specifically and/or doesn't want it to "compete" with TF2

While this would make for a good pity party/movie plot, I don't think there is any evidence to support this.
Valve is moving away from supporting mods in general

Unfortunately, I think this is the most likely answer. Mod support from Valve has been getting increasingly small over the past years. Here's a select few things that point to this:
- Zero mods have received Steamworks support since around 2009
- When using Create a Mod in Source SDK to create a 2007 (OB) engine mod, it gives you source code that doesn't compile because it is missing files. This has been the case for a while and has not been fixed
- The 2009 engine update has not received mod support (the Portal 2 engine with Mac support); it seems likely at this point that it never will
- Mods are somewhat buried in the Steam store (as a "fun" game, try to find Fortress Forever's Steam store listing without searching for it directly), and the Steamworks mods have been removed from the Library tab if they are not installed
- The hlcoders mailing list, where you used to be able to get responses from Valve employees about Source mod programming, has been almost entirely abandoned by Valve

Essentially, this boils down to the fact that we probably won't be getting Steamworks support. However, Steamworks support isn't as big of a deal as it once was and is more likely to get worse for mods over time (due to #3 above) rather than better. It seems unclear at this point if getting on Steamworks would even increase FF's visibility in the Steam UI.

I'd love to be proven wrong and see Valve release updated tools and a new mod-supported engine version. In the meantime, though, we'll keep plugging away at improving Fortress Forever. With Steamworks no longer in the picture, we must make our own way forward, meaning that community support is as necessary as it's ever been. If you'd like to help us out with anything, let us know on the forums.

Also, be on the look out for a new patch in the near future (give or take a few soon's).