this post was submitted on 25 Apr 2024
377 points (97.5% liked)
Games
16370 readers
840 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
IMO the solution is to enable easier manual versioning management. Instead of auto updating everything, just add an update button when there's an update available, include a rollback option, and offer downloads for popular versions instead of just the latest.
Back in the StarCraft modding days, some tools required specific versions of the game to function. The modding community figured out how to work around that by hosting the patches that got to the desired version and giving instructions (maybe even tools) for users to manage using both a specific version for mods and the latest version to play online.
The modding community was doing its own thing and didn't expect Blizzard to adjust the way they were doing anything to make things easier. I can't believe the sense of entitlement I'm seeing all over the place regarding this.
These broken mods were using a third party tool that reverse engineered the game's binary to do things their modding API didn't expose. If they wanted to be dicks about it, they might have been able to shut it down as a tos violation or tried to deliberately block it some other way. All they did was update the code, which then generates a new binary and changes all of the addresses and offsets that the tool needs to use.