15. Contact People for Historical Files

So far, this guide has focused primarily on finding files through websites, archives, FTP servers, CD-ROM collections and other publicly accessible sources. There is another resource that can be even more valuable: people.

Former Quake developers, contributors, players and archivists may have files that were never publicly distributed or that have disappeared from every surviving archive. These can include original releases, beta versions, development builds, source code, website backups, documentation and supplementary material.

In my experience, contacting people directly has been one of the most successful ways to recover rare Quake files. It is also one of the most labour-intensive approaches. Finding the right people, locating working contact details and getting a response can require considerable effort.

This chapter describes how to identify potential contacts, organise your outreach and make the most of the connections you establish.

Identify Who Might Have the Files

Start by building a list of people who were involved with the modification or its surrounding community.

Do not limit your search to the developers listed on the original project website. Many other people may have retained useful files.

Look for the following groups.

Original developers

Identify the people who created and maintained the modification. This includes:

  • Project leaders and coordinators.
  • Programmers and source code contributors.
  • Level designers and mappers.
  • Model and texture artists.
  • Sound designers and musicians.
  • Website administrators.

Developers are particularly valuable because they may have retained original release archives, development versions, source code, build scripts and project documentation.

Additional contributors

Many modifications attracted contributions from people outside the original development team. Look for people who created:

  • Additional maps and map packs.
  • Player models and skins.
  • Weapons, models and textures.
  • Guides, manuals and documentation.
  • Patches and compatibility updates.
  • Custom game modes and extensions.

These contributors may have retained their own work, including versions that were never incorporated into the main release.

Beta testers and community members

People who tested early versions or participated in the modification’s community may have retained beta releases, test builds, patches and other files.

Also consider server administrators, clan members, tournament organisers and long-time players. They may have collected files for running servers, organising matches or maintaining community websites.

Other Quake archivists

Identify people who have spent years collecting Quake files. Some maintain public archives, while others have extensive private collections.

They may have the exact files you need, or they may know other collectors who can help. Their knowledge of historical FTP servers, mirrors and distribution networks can also provide valuable research leads.

Find Potential Contacts

Use the information already collected during your research to identify people.

Useful sources include:

  • Original project websites and team pages.
  • Readme files and release documentation.
  • Source code repositories and file headers.
  • News articles and interviews.
  • Usenet messages and forum discussions.
  • Credits in maps, skins and other contributions.
  • Historical community websites.
  • Old FTP listings and archive documentation.
  • Links to personal websites and developer pages.

Pay particular attention to usernames, email addresses and personal website URLs found in old files. A developer’s original email address may no longer work, but their name or username may help you find a more recent contact method.

Search for the person’s name and known aliases. Try combinations with terms such as Quake, the modification name, mapping, development and modding.

Do not assume that two similar usernames belong to the same person. Look for supporting evidence, such as matching email addresses, project credits or links between websites, before treating an identity as confirmed.

Also search community discussions for people who mention the modification or its developers. Someone who was not directly involved in development may still know how to contact the original team.

Build a Contact Spreadsheet

Maintain a spreadsheet of everyone you identify. This is important because contacting people can become a substantial research activity involving dozens or even hundreds of potential contacts.

A useful spreadsheet might contain the following columns:

ColumnDescription
NamePerson’s name, if known
UsernameHistorical or current online identity
RoleDeveloper, mapper, tester, archivist, etc.
ProjectModification or community they were associated with
EmailKnown email address
Other contactFacebook, Twitter, Discord, forum profile, website
SourceWhere you found their details
Contact attemptedWhether you have tried contacting them
Contact methodEmail, social media, forum message, etc.
ResponseNo response, bounced, replied, inactive, etc.
Relevant filesWhether they have material that may help
NotesAdditional information
ReferralsOther people they recommended contacting

Track every attempt, even when it fails.

For example, an email may bounce, a social media account may be inactive, or someone may respond that you have contacted the wrong person. Record these outcomes so you do not repeatedly try the same unsuccessful method.

