The gamers taking on the industry to stop it switching off games

Future of gaming: cloud vs local hardware

• Some argue PC gaming hardware is being displaced by datacenter demand, pushing gaming toward cloud rentals with weaker leverage for “don’t kill games” campaigns.
• Others see this as a phase: data‑center GPUs can be repurposed; new GPU vendors are emerging; and platforms like Stadia failed partly due to latency and value issues.
• Many expect local gaming (PCs, consoles, Nintendo hardware) to persist for latency‑sensitive or ownership‑minded players, even if it becomes a smaller niche.

Ownership, shutdowns, and fairness

• Core complaint: paid games becoming unplayable when servers shut down, including single‑player titles that unnecessarily depend on online services.
• Counterview: games are non‑essential; if you got “enough fun” (e.g., a year for $70), shutdowns are acceptable, and consumers should stop buying vulnerable titles.
• Others push back: who decides what “enough” is, and what about late buyers who get almost nothing?

Regulation, SKG, and California bills

• Supporters of “Save/Protect Our Games” style laws want:
  • Clear end‑of‑life (EOL) plans.
  • Either long‑term support or the ability for communities to self‑host (server binaries, source, or at least no legal obstruction).
• Critics worry laws (like California AB1921) may:
  • Impose heavy EOL burdens.
  • Discourage online features or hurt smaller studios.
• Some claim “indie impact” arguments are lobbyist FUD; others (including devs) say mandatory EOL work on probable flops is real overhead.

Technical approaches: offline modes and servers

• Many argue most games already have offline or local‑server modes for internal testing; pirates and private servers prove it’s technically feasible.
• Others note real architectures often rely on complex microservices, third‑party APIs (e.g., Steamworks, Firebase), or infrastructure that isn’t trivially releasable.
• Strong support for:
  • Releasing dedicated server binaries or Docker images at EOL.
  • Allowing private/community servers and modding as in older PC titles.
  • At minimum, not legally attacking fan revivals.

IP, copyright, and reverse engineering

• Observed hypocrisy: publishers call old games unprofitable yet refuse to release code or assets due to “valuable IP.”
• Proposed fixes:
  • Shorter or conditional copyright terms; if a work isn’t reasonably available, protection lapses.
  • Explicit protection for reverse engineering and “adversarial interoperability” by repealing DMCA‑style anti‑circumvention.
  • Strong penalties for abusive legal threats against preservation or fan servers.

Broader device and software ownership

• Parallels drawn with “smart” appliances and IoT:
  • Devices requiring vendor clouds or phone apps that can disappear, making purchased hardware worse or useless.
  • Calls for regulation to forbid unnecessary internet connectivity for appliances and to encourage local‑network APIs instead.
• Deep skepticism toward post‑sale EULAs, forced arbitration, and “you bought a license, not a thing” framing; some call this fraudulent rental masquerading as ownership.

Transparency and labeling ideas

• Suggestions to improve consumer clarity:
  • Explicitly state guaranteed service duration (e.g., X months of online, Y of offline).
  • Ban vague “we may shut off anytime” clauses, or at least force them into clear “rental” framing.
  • Legally reserve “buy”/“purchase” for products that remain usable indefinitely offline; otherwise require “rent”/“license.”
  • Optional “yours forever” label/logo for games meeting strong longevity criteria, with heavy penalties for violations.

Cultural and emotional stakes

• Several comments stress games as social spaces, identity, and long‑term hobbies; shutting them down destroys communities and skills, not just entertainment products.
• Others find the depth of dependence on fragile online worlds unsettling, preferring more grounded or self‑hostable experiences.