5. Choose an Archive Topic

Before you start searching for old websites, downloading files or reconstructing release histories, you need to decide exactly what you are trying to preserve.

This might sound like a simple decision, but it has a significant effect on the entire project. A small, focused archive might take a weekend to assemble. A comprehensive archive covering an entire category of Quake modifications could take months or years.

The goal of this chapter is to help you choose a worthwhile topic, understand the trade-offs between different project sizes and define clear boundaries for your archive.

What makes a good archive topic?

A good archive topic is one that has some historical, technical or community value and is practical enough for you to make progress.

You do not necessarily need to choose a famous modification. An obscure project with only a handful of surviving files might be just as interesting to preserve as a popular modification with hundreds of releases.

Consider a few possible reasons for choosing a topic:

  • Historical significance: The modification was influential, popular or representative of an important period in Quake modding.
  • Personal interest: You remember playing the modification or have an interest in its developers, technology or community.
  • Preservation opportunity: You have discovered files, websites or historical references that might otherwise be lost.
  • Research opportunity: There are enough surviving clues to reconstruct at least part of the project’s history.
  • Community value: Other people might appreciate being able to find, download or learn about the modification.
  • Technical interest: The project contains interesting code, maps, models, tools or gameplay ideas worth studying.

These reasons can overlap. For example, you might choose a modification because you enjoyed playing it in the late 1990s, discover that its original website has disappeared and then realise that several of its releases are missing from existing archives.

That is a promising starting point.

However, interest alone is not enough. You should also consider whether the project is manageable. A topic can be fascinating but so broad that you never finish documenting it.

Different ways to define an archive topic

There are several useful ways to approach an archive. Each produces a different kind of preservation project.

A specific modification

The simplest approach is to choose one particular modification and document its history and releases.

Examples include:

  • Action Quake
  • Threewave Capture the Flag
  • Rocket Arena
  • Team Fortress
  • Quake Rally

A focused project might document the original website, development team, release announcements, version history, downloadable files and related community activity.

This is often the best starting point for a first archive. You have a reasonably clear subject, and you can make meaningful progress without having to investigate the entire Quake modding scene.

For example, an Action Quake archive might aim to identify every known public release of the original modification, recover surviving downloads and reconstruct the project’s development history.

A category of modifications

Instead of choosing one project, you could archive a particular category of modifications.

Examples include:

  • Quake 1 bots.
  • Quake 2 total conversions.
  • Quake 3 capture-the-flag modifications.
  • Quake 1 single-player campaigns.
  • Quake 2 weapon modifications.
  • Quake 3 player models.

A category archive can be especially valuable because it brings together projects that might otherwise be difficult to discover.

For example, an archive of Quake 1 bots could include hundreds of independent projects. Some might have been widely used, while others were small experiments by individual developers.

The challenge is deciding which projects qualify. Does a bot need to be a standalone modification? Do bot libraries and navigation tools count? What about modifications that include bot support as one of several features?

Category archives therefore require more careful scope definition than archives of individual modifications.

A developer or development team

Another approach is to follow the work of a particular developer or team.

For example, you might discover that one developer created several Quake modifications, contributed to other projects and released a collection of tools.

Rather than archiving each project independently, you could create a record of all their known work.

This might include:

  • All known modifications and releases.
  • Maps, models and other contributions.
  • Development tools and utilities.
  • Source code and technical demonstrations.
  • Personal websites and project announcements.
  • Collaborators and development teams.
  • Later projects or contributions to commercial games.

This approach can reveal connections between projects that would otherwise be missed.

It can also be challenging. Developers sometimes used different usernames, collaborated under team names or contributed anonymously. Identifying all their work may require considerable investigation.

A historical collection

You could define your archive around a particular period of Quake modding.

For example:

  • Quake modifications released during 1996 and 1997.
  • Quake 2 modifications from 1998.
  • Quake 3 modifications released between 1999 and 2001.
  • Modifications developed during the early PlanetQuake era.

A historical collection can help document how the modding community evolved over time.

It might capture changes in development tools, distribution methods, popular gameplay ideas and the communities that formed around particular games.

The main difficulty is that historical periods are not always neatly separated. A modification might have started in one year, received updates for several years and continued to be distributed long after development stopped.

You will need to decide whether the archive is based on the original release date, the development period or some other criterion.