You may eventually find another contact method or discover that someone else has taken over an old website or account.

Keep the spreadsheet under research/, for example:

research/
    contacts.xlsx

You can also use a CSV file or a simple Markdown table. The important thing is to maintain a central record and work through it systematically.

I exclude spreadsheets like this from the public archive project to ensure the contact details I track down remain private. I recommend that you take a similar respectful approach.

Exhaust Public Research Before Contacting People

I recommend leaving direct personal outreach until relatively late in the research process.

There are two reasons for this.

First, contacting people is time-consuming. You may need to track down old developers, find current contact details, send messages and wait for responses. It is better to exhaust the publicly available sources first.

Second, you should know exactly what you are looking for before asking someone to search through old backups.

By this stage, you should have:

  • Identified the known releases.
  • Located all publicly available copies.
  • Identified missing releases and versions.
  • Recorded known filenames and alternative names.
  • Identified missing documentation and supplementary files.
  • Established which files are particularly rare or valuable.

This allows you to make a focused request.

For example, rather than asking a former developer whether they have any old Quake files, you might ask whether they still have the original version 1.2 release archive, an earlier beta build, or the source code for a particular release.

Prioritise the rarest and most valuable missing material. Do not ask someone to search for files that are already readily available from public archives.

Reach Out to the Community

Before contacting individuals directly, introduce your archival project to relevant communities.

Look for Quake forums, Discord servers, mapping communities and other online groups where long-time players and developers might still participate.

Explain what you are doing and why. Be specific about the modification, its history and the files you are trying to recover.

For example, you might explain that you are reconstructing the release history of a particular Quake modification and are looking for original archives, beta versions, patches and documentation.

Ask whether anyone has relevant files or knows someone who worked on the project.

Community engagement can produce unexpected leads. Someone might recognise a developer’s old username, remember a forgotten FTP server or know of a collector with a large backup of historical Quake files.

Do not restrict your search to one community. Different groups have different members and historical knowledge. A mapper community might know someone who contributed maps to your modification, while a general Quake archive community might know someone who preserved its original releases.

Contact Specific Individuals

Once you have identified potential contacts, reach out to them individually.

Try the contact methods available to you:

  • Email.
  • Facebook.
  • Twitter.
  • Discord.
  • Historical community forums.
  • Personal websites and contact forms.

An old email address may no longer work, but the person might still use the same username on a modern platform. Try multiple reasonable contact methods where appropriate.

Keep your initial message short and specific. Explain:

  1. Who you are and what you are researching.
  2. Why you believe they may be connected to the project.
  3. What files or information you are looking for.
  4. That even a small amount of information could be helpful.

Avoid sending a long list of questions or asking someone to undertake a substantial search immediately.

If they respond positively, explain exactly what you are missing and ask whether they might have retained any relevant material.

Ask about old storage media

People often forget what they have retained from earlier computers. Ask specifically about old backups and storage devices.

Useful places to look include:

  • CD-ROM backups.
  • Floppy disks.
  • Old hard drives.
  • External backup drives.
  • Old desktop computers.
  • Laptop backups.
  • ZIP disks and other removable media.

A former developer might not have a folder of old Quake releases readily available, but they may still have an old backup CD containing their development directory.

Even if the original computer no longer works, its hard drive may still be readable using another machine or suitable hardware.

Be specific about the likely files and approximate time period. This makes it easier for someone to decide whether looking through old storage is worthwhile.

Be Patient, Kind and Grateful

Remember that people are doing you a favour. They may need to spend considerable time searching through old computers, backups and storage media.

Be polite, patient and appreciative. Do not pressure people for responses or expect them to undertake extensive recovery work.

If someone finds files, thank them and explain how the discovery contributes to your archive. If they do not have anything useful, thank them for checking anyway.

Some people may be interested in the historical project and willing to help further. Others may simply want to answer your question and move on. Respect their preferences.

