this post was submitted on 24 May 2025
468 points (97.2% liked)

Games

38773 readers
1273 users here now

Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.

Weekly Threads:

What Are You Playing?

The Weekly Discussion Topic

Rules:

  1. Submissions have to be related to games

  2. No bigotry or harassment, be civil

  3. No excessive self-promotion

  4. Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts

  5. Mark Spoilers and NSFW

  6. No linking to piracy

More information about the community rules can be found here and here.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] mriswith@lemmy.world 78 points 1 day ago* (last edited 1 day ago) (29 children)

That's nothing new.

Gamers who don't know any programming, or maybe made a little utility for themselves. Looovee to bring out the old "just change one line of code", "just add this model", etc. to alter something in a game.

They literally do not understand how complex systems become, specially in online multiplayer games. Riot had issues with their spaghetti code, and people were crawling over eachother to explain how "easy" it would be to just change an ability. Without realizing that it could impact and potentially break half a dozen other abilities.

[–] Ghoelian@lemmy.dbzer0.com 72 points 1 day ago (14 children)

Even if you're an actual software dev, it's still pretty much impossible to guess how much work something is without knowing the codebase intimately.

[–] shoo@lemmy.world 11 points 1 day ago* (last edited 21 hours ago) (6 children)

When a dev with game dev experience says something should be easy to fix, it's under the assumption of a reasonable code base. Most games are built off of common engines and you can sometimes infer how things are likely organized if you track how bugs are introduced, how objects interact, how things are loaded, etc...

When something is a 1 day bugfix under ideal conditions, saying it will take 6+ months is admitting one of:

  • The codebase is fucked
  • All resources are going to new features
  • Something external is slowing it down (palworld lawsuit, company sale, C-suite politics, etc...)
  • Your current dev team is sub par

Not that any of those is completely undefendable or pure malpractice, but saying it "can't" be done or blaming complexity is often a cop out.

[–] DireTech@sh.itjust.works 6 points 23 hours ago

Can’t be done is usually shorthand for the cost massively outweighs the benefits. No different from remodeling a building. Like coding, literally anything is theoretically possible but sometimes you’d have to redo so much existing work it’s never going to be worth it.

load more comments (5 replies)
load more comments (12 replies)
load more comments (26 replies)