Games

16822 readers

1100 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:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 1 year ago

MODERATORS

nanoUFO@sh.itjust.works

372

Fallout London's project lead is not taking the surprise drop of Fallout 4's update well: 'That has, for a lack of a better term, screwed us over' (www.pcgamer.com)

submitted 7 months ago by nanoUFO@sh.itjust.works to c/games@sh.itjust.works

136 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] BolexForSoup@kbin.social 0 points 7 months ago

Like I said in my edit, I’m not entirely defending Bethesda here. I’m just trying to look at this case specifically and not let their entire history color it, as difficult as that may be. FOLON is somewhat turning this into a blame game, where I don’t think anyone’s really at fault except arguably Bethesda in that specific case.

Even with all of that in mind, Bethesda should have been in better communication with modders. There’s no doubt here. They are critical part of the overall success and staying power of their games.

From a business/PR standpoint, Bethesda missed a great opportunity to regain some rapport with the community post-Starfield