yourenotsupposedtobeinhere: Summerset Isle Mod Controversy: Fact vs. Forum Consensus

Purpose: To provide verifiable, primary-source data correcting long-standing misinformation, internet rumors, and platform-biased narratives regarding the development, permissions, and history of yourenotsupposedobeinhere's Summerset Isle modification.

Legendary Edition (LE) Permissions & Content Creator History

The Public Narrative:

The mod author maintained a hostile, blanket ban on content creation, YouTube Let's Plays, and reviews during the original Legendary Edition era, aggressively punishing creators who attempted to showcase the mod, or make patches.

The Documented Facts:

The Legacy Clause: Upon the mod's initial 2015 release, the permissions text contained a strict protective clause regarding monetization on video platforms. Despite this text being technically present, it was never used punitively by me. Dozens of content creators openly ignored the text and covered the mod for years with zero intervention, restriction, or friction from me. Those harsh permissions were simply ported using the 'port mod' button on a 5-year-old LE version that no one paid attention to. When notified that the legacy text was too strict, both permissions were updated to, "Ask first."
Extensive Public Coverage: The claim of a historical streaming ban is entirely contradicted by a massive, verifiable record of prominent content creators who freely played, reviewed, and spotlighted the mod without any restriction or interference from the me. Verifiable public coverage includes:

Comprehensive showcases and by major community channels including Gopher, Brodual, MxR.
Multi-part Let’s Play video series and gameplay reviews by creators such as OneMeanEastEuropean, Enraged Bard, Magicka Addict, Chayification, Jaden Scremo, Kaloari Jikashi, agb015mudkip, L1L_F3LL4, ArqueiroFreelancer_, Delver Rootnose, AerysTMD, Grimboozed, しちめんちょう, just to name a few.

The Living Patch Ecosystem: The absolute baseline claim that patching or tweaking the mod was banned or made "impossible" due to permissions is completely dismantled by the physical existence of the Nexus Mods database. Dozens of standalone compatibility patches, translations, framework integrations, and visual updates exist publicly—none of which required permission friction or faced punitive action from me.
Verifiable Community Modifications & Patches:
Legendary Edition (LE) Archive:
- Summerset Isle - Merged Patches
- Summerset Isle - Patches
- Summerset Isle - Polish Translation
- Summerset Isle - Spanish Translation
- Summerset Isle - Translation Brazilian Portuguese (PT-BR)
Special Edition (SE) / Anniversary Edition Ecosystem:
- Visual & Landscape Frameworks: DynDOLOD TexGen Fixes (Beyond Reach-Gray Cowl-Summerset Isle-Extended Cut-ELFX), Terrain Shadows - Mod Patches, GKB Waves For Various Mods, Unique Grass in New Lands, Basic LOD for Happy Little Trees / Fabled Forests / Aspens Ablaze / Green Lush, Basic LOD for Ulvenwald / Wigfrids Tree Replacer.
- Ecosystem & Overhaul Integration: Legacy of the Dragonborn - Craftloot Sort and Storage FormList Patches (FLM), Tamriel Location Framework - Patch Hub, Botox of Skyrim - Patch Hub - NPC Overhaul, Kit's FaceGen Patches for Shiva's Vanilla Hair Replacer.
- Gameplay, Survival, & Core Mechanics: Summerset Isle - CACO (Complete Alchemy and Cooking Overhaul) Patch, SkyFood A Delicacy for Mods - SkyPatcher Edition, SPID Distribution Text Addons for Edmond's Immersive Needs, Summerset Isle Survival Mode Compatibility, NAT3 - Patches, StarRiseShine's Apothecary and Apothecary Food Patches, StarRiseShine's Gourmet Patches, Colorful Lights - No Shadows Patch Hub, Put Camp Without Potion - Simple Survival Craft, SkyLore - Ingredients / Ingredients Have Description, Stop Handling The Fish - No Catching Fish by Hand.
- Global Localization Releases: Summerset Isle (Russian Translation), Summerset Isle - SSE - Deutsch, Summerset Isle - SSE - Chinese / With Light CHS, Summerset Isle SE Spanish, Summerset Isle PT-BR v1.522, Summerset Isle - Polish.

The Zero Period Productions Deletion (The Direct Chats)

The Public Narrative:

