DECEMBER 2025 — SEPTEMBER 2026
We kept building
what we needed next.
A community became a server network. The network became a studio. Every rebuild left something worth passing on.
Thunder Buddies grew through collaboration, experiments, setbacks, and the people who kept showing up. This is our account of that journey, and why these source projects now have a home here.
The community before the platform
Thunder Buddies was already active by December 2025. Before ThunderLink and Faircroft, there were community websites, Discord tools, game servers, and modding support. Much of the work began with a simple need: make something useful for the people already here.
Early hosting interruptions and platform problems forced rebuilds. Explaining failures clearly became part of the studio’s voice, alongside the humor and informality of the community itself.
One server became a network
On December 24, the studio announced a beginner-friendly World War 3 PVE experience for Xbox, PlayStation, and PC. By December 28, its announcements described four live PVE servers. Missions, worlds, and mod combinations gave each server its own character.
The practical lessons mattered as much as the ideas: console limits, stable performance, saved loadouts, and a manageable download. Features were removed when they made the experience worse. Servers were paused when rebuilding was the responsible choice.
Making room for other builders
Thunder Buddies and The Social Club announced a plan for free Reforger hosting. It was a proposal and a direction, not proof that every promised feature reached production. The aim was to lower the barrier for smaller communities.
The studio also described itself as a collaboration of server owners. Partners brought their own work and identities. PVE, faction warfare, survival, WW2, close-quarters combat, and other experiments followed; some launched, some stayed tests, and some changed direction.
Faircroft, and a world beyond the server
Faircroft became a laboratory for persistent roleplay: properties, government, banking, markets, records, and systems connecting the game to the web. A server was becoming part of a much larger application.
On July 25, RP Link became ThunderLink TBS Roleplay Network. Accounts, dispatch, CAD, payments, and APIs expanded that idea. Plans for isolated cloud deployments and rebuilt whitelisting followed. Announced capabilities and working systems were not always at the same stage.
Choosing to change course
The studio biography records a security crisis in late August and the decision to step away from Arma development around August 30–September 1. Safety took priority over keeping services running.
This chapter is preserved without repeating private incident details or personal identifiers. The broader lesson stayed with the studio: communities need clear boundaries, protected infrastructure, and room to stop and rebuild.
Building beyond Reforger
The next direction included experiments beyond Arma and work toward an original game. FaultLine: Storm of Shadows emerged as an open-world cooperative and multiplayer concept, carrying forward lessons from scenario design, survival systems, and server operation.
ThunderLink also developed toward a launcher, game library, and platform for independent developers. These were projects in development, not a claim that every proposed game, storefront feature, or future expansion had shipped.
The ThunderLink AI experiment
ThunderLink AI grew from hosted-model experiments into work on conversation, coding, research, and creator tools. Its free-access ambition continued a familiar theme: useful tools should be within reach of people building with limited resources.
The hosted AI service closed on September 27, 2026. Its separate archive preserves the engineering story, benchmarks, limitations, and goodbye. That closure is part of this history; it does not mean every other Thunder Buddies project ended on the same date.
The work stays available
This library gives the modding chapter a place to live on. It preserves source projects, experiments, dependencies, and the context behind them so another builder can find an idea worth carrying forward.
For original Thunder Buddies material in this release, the new attribution license permits reuse, modification, and redistribution with visible credit. Existing third-party terms remain attached to their work. The request is simple: acknowledge where the work began.
Adapted from the studio’s “Thunder Buddies Studios — A Detailed Timeline Biography,” covering December 2025 through September 2026, and the studio’s subsequent closure and library-release statements. This is a studio-authored history. Plans and experiments are identified as such; private incident details are omitted.
Explore the source library → · ThunderLink AI archive ↗