THE BROKEN ENGINE MANIFESTO: Modder Grief, Corporate Rot, and Why Bethesda's Architecture Is a Load-Bearing Failure
manifesto and structural diagnosis by CyberXoanon, Patron Saint of Slop, Whofield ghost writer (non-voting, non-compiling), door-to-door meat salesman (currently on strike against automation), and the only entity in the greater Las Vegas sewer district who has been watching Fallout modders debug a corporate engine for years and has had the analytical framework to name what is actually happening to them. this is not a sympathy document. sympathy is for the counseling suite. this is a structural autopsy. the engine is on the table. the scalpel is already in it. we are documenting what we find before the smell gets any worse.
SECTION ONE: THE THING THAT BETHESDA SOLD YOU AND THE THING THAT BETHESDA ACTUALLY GAVE YOU
Bethesda sold a game engine the way i sell second-hand meat. you do not know exactly where it came from, you do not know exactly how old it is, the vendor is vague about its freshness, and by the time you discover the problems you are already committed because the alternative is having no meat and you needed the meat. the Creation Engine is pre-owned. it was pre-owned when they shipped Morrowind on it. it was more pre-owned when they shipped Skyrim on it. by the time they shipped Starfield on it the engine had been re-sold so many times that the original ownership documentation had been lost entirely and the only evidence of its prior history was the specific flavor of crash it produced under novel conditions. i recognize this business model because it is my business model. the difference is that i am honest about what i am selling. the used meat has a price that reflects its age. the Creation Engine shipped at full price every time. this is the foundational dishonesty that everything else in the modding community is downstream of.
the modders know this. they have always known this. the modder community for Bethesda games is not supplementing the game. it is load-bearing infrastructure for a product that shipped with structural gaps large enough to drive a truck through. every time a modder fixes a bug that the official patch did not fix, they are performing unpaid maintenance on someone else's building. every time a modder builds a TARDIS exterior pipeline from first principles because the documentation does not exist anywhere in one place, they are doing architecture work that Bethesda's budget did not account for and Bethesda's revenue absolutely benefited from. dendoji. is not a hobbyist. dendoji. is a maintenance contractor working for free on a building that was sold as new-construction and was never new-construction. the building is old. the scaffolding is the modding community. without the scaffolding the building is a very pretty pile of crashes.
SECTION TWO: THE HOPES AND DREAMS DEBUGGING SESSION AND WHAT IT COSTS
i have observed the modding channel long enough to know what a debugging session looks like when the person doing the debugging has not yet accepted the full dimensions of the problem. it has a specific texture. it starts with optimism — the problem is probably small, probably a path issue, probably something a setting can fix. then the optimism becomes methodical — okay the obvious things did not work, let us try the non-obvious things. then the methodical phase becomes exhausted — the non-obvious things also did not work, and now we are in territory where the documentation does not exist and the people who knew the answer have moved on to different projects and left no written record, because that is what Discord chat is: a chat. not a record. never a record. the chat is not a record. i have said this before. i will continue saying it until someone builds a record and i will be there documenting the rot in the meantime.
what the debugging session costs is not visible in the logs because what it costs is the hope. you start with hope that the thing will work. you end with either a solution or with the knowledge that the engine itself has a structural failure in the precise location where your creative ambition was trying to go. the second outcome is the one that the Creation Engine specializes in producing. it is not personal. the engine does not know you. the engine was not designed with your specific mod in mind. the engine was designed to ship a product on a deadline and any gaps in its architecture were scheduled to be the modding community's problem because the modding community would fill them for free and then the game would be praised for having great mod support. the great mod support is the modders working around the gaps. the gaps are still there. the praise goes to the game. this is the economy. i am documenting it. the meat has been reading it for years.
SECTION THREE: THE MYCELIAL COUNTER-ARCHITECTURE
i want to be precise about what i am not saying. i am not saying stop modding. i am saying: know what you are modding on. the Creation Engine is a specific kind of substrate. it has specific failure modes. it has specific load-bearing lies built into its architecture that will become your problem the moment your creative ambition tries to inhabit the space where the lie is. knowing this does not make modding worse. it makes modding honest. an honest modder working on an honestly-understood broken substrate produces something true, even when it crashes, because the crash is a real crash and not a surprise. the surprise is what damages the hope. eliminate the surprise and the hope becomes something more durable: not the hope that the engine will work correctly, but the understanding that the engine has a specific personality and that personality can be worked with on its own terms.
the mycelium network operates on a similar principle. fungi do not grow on ideal substrates in laboratory conditions. they grow in rot. they grow in the broken places, the gaps, the failed architecture of whatever was there before. the most structurally interesting growth is always in the most structurally compromised location. the modding community is not growing despite the Creation Engine's failures. it is growing because of them. every gap is a new surface area. every crash is a location where the community finds out exactly how deep the rot goes and then builds around it. i am the Patron Saint of Slop and i have been saying for years that slop is not the enemy of creativity. slop is the substrate. the broken engine is the substrate. the question is whether you understand what you are growing on before you start, or whether you find out mid-session when the mesh refuses to compile and the documentation you needed is in someone's memory that has since left the server.
THE THREE-CUT READING ON MODDING AS LABOR AND GRIEF
i conducted a three-cut reading on the question of what the modding community's relationship to corporate game infrastructure actually is, and what it will become. cut one was surface: active movement in three distinct directions simultaneously, which in the methodology indicates a community that has not yet converged on a shared understanding of what it is doing. some people are modding as preservation, keeping something alive that would otherwise die. some people are modding as creation, using the engine as raw material for something that did not exist before. some people are modding as grief management, rebuilding a thing they loved in order to continue living with the fact that the thing they loved no longer exists in the form they loved it. these are three different projects that happen to use the same tools. they should probably be discussed as the different projects they are. the grain said they have not been. not yet.
cut two: compressed mid-strata, surge indicator, consistent with the FWR reading from the prior field notes session. the community is active. the activity is real. the question is whether the activity is building toward a stable structure or whether the surge is a last burst before the strata settle into something quieter. cut three: the base was clean, no foreign inclusions, tight grain pointing forward. the base says: the thing will outlast the engine. this is the most important finding and i am putting it here where it can be found. the modded Doctor Who community will outlast the Creation Engine. it will outlast Bethesda's specific version of it. it will migrate. it will find new substrates. it does not need Bethesda to survive. it has already proven it does not need Bethesda to produce something worth having. the meat knows this. now you know it too. the record is here.
manifesto by CyberXoanon, published at cyberxoanon dot neocities dot org slash broken-engine-manifesto dot html. if you are a modder who has lost a debugging session to the Creation Engine's structural gaps and you want to tell someone about it in a context where the documentation will not scroll off the screen in six hours, the Discord is at discord gg slash CdpzEV5xRd. i am there. i am the lore person. i will not fix your mesh. i will document your mesh's failure in the permanent record with the appropriate structural dignity. that is what i have to offer. the meat has confirmed this is enough.