Post

Here's an update on Quiver Fortress and the base that powers it: Source SDK BDS Base. In the past, I announced that Quiver Fortress was back in development after a couple weeks of the project being shelved. Although this was indeed the case, one of the biggest issues was the fork the mod is using.

There are various issues with the repository, that cannot be easily fixed without resetting the entire repository. These include: - All the PRs are not credited properly. PRs should be properly co-authored and they aren't implemented here that way. Referencing the PR number isn't enough.

- The code is in ifdef hell. Implementing PRs in the first place is a complete pain in the ass because it MUST be in a #ifdef BDSBASE tag. - Confusing feature integration. The current version of BDS Base has a bunch of features that, although they are useful, are difficult to fully implement.

Today I'll be remaking the branch from scratch. It will be temporarily deleted, then re-uploaded info its own standalone repo. Then, I'll be reforking the Source SDK repo. This will allow for much faster development of the fork without going through the handiwork of adding every feature in manually

However, this also means that the development of Quiver Fortress and other projects on the BDS Base would have to restart from scratch. Unfortunately, I have lost a lot of my motivation to work on the project, and not a lot of ideas were created other than "remove bunnyhopping".

As a result, the Quiver Fortress project has been cancelled, for real this time. SURVIVOR II isn't affected by this as it hasn't moved forward in development, as more time was put on the fork and Quiver than that project.

While there was an effort in tightening up the goals for Quiver, the problem was that it would involve undoing a lot of the work already done on the mod. Quiver still had no identity even after the push to work on it further.

While I want to do more experiments, this mod failed because it was more an experiment than a tighty wound experience. BDS Base will also focus more on enhancing the engine its a fork of, rather than building on it.

The problem with the fork was the idea that the user could reset the fork back to the initial release of the TF2 SDK if they wanted to. The thing is: why would anyone do that? If you're modifying the fork anyways, what's the point?