A distribution source

You can also build an archive around a particular place where modifications were distributed.

Examples include:

  • Modifications hosted on a particular website.
  • Files distributed through a particular FTP server.
  • Modifications included on PC gaming magazine CDs.
  • Files from a particular collection of shareware or game discs.
  • Projects hosted on a particular community portal.

This is an interesting approach because distribution sources are themselves part of gaming history.

For example, a magazine CD might contain dozens of Quake modifications that are now difficult to find online. Preserving the contents of that CD, documenting the files and identifying their original projects could produce a useful historical collection.

A distribution-source archive may also reveal obscure modifications that would not appear in searches for popular projects.

The main challenge is that the collection may contain many unrelated projects. You will need to decide whether you are preserving the original distribution as a whole, documenting every file or extracting and documenting individual modifications.

Choose between a quick archive and a comprehensive archive

Not every preservation project needs to become a major research undertaking.

It is useful to distinguish between two broad approaches.

Create a quick archive

Small, focused project

A quick archive captures something useful while the information or files are available.

Examples:

  • Documenting a newly discovered release.
  • Preserving files from an old magazine CD.
  • Recording the historical URLs of a vanished website.
  • Creating a basic record of a modification and its known downloads.
  • Publishing a list of files recovered from an old FTP directory.

The objective is to preserve a useful discovery without requiring a complete reconstruction of the project’s history.

Create a comprehensive archive

Long-term research project

A comprehensive archive attempts to reconstruct as much of a project’s history and surviving distribution as possible.

Examples:

  • Identifying every known release.
  • Recovering missing versions from historical sources.
  • Reconstructing a detailed release chronology.
  • Identifying developers and contributors.
  • Recording original download locations and mirrors.
  • Preserving supporting evidence and historical references.
  • Documenting missing files and unresolved questions.

The objective is to create a detailed, defensible historical record that can be extended as new discoveries are made.

A quick archive is not an inferior version of a comprehensive archive. It can be a valuable preservation contribution in its own right.

In fact, a quick archive can become the foundation for a more comprehensive project later.

You might begin by preserving the contents of a single magazine CD. Several months later, you might discover that one of the files belongs to a modification with multiple missing releases. That discovery could become the starting point for a much larger archive.

The important thing is to preserve what you have found rather than postpone the work until you have enough information to create a perfect archive.

Understand the trade-off between narrow and broad topics

One of the most important decisions is how much material your archive will cover.

A narrow topic is generally easier to complete. A broad topic can provide greater value to the community, but it can also become an enormous undertaking.

ConsiderationNarrow topicBroad topic
ExampleOne Quake 2 modificationAll Quake 2 total conversions
Research effortMore manageablePotentially substantial
Historical detailEasier to document deeplyMay need to be selective
File recoveryMore focusedMany more projects and files
CompletionEasier to defineCan be difficult to achieve
Community valueValuable to a smaller audiencePotentially valuable to a larger audience

Consider two possible projects.

Project A: Archive Rocket Arena 2

You decide to document one particular modification. You can focus on its developers, website, releases, patches, maps and historical announcements.

You might eventually identify almost every known release and produce a detailed chronology.

Project B: Archive all Quake 2 arena modifications

You decide to document every arena-style modification released for Quake 2.

This could include dozens of projects, each with its own developers, websites, versions and distribution history. Some projects might have only one surviving file, while others might have extensive release histories.

Project B could be more useful as a community resource, but it would require much more research. You might also find it difficult to decide when the archive is complete.

Neither approach is inherently better.

A useful strategy is to begin with a narrow topic and design the archive so that it can grow. You could start with one modification, then add related projects once you understand the research process and have a working archival structure.

Define the boundaries of the archive

Once you have selected a topic, you need to decide exactly what belongs in the archive.

This is important because modifications rarely exist in isolation. They often have related projects, supplementary files, community contributions and derivative versions.

Consider an archive focused on Action Quake.

Should it include only the original Action Quake 2 modification, or should it also include modern extensions?

What about custom maps created for Action Quake? Should server-side modifications be included? What about patches created by third parties or independent projects derived from the original modification?

There is no universally correct answer. The important thing is to make the decision explicit.

Here are some boundaries you might define.

Decide whether your archive covers only one game or includes related projects for other Quake titles.