Also ask whether they know anyone else who might have relevant files. A referral from someone who worked on the project can be much more valuable than another cold contact.

Keep track of these referrals in your contact spreadsheet and add new people to your list.

Expect a Low Response Rate

One of the most important things to understand is that contacting people is a numbers game.

In my own experience, I have had considerable success recovering rare files directly from former modification developers and old Quake archivists. However, the effort required is substantial.

As a rough personal estimate, perhaps one in fifty people listed results in a working connection, such as a valid email address or a successful message exchange. Of those who respond, perhaps half have old files that are useful.

These are not formal statistics, but they illustrate the amount of effort involved.

You may identify hundreds of potential contacts and receive very few useful responses. Some email addresses will bounce, some accounts will be inactive, and some people will simply not reply.

Do not let this discourage you. A single successful contact can recover files that would otherwise be permanently lost.

Work through your contact spreadsheet systematically. Try alternative contact methods when appropriate, record the results and follow referrals. Over time, even unsuccessful attempts can help establish a better picture of the people and communities involved in the modification.

A Sample Email

The initial email should be friendly, brief and specific. You want to explain the project, establish why you are contacting this particular person, and make it easy for them to respond. Avoid asking for everything they might possibly have in the first message.

Hi [Name],

I hope you don’t mind me getting in touch. I’m putting together an archive documenting the history of Quake modifications, and I’m currently researching [Modification Name].

I came across your name while looking into the project and understand that you were involved as [their role, if known]. I thought you might be able to help with one particular part of its history.

I’m trying to recover a copy of [specific filename or release], which appears to have been released around [year]. I’ve found references to it, but haven’t been able to locate an actual copy.

Do you happen to have this file, or know where I might be able to find it? It may be sitting on an old hard drive, backup CD, FTP backup or somewhere else among your old files. Even a lead on where it might have been stored would be very helpful.

The aim of the archive is to preserve these old releases and document their history so they remain accessible to the Quake community. I’d be happy to acknowledge your contribution in the archive. The archive is located here: [link to your archive, if published by this point]

Thanks very much for your time, and for any help you can offer.

Best regards,

[Your Name]

It is a good idea to reach out to people after your archive has been published so that you can include a link to it and demonstrate that you are serious and have put in significant time and effort into the project already. We will explore how to publish your archive in a later chapter.

If you do not receive a response within a few weeks, consider sending a gentle follow-up. Keep it low-pressure and do not simply repeat the original request. You might instead say that you are still working on the archive and would be interested to hear whether they have any fond memories of the modification, remember who was involved, or know what happened to the project. The aim is simply to make contact and invite a conversation, rather than make someone feel obliged to search through old files or respond to a request. Even if they cannot help with the specific file, they may have an interesting story, useful recollection or lead to another person who can help.

Continue the conversation

The first email should focus on making contact and asking for something specific. If the person responds positively and is receptive to helping, you can gradually broaden the conversation.

For example, you could ask whether they have copies of other releases, including earlier versions, patches, beta releases or development builds that were never publicly released. You could also ask whether there is other material from the project that they would like included in the archive, such as source code, documentation, screenshots, website backups or development notes.

Finally, ask whether they remember other people who might be able to help. Former team members, contributors, beta testers and community members may have retained files or know where to find them. One successful contact can lead to several more, creating a network of people who can help reconstruct the project’s history.

Summary

People are potentially the best source of non-public Quake files. Former developers, contributors, beta testers and long-time archivists may have retained original releases, beta versions, source code, backups and documentation that cannot be found through public archives.

The process involves identifying potential contacts, researching their backgrounds, maintaining a contact spreadsheet and reaching out through community forums, Discord, email and social media.

Leave this work until you have exhausted the easier public sources and know precisely what you need. Be specific in your requests, patient with responses and grateful for any assistance. Ask people for referrals to other potential contacts.

This approach requires considerable legwork and has a low success rate, but the results can be exceptional. A single former developer or collector may have exactly the rare release that your entire archival project has been missing.