The mod author weaponized copyright claims and malicious DMCA takedowns to force the YouTuber George (Zero Period Productions) off his series, and routinely struck down other channels to suppress critical reviews.

The Documented Facts:

Direct, unedited private messaging logs and official legal agreements prove that no legal threats or copyright abuse occurred. Clear boundaries exist between a broken private contract and a singular action against severe targeted harassment:

The Zero Period Productions Contract: Before starting his 2022 series, George explicitly entered into a mutual text agreement to cover the mod under specific parameters, stating: "Like you said, I will treat the playthrough and review the way I would a sponsorship for any game I'd play." Under this agreement, I permitted full video monetization, due to the poor relationship we had before and how he mislead me, and his viewers.
The Voluntary Removal: When I confronted George regarding his breach of our agreement (rushing through major world spaces in minutes, utilizing a generic burner save rather than a dedicated character, cutting gameplay that challenged his character, and publicly misrepresenting a 200+ hour mod as a 20-hour experience), George voluntarily chose to delete the playlist to avoid personal accountability and creative critique, stating: "I have taken the liberty of removing the playthrough in full, and will not be releasing the final YouTube episode... While you did not ask for this, I simply want to avoid any more of a headache."
The Singular DMCA Action: I executed exactly one DMCA copyright strike in the entire history of the mod's existence. The target was a single monetized video where the content creator was impersonating another youtuber while he used the mod's showcase as a platform to abuse me, explicitly instructing me to commit suicide over approximately 20 minutes.
The Outcome: The Skyrim community stripped these events of their logistical and safety contexts, twisting George's voluntary exit over an agreement he broke into a false narrative about me issuing arbitrary copyright strikes against reviewers.

Subreddit Moderation and Selective Censorship

The Public Narrative:

The r/skyrimmods moderation team acted as neutral, objective administrators who only stepped in to delete aggressive comments to maintain the forum's strict "no-drama" policies.

The Documented Facts:

Public statements and moderation logs show that prominent staff members, specifically the moderator Thalassa, held deep, personal institutional bias against me and actively used their administrative powers to curate a negative narrative while silencing dissenting viewpoints.

Public Defamation by Staff: In public community threads, Thalassa actively stepped out of a neutral moderation role to personally run down my reputation, stating: "His reputation in the community is quite public... don’t complain that someone’s reputation is in the dumpster when they earned that through their own actions," and publicly accusing me of a "refusal to learn."
Asymmetric Enforcement: Moderation logs demonstrate that the team actively practiced selective censorship. Highly critical, speculative, or rumor-heavy comments targeting me (such as claims regarding "questionable stipulations") were left completely intact. Meanwhile, any constructive or empathetic comments pointing out the years of uncompensated labor I provided or calling for objective criticism were systematically deleted under the guise of "preventing drama."

Technical Collaboration vs. The Closed Group

The Public Narrative:

The mod author was technically incompetent, stubbornly refused to fix critical engine errors (like the reference handle limit or converting the file into an .esm structure), and rejected all community help out of spite or ego.

The Documented Facts:

Private Technical Consultation: I was actively, privately consulting some of the most knowledgeable and established technical minds in the Bethesda modding community to run tests, optimize architecture, and safely navigate Skyrim's engine limitations without corrupting user data. These tests lasted a decade.
The Core Plugin Conflict: The conflict arose when an uninvited, closed group consisting of robertgk2017, FelesNoctis, and others began decompiling and altering the mod's core master files behind closed doors without my knowledge or consent. robertgk2017, a member of this group publicly claimed to have fixed the mod based on an incomplete, single-day test run, while claiming certain records caused immediate crash-to-desktop (CTD) errors—a claim directly debunked by veteran engine testers in the very same group.
Ownership and Integrity: I refused to blindly implement untested, sweeping structural modifications to my core master file forced upon me, while at work, by an outside group that refused to share their full methodology or invite me to the table. I maintained that as the sole individual responsible for the mod's long-term maintenance and updates, I am required to understand and verify every single record alteration before deployment.
Documented Institutional Bias: Verifiable archival records show that prominent figures and project leads from massive community modification teams (such as Beyond Skyrim) and highly influential mod creators systematically targeted the project with bad-faith public critique immediately upon release.
EnaiSiaion