For example, an archive of Quake 1 modifications might exclude Quake 2 and Quake 3 projects, even if they share a name, developer or gameplay concept.

Alternatively, you could deliberately create a broader archive covering a modification series across multiple games.

Decide whether to include maps, models, skins, sounds and other content created for the modification.

You might choose to include only official releases, or also preserve community-created additions.

A map designed specifically for a particular modification might be an important part of its history, even if it was distributed separately.

Patches and supplementary files

Decide whether to include patches, fixes, server updates, configuration files and other supplementary downloads.

These files can be important because they document how a project evolved and how players actually used it.

For example, a modification might have a main release followed by several small updates distributed separately. If you preserve only the main download, you may miss important parts of its release history.

Third-party contributions

Decide whether to include work created by people outside the original development team.

This might include:

  • Community maps.
  • Unofficial patches.
  • Alternative game modes.
  • Custom models and skins.
  • Server modifications.
  • Tools and utilities.
  • Unofficial ports and compatibility fixes.

You could include these in the main archive or document them in a separate section.

Derivative projects

Some modifications inspire other projects or are adapted by other developers.

Decide whether these belong in your archive.

For example, a project might use the original modification’s code, assets or gameplay ideas to create a substantially different experience. It may be historically related without being an official release.

A useful distinction is between the original project and related projects. You can document the relationship without necessarily treating every derivative as part of the original archive.

Write down the scope

Do not leave the boundaries of your archive as informal assumptions. Write them down before beginning substantial research.

A short scope statement is usually sufficient.

Your scope statement does not need to anticipate every possible discovery. You can revise it as your research progresses.

For example, you might initially exclude unofficial patches, then discover that one of them was widely distributed and became an important part of the modification’s history. You can update the scope and document the reason for doing so.

The purpose of defining boundaries is not to prevent the archive from growing. It is to make sure that growth happens deliberately rather than allowing the project to expand without direction.

Avoid making the project too ambitious

A common mistake is to begin with an enormous objective.

For example:

I am going to archive every Quake modification ever released.

This is an appealing goal, but it is difficult to turn into a manageable project. There are thousands of modifications, incomplete historical records and many files that may no longer exist.

You could spend years researching without ever feeling that you have made sufficient progress.

A better approach is to define a useful first milestone.

For example:

  1. Identify 20 modifications in a particular category.
  2. Select one modification for detailed research.
  3. Recover at least one original release.
  4. Document its known versions and historical download locations.
  5. Publish the resulting archive.
  6. Expand the collection when the initial project is complete.

This gives you a concrete result while leaving room for future work.

You should also remember that archival completeness is often impossible to establish. There may be releases that were never announced publicly, files that were distributed privately or websites that were never captured by an archival service.

Your objective is to create the best record you reasonably can, not to guarantee that every historical artifact has been recovered.

Your first archival decision

Before moving on, make a decision about the topic you want to archive.

You do not need to know everything about the project yet. In fact, the research chapters that follow will help you discover what material exists and how much work is involved.

For now, write a short project definition containing:

  1. Topic: What modification, category, developer, historical collection or distribution source will you archive?
  2. Reason: Why is this topic worth preserving?
  3. Approach: Are you creating a quick archive or planning a comprehensive historical archive?
  4. Included material: What projects, releases, files and related material belong in the archive?
  5. Excluded material: What will you deliberately leave outside the project?
  6. First milestone: What is the smallest useful result you want to publish?

Chapter summary

Choosing an archive topic is the first step in turning an interest in Quake history into a practical preservation project.

The main ideas from this chapter are:

  • An archive can focus on a specific modification, a category, a developer, a historical period or a distribution source.
  • A quick archive can preserve a useful discovery without requiring comprehensive research.
  • A comprehensive archive attempts to reconstruct a project’s history and recover as many known releases as possible.
  • Narrow topics are easier to complete and research in depth. Broad topics can offer greater community value but require considerably more effort.
  • Every archive needs explicit boundaries covering related projects, maps, patches, third-party contributions and derivative work.
  • A realistic first milestone helps prevent the project from becoming too ambitious.

Outcome: You have selected an archive topic and defined what is inside and outside its scope.

In the next chapter, you will turn that decision into a practical directory structure for storing research notes, historical evidence, recovered files and the published archive.