20. Common Problems and How to Get Unstuck
Archiving old Quake modifications can be frustrating.
Files are missing, historical websites are broken, release dates conflict and sometimes weeks of searching produce very little new information.
You may also find yourself questioning whether your archive is worth creating, whether you have enough information or whether you are doing the research correctly.
These problems are normal. Quake modifications were often developed by small teams, distributed through temporary websites and mirrored across dozens of servers. Many were released without formal version histories or consistent documentation.
Most of the problems discussed in this chapter have already been covered elsewhere in this guide. Rather than repeat the detailed research techniques, this chapter offers practical suggestions for overcoming common roadblocks.
The most important advice is to keep moving forward.
You do not need a complete release history, a perfect directory structure or even a single recovered file to begin an archive. Start with what you know, document what you discover and improve the archive as your understanding grows.
I don’t know what to archive
Start with a modification you remember playing.
Perhaps there was a particular bot, total conversion, multiplayer modification or map pack that you enjoyed. Personal interest is a good reason to create an archive because it provides motivation when the research becomes difficult.
Alternatively, look through Quake forums, Discord servers and other community discussions. Find modifications that people remember fondly, ask about or struggle to locate.
You could also choose a popular modification, a particular development team or a theme such as bots, capture the flag modifications or early QuakeC projects.
Start as small as possible. Archiving one modification is a manageable project and will teach you techniques that can be applied to larger collections later.
I don’t know where to start researching
Start with a simple web search for the modification’s name.
Look for surviving download pages, old news articles, forum discussions and references to the original project website.
Search the Internet Archive, Usenet archives and historical CD collections such as those catalogued by QuakeDiscs.
You only need one useful lead.
A download page might reveal an original filename. A readme might identify the developers and project homepage. An archived news announcement might provide a release date and links to other resources.
Follow these connections and begin recording your discoveries.
If you are unsure where to look next, revisit the research chapters of this guide and try another source.
I don’t have enough information to start an archive
You probably have more than you think.
Even a modification name, a short description and a few historical references are enough to begin documenting a project.
Create a simple Text or Markdown file containing everything you currently know.
Record the modification’s name, the game it belongs to, any known developers, references to releases and links to historical websites.
Add questions about anything you cannot establish.
The act of organising this information often reveals new search terms and research opportunities.
You can expand the archive’s structure later when you have more material.
Another archive already exists
This is good news. It means someone else cares about preserving the modification.
There is no requirement that a Quake modification have only one archive.
You may want to organise the releases differently, provide more detailed historical documentation, investigate missing versions or preserve evidence that the existing archive does not include.
Even if the collections are similar, independent archives provide redundancy. If one disappears, another may survive.
Consider contacting the other archivist. You may be able to exchange files, compare research and help each other resolve outstanding questions.
Multiple archives can be better for the community than a single collection maintained by one person.
The project seems too large or complicated
Reduce its scope.
You do not need to recover every release, investigate every historical website or reconstruct the entire development history before publishing.
Begin with one modification and a small collection of known releases.
If necessary, focus on a single task, such as identifying the original release filenames or finding the project’s homepage.
Record what you discover and move on to the next task.
A modest archive that is publicly available is more useful than an ambitious archive that never gets finished.
I am worried about publishing incomplete or incorrect research
An archive does not need to be complete before it becomes public.
In fact, publishing early can be helpful.
It gives you a reason to organise your findings, explain your conclusions and maintain a clear record of where files came from.
It also allows other people to find your work and contribute missing information.
Make uncertainties explicit. Use question marks for unknown dates, identify unverified releases and distinguish evidence from speculation.
You can correct mistakes as new information becomes available.
The goal is not to publish a perfect historical account on the first attempt. It is to create a reliable record that can improve over time.
GitHub seems too complicated
You do not need a full GitHub repository to create a useful archive.
The simplest archive can be a single Markdown document.
List the known releases, approximate dates, original filenames, historical download URLs and any surviving download links. Include the project homepage, relevant references and important unanswered questions.
You can publish this document using GitHub Gist:
https://gist.github.com/
A Gist is a lightweight way to publish a Markdown document without creating and maintaining a complete repository.
I sometimes use this approach for small, one-off archival investigations. After a few days of research, I publish everything I can establish about a modification, including known releases, historical links, working downloads and missing files.
The result is useful even if I never return to the project.
Someone can use it to download an old modification, understand what other releases existed or continue the research themselves.
You can always move the information into a larger repository later.
I cannot find the original project homepage
Start with contemporary references to the modification.
Historical gaming news websites often linked directly to project homepages when announcing releases.
Search archived news articles, Usenet posts, forum discussions and old download pages.
If you can recover a copy of the modification, inspect its readme. Developers frequently included the project website, email addresses and other contact information.
Search for the developers’ names and aliases as well.
The project may have moved between several hosting services, and an early homepage might use a completely different address from a later one.
If you cannot identify the homepage, document the references you have found and continue researching other aspects of the modification.
I cannot determine the original release filenames
Look for historical download links rather than relying only on surviving files.
Archived project websites, gaming news announcements, FTP listings and magazine CD catalogues may identify filenames even when the downloads themselves are missing.
Search for different naming conventions, abbreviations and version number formats.
If you have a recovered release, inspect its readme for references to earlier versions or patches.
You can also make educated guesses about filenames and search for them. For example, a known release might suggest a naming convention used for earlier versions.
Treat guessed filenames as search leads, not established historical facts.
Document what you know and keep investigating.
I cannot recover any files
An archive without recovered files can still be useful.
Document the modification’s history, known releases, original filenames, historical download locations and surviving references.
If you have very little information, keep everything in a single Markdown document rather than building an elaborate directory structure.
Try broadening your research.
Look for related modifications, other projects by the same developers, alternative hosting services and collections that might contain files from the same period.
Search for distinctive filenames, readme text, developer aliases and related project names.
You may also need to contact collectors, former developers or other community members.
Be creative. A missing release might survive inside an unrelated CD collection, a personal backup or an archive maintained for another modification.
If you exhaust the available leads, publish what you know and move on. A documented missing file is easier for another collector to recognise and recover.
I can only find broken historical download links
Broken links are still valuable discoveries.
They may reveal original filenames, version numbers, distribution locations and the structure of historical project websites.
Record the complete URLs in research/wishlist_urls.txt and connect them to the appropriate releases in research/history.md.
Try searching for the filename and checking whether the file was preserved by the Wayback Machine or copied to another mirror.
If the file remains unavailable, leave it on your wishlist.
Do not spend unlimited time pursuing a single broken link. Document the evidence and investigate another lead.
A copy may eventually turn up through another archive or collector.
The file timestamps don’t match the release date
This is common and does not necessarily indicate a problem.
Files inside an archive may have been created or modified days or weeks before the release was published. Developers often prepared a release, tested it and distributed it later without changing the contents.
Alternatively, files may have timestamps later than the supposed release date.
There are several possible explanations:
- The developer corrected a problem and redistributed the release using the same filename.
- The archive was repackaged by a mirror, collector or CD publisher.
- The release was updated without changing its version number.
- The files were extracted and compressed again, changing their timestamps.
- The original computer’s clock was incorrect.
- The timestamps were changed by copying, extraction or archive creation tools.
- The historical release date was recorded incorrectly.
Consider the available evidence and develop plausible explanations.
Compare readmes, changelogs, file contents, archive timestamps and contemporary announcements.
Document your interpretation and the evidence supporting it.
If you cannot establish the reason for the discrepancy, record the uncertainty and move on.
The readme contains the wrong version number, date or filename
This is also common.
Developers often reused readmes from earlier releases.
They might update the changelog and package new files but forget to change the version number, release date or download filename elsewhere in the document.
A readme may therefore contain contradictory information.
Compare it with the actual archive contents, release announcements, changelog entries and other distributions.
Look for evidence that identifies the release independently of the incorrect information.
Do not silently correct the original readme. Preserve it as distributed and document the discrepancy in your historical record.
If the most likely explanation is that the developer forgot to update the document, say so, while making clear that this is an interpretation.
I found multiple files with the same filename but different hashes
This is very common in historical software archives.
Two files may have identical names but different contents, sizes or timestamps.
They might represent different releases, silent updates, alternative distributions, repackaged copies or modifications made by third parties.
Do not overwrite one file with another.
Preserve each distinct copy.
If necessary, add a suffix to the filenames in your archive to distinguish them, such as _v1 and _v2, or a suffix identifying the source. These suffixes are archival labels and should not be mistaken for official version numbers.
Record the original filename for each copy in research/history.md.
Compare their contents, readmes, changelogs, file timestamps and any available historical evidence.
Try to determine which copy was distributed first, whether the differences are meaningful and whether either copy can be linked to a particular release announcement.
Sometimes you will be able to establish a clear relationship between the files. Other times, the evidence will remain inconclusive.
Preserve both copies and document what you know.
I found files with different names but identical contents
This may indicate that a release was renamed by a mirror, CD publisher or collector.
Calculate hashes and compare the contents of the archives.
If the archives are byte-for-byte identical, they are copies of the same file despite having different names.
If the archive hashes differ but the extracted contents are identical, they may have been repackaged using different compression settings or archive tools.
Record the different filenames and distribution sources.
You do not necessarily need to preserve every identical copy in bin/, but the alternative filenames and historical locations may be useful evidence.
In particular, an alternative filename can provide a valuable search term for locating additional mirrors.
I cannot tell whether two files are different releases
Start by comparing their contents.
Look for changes in readmes, changelogs, executable files, QuakeC files, maps, configuration files and other resources.
Check for internal version numbers and release dates.
Compare the files against historical announcements and known distribution locations.
A difference in archive size or timestamp alone is not enough to establish a new release.
The files may represent the same release packaged differently.
If you cannot determine their relationship, preserve both and describe the differences you have identified.
There is no need to invent a version number or force every file into a definitive release sequence.
The release dates conflict between sources
First, determine whether the sources are describing the same event.
A modification might have been announced on one day, uploaded to a download server the next day and mirrored elsewhere several days later.
A magazine CD might distribute the same release months afterward.
These dates are not necessarily contradictory.
If two sources genuinely disagree about the release date, compare their reliability and proximity to the original event.
A contemporary announcement from the developer may be stronger evidence than a date listed in a much later archive.
Record the conflicting information and explain which date you consider most likely.
If the evidence is insufficient, leave the date uncertain.
A recovered archive is damaged or incomplete
Preserve the damaged file before attempting to repair it.
A partially corrupted archive may still contain useful files, filenames, directory structures or other evidence.
Try inspecting its contents with alternative archive utilities. Some tools can recover files that others cannot.
Compare the damaged copy with other distributions or releases to identify what is missing.
If you create a repaired or reconstructed archive, keep it separate from the original and clearly document what you changed.
Do not present a repaired copy as an untouched original release.
Even when recovery is impossible, the damaged archive may provide useful evidence about a missing distribution.
I found an extracted directory but not the original ZIP
This often happens with files recovered from magazine CDs, old installations or personal backups.
Preserve the extracted files and their directory structure.
If you want to make the release easier to download, you can package the files into a new ZIP archive.
Use a filename suffix such as _repack to distinguish the new archive from an original developer distribution.
Document the source, original directory structure, repackaging process and any known original filename.
The recovered content is still valuable, even if the original distribution archive has been lost.
I cannot determine where a file originally came from
Record where you recovered the copy and what you can establish about it.
For example, you might know that a file came from a particular FTP mirror or CD collection without knowing where that source originally obtained it.
Inspect the readme, internal files, timestamps and other metadata for clues.
Search for the filename in historical announcements and archived websites.
Compare the file with copies from other sources.
If the original distribution location remains unknown, say so.
A documented recovery source is still useful provenance, even when the complete chain of custody cannot be reconstructed.
I cannot contact the original developers
Many Quake developers used temporary email addresses, old usernames or personal websites that disappeared decades ago.
Some may no longer participate in the Quake community or may simply have no interest in discussing their old projects.
Try alternative contact methods and look for other contributors, beta testers or people who worked with them.
Other archivists may know how to contact former developers or may already have copies of the files you need.
If you do reach someone, be respectful of their time and avoid repeated requests.
Remember that contacting people is only one research technique.
If you cannot reach the developers, continue investigating public sources and other collectors.
Nobody responds when I ask the community for help
Community requests do not always receive immediate responses.
The people who have the files you need may not see your message, may no longer participate in the community or may need time to search old backups.
Make your request specific.
Rather than asking generally for old Quake files, identify the modification, missing versions and original filenames you are looking for.
Link to your public archive so people can see what you have already recovered.
Try different communities and consider posting again after a reasonable amount of time if you have new information to share.
Do not interpret a lack of responses as evidence that the files no longer exist.
I keep finding the same files everywhere
This is often a sign that you have thoroughly searched the most accessible sources.
Rather than repeating the same searches, change your approach.
Look for historical filenames instead of modern project names. Search for individual files inside archives, developer aliases, original download URLs or references in contemporary news.
Investigate less obvious sources such as magazine CDs, personal FTP mirrors, regional gaming websites and related modifications.
You can also pause the project and return later with new ideas.
Finding the same files repeatedly is not necessarily wasted effort. It can help confirm their distribution history and establish which copies are identical.
I have run out of research leads
Review everything you have already collected.
Look through your notes, references, historical URLs and missing files wishlist.
Ask whether you have followed every useful connection.
Perhaps an old announcement mentions a mirror you never investigated, or a readme contains a developer’s personal website that you overlooked.
Try approaching the problem from another direction, such as searching for the development team rather than the modification.
You can also contact other archivists and ask whether they know of relevant collections or research resources.
If nothing promising remains, stop for now.
Publish your current findings and return after a month, six months or a year.
New resources, new techniques and experience from other archival projects may help you make progress later.
I don’t have enough time to finish the archive
You do not need to finish everything in one sitting or even one continuous research effort.
Break the work into small tasks.
One session might be spent identifying historical download URLs. Another might focus on a single FTP archive or a particular missing release.
Document your findings as you go so that you can resume without repeating earlier work.
If you have limited time, prioritise publishing the information and files you have already recovered.
A small, well-documented archive is a worthwhile contribution.
You can improve it whenever time and interest allow.
I am worried that the archive will disappear
This is a reasonable concern, particularly when you have recovered rare files that may not exist elsewhere.
Publish the archive on a reliable platform, maintain independent backups and preserve important evidence locally.
GitHub is a convenient public host, but do not rely on it as your only copy.
For particularly valuable collections, consider making additional copies available through suitable archival services.
Keep the repository simple enough that someone else could download it and continue maintaining it if necessary.
The easier your archive is to copy, understand and reuse, the better its chances of surviving.
I am not sure whether the archive is finished
There is no universal definition of a finished archive.
You might have recovered every known public release but still lack development builds or supplementary files.
You might have a complete set of files but unresolved questions about release dates and distribution history.
Or you might have documented everything you can find while several releases remain missing.
All of these can be reasonable stopping points.
Review your original scope and decide whether you have achieved what you set out to do.
If you have preserved the available material, documented the known history and identified outstanding gaps, you have created something useful.
Publish it, maintain it when necessary and move on to another project if you wish.
You can always return when new information becomes available.
Chapter Summary
Quake archiving involves incomplete evidence, missing files, conflicting information and research leads that sometimes go nowhere.
These problems are part of reconstructing the history of software that was distributed decades ago.
Most can be addressed by investigating alternative sources, comparing evidence, documenting uncertainty and being willing to revise earlier conclusions.
When you cannot resolve a problem, record what you know and continue with another part of the archive.
Do not allow the pursuit of completeness or certainty to prevent you from preserving what you have already found.
The most important thing is to keep moving forward. Start small, document your discoveries, publish what you have and improve the archive over time.