Tag: modding

Posted on by

Ancient Web: ToastyTech Never Stopped Making Doom WADs

Some people played Doom in 1993 and moved on. The person behind ToastyTech apparently interpreted Doom’s release as a long-term maintenance obligation.

Visit ToastyTech’s Doom pages

The page opens with a simple explanation: id Software released Doom on December 10, 1993, and “I never stopped playing.” What follows is less a polished portfolio than a fossil bed of Doom enthusiasm—custom levels, screenshots, old versions, experiments, joke material, music files, and work-in-progress archives accumulated over years.

MarsWar is the obvious centerpiece. It is a Doom II megawad with its own story about a Martian terraformer, an invasion from Earth, and space-warp ships built by a company whose initials happen to be “MS.” The site keeps multiple versions available, including older builds because people asked for them. That small detail says a lot about the culture around old game mods: history survives because somebody decides an obsolete ZIP is still worth leaving online.

Elsewhere there is a Doom 1 MegaWad compilation, a Hexen level, Skulltag and jDoom material, Doom Alpha levels modified for deathmatch, original MOD and MIDI files, Ranma 1/2 character skins, unfinished maps, and even a Firefox-themed WAD. There are also screenshots from very early Doom versions and a “Doom Guys Vacation” section whose description is simply: went to hell, took pictures, posted them here.

The important thing is not that every file is a masterpiece. The page preserves how PC game modding actually looked when personal websites were the distribution system. A ZIP file sat next to a TXT file. Screenshots were separate. Compatibility notes mattered. Old versions stayed reachable. The author’s own jokes, experiments, and unfinished work remained mixed in with the serious releases.

Modern mod sites are much better at indexing and downloading. They are often worse at preserving the creator’s original neighborhood around the files. ToastyTech still has that neighborhood.

For researchers studying Doom, homebrew level design, WAD distribution, early fan culture, or the long tail of DOS-era games, these personal pages can be more revealing than a clean database entry. They show what the creator thought belonged together.

That is the same reason CacheRat maintains the 1,967 Ancient Web Domains research list: sometimes the useful historical unit is not the file. It is the whole weird page around it.

Doom is still alive almost everywhere. ToastyTech is interesting because it preserves one person’s uninterrupted relationship with it.

Dig through ToastyTech’s Doom stuff

Posted on by

Ancient Web: The TeamTNT Memorial Keeps a Doom Modding Collective Online

TeamTNT began as a group of Doom hobbyists and ended up inside official Doom history.

Visit the TeamTNT Memorial

The group formed out of the active Doom-editing community in the mid-1990s. Members were spread across different locations and coordinated online, building levels, tools, total conversions, deathmatch packs, and eventually engine technology that would influence Doom mapping far beyond their own releases.

Their most famous project was TNT: Evilution.

The megawad was originally intended to be released free to the Doom community. Historical accounts describe id Software contacting team leader Ty Halderman only hours before the planned public release and arranging to acquire the project.

TNT: Evilution became one half of 1996’s commercial Final Doom.

That is an extraordinary path from hobby project to official product.

It was also controversial at the time because some Doom players saw the commercialization of a community-made WAD as crossing a line that had not really existed until somebody crossed it.

Modders building infrastructure

TeamTNT’s importance goes beyond one release.

The group also produced projects including Icarus: Alien Vanguard, Eternal Doom, deathmatch packs, and development resources. TeamTNT members were responsible for the Boom source port, which relaxed engine limits and added features that became deeply important to later Doom level design.

That matters because modding communities often leave two kinds of legacy.

The obvious one is content: maps, graphics, music, and campaigns people can still play.

The less visible one is infrastructure: tools, standards, techniques, engines, documentation, and workflows that let everybody else build more ambitious things afterward.

TeamTNT did both.

The memorial site preserves that identity after the original organization largely wound down. Ty Halderman, who had been a central organizer and later maintained the enormous idgames archive, died in 2015. By then TeamTNT had already become part of Doom history rather than merely an active mapping crew.

The old pages matter because distributed creative groups are unusually easy to lose.

There may be no office, company archive, filing cabinet, or institutional historian. The work exists in ZIP files, mailing-list posts, readme files, websites, and the memories of people who once knew which handle belonged to which mapper.

CacheRat’s 1,967 Ancient Web Domains research list includes gaming sites like this because fan-created work frequently becomes part of the medium’s history before anybody thinks to preserve the people behind it.

TeamTNT started by editing Doom.

Eventually Doom’s history had to be edited to include TeamTNT.

Explore the TeamTNT Memorial

Posted on by

Ancient Web: GoldenEye Forever Refused to Let One N64 Game Die

Most fan sites eventually become memorials. GoldenEye Forever behaves more like the game is still under active investigation.

Visit GoldenEye Forever

The site is devoted to GoldenEye 007 for the Nintendo 64, but “devoted” barely covers it.

There are cheats, GameShark codes, emulator guides, multiplayer strategies, custom levels, videos, weapon information, hidden-content research, and material documenting the community that kept pushing the 1997 game long after the original hardware generation had ended.

One of the site’s signature subjects is the Citadel, a famous unfinished level left inside the game’s data.

Fan researchers gradually learned how to expose more of it. By the mid-2000s, GoldenEye Forever was documenting a fully playable multiplayer form accessed through extensive GameShark coding. Historical accounts of the discovery describe code sets running to thousands of lines.

That is no longer merely playing the game.

That is excavation with controllers.

A game that kept getting new rooms

GoldenEye Forever also documents the wider modding scene that formed around the game.

Community members converted single-player areas into multiplayer maps, imported environments inspired by Perfect Dark, experimented with custom weapon sets, pushed emulator-based online play, and treated the original ROM as a platform for continued development.

The site’s writing repeatedly returns to the same idea: GoldenEye keeps evolving because players keep finding things to do with it.

There is a nice old-Web quality to how the discoveries are presented.

The homepage is dense. Screenshots pile up. Download links sit beside personal commentary. Updates refer to forum regulars by handle because the audience is assumed to know who these people are. The site feels less like a polished publication and more like a clubhouse whose filing cabinets happen to be public.

That is useful history.

The surrounding community mattered because many discoveries did not originate from companies or official re-releases. They came from hobbyists examining the game, sharing codes, building tools, testing on real hardware, and comparing results in forums.

A commercial product became a collaborative object.

CacheRat’s 1,967 Ancient Web Domains research list includes fan archives like this because games often survive culturally through the people who refuse to accept that development ended when the cartridge shipped.

Rare finished GoldenEye in the 1990s.

GoldenEye Forever never got the memo.

Explore GoldenEye Forever

Posted on by

Ancient Web: The RCT Technical Depot Reverse-Engineered RollerCoaster Tycoon One File at a Time

Some game communities write walkthroughs. Others eventually start documenting the byte layout of the save file.

Visit the RCT Technical Information Depot

The RCT Technical Information Depot belongs firmly to the second category. It collects technical information discovered by fans about RollerCoaster Tycoon, RollerCoaster Tycoon 2, RollerCoaster Tycoon 3, and Locomotion.

The site explains that it was originally hosted through GameSpy’s StrategyPlanet as part of RCTUK and was later moved after that server disappeared.

What survived is not a conventional fan site. It is documentation for people who wanted to understand the games underneath the interface.

When curiosity reaches the file format

The Depot covers formats such as TD4 and TP4 track files, SV4 and SC4 saves and scenarios, RCT2 object DAT files, TD6 track designs, SV6 and SC6 data, and later RCT3 formats including TRK, DAT, OVL, FWD, FWR, and PRF.

That means checksums, compression or encoding methods, record layouts, object structures, and the odd undocumented behavior required to make outside software read or write data correctly.

Utilities sit beside the documentation, including object editors, save-game tools, and explorers.

This is fan work becoming informal specification.

Commercial game developers rarely publish enough internal detail for third-party preservation and tooling. Communities fill the gap by comparing files, changing one value at a time, observing what breaks, and sharing the discoveries.

The Depot’s framing is careful about purpose. The material is aimed at enhancing and extending the games, not replacing their commercial distribution.

That distinction helps explain why technical fan archives are worth preserving even after newer modding frameworks appear. They contain the path by which the community learned what the software was actually doing.

Modern projects may eventually turn that knowledge into source code or a polished wiki. The old HTML pages preserve the excavation layer beneath them.

CacheRat’s 1,967 Ancient Web Domains research list includes game-technical sites because software history is often reconstructed by enthusiasts long before anyone calls the work preservation.

Somebody had to figure out what byte 37 meant.

Then somebody had to write it down.

Return to the RCT Technical Information Depot