36
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Aug 2025
36 points (90.9% liked)
Games
20752 readers
494 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 2 years ago
MODERATORS
Disingenuous? I think that's projection.
Not once have I stated it was high art to not add this in. That's a wild statement.
I'm simply stating not doing so isn't lazy, or gate keeping. The devs ar e focusing elsewhere. To focus here, they spend more money or take something else out. As a dev you should know this.
This is a feature. You can focus on a subset of all possible features. Not implementing one does not make you a worse dev your code is what matters. A dev should know this. You have x amount of time (money) a dev thus can implement y features.
A house should have a garage. Not building one doesn't make you a lesser builder you just didn't have the finds and chose to build a nursery instead with the money. Focus was elsewhere.
Edit: It's clear to me this persons not going to engage. They ignore my arguments, make up new ones, and don't seem to care for the discussion. I'm going to disengage
As a dev you keep throwing around the word accessibility very loosely. This is very weird. Are we talking about accessibility for disabled people or for people who simply find the game difficult? The latter is the main conversation here. The prior is ableism through low expectations. You're nolonger talking about an "easy mode" either. Accessibility settings aren't "easy modes" disabled people don't need to be coddled.
Also, as a dev, you should know seemingly simple features are not commonly simple. Any dev past junior should know this. No Dev past junior should make these claims unless speaking directly about tech.
Edit: On top of this, I've made no all or nothing argument. Lowering damage and speed does very little to help. Essentially nothing.
Please, under any engine of choice, give me a top level on how you're implement variable speed.
You throw a lot of hatred towards devs (calling them lazy gatekeepers who are poor in craft who can't implement something AI can) what are your creds?
I'm a fullstack software dev with 7 years experience and a specialization in accessible ui (disability, not dislike for the combat system) and multiplatform codebases. You?