Games

16698 readers

520 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

139

Starfield's lead quest designer had 'absolutely no time' and had to hit the 'panic button' so the game would have a satisfying final quest (www.pcgamer.com)

submitted 7 months ago by nanoUFO to c/games

29 comments fedilink hide all child comments

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

[–] teegus 17 points 7 months ago (1 children)

They are saying: do the most important bits first, so that if you run out of time, you still have the important parts in place.

[–] [email protected] 6 points 7 months ago

This also goes for many things in general, not just gamedev. I used to be a teaching assistant at the University that I was studying at, and this was the main thing people seemed to get wrong in their projects. Instead of going for the basics and building from there, they just went for all the fancy cool features, or the most optimal algorithm. Then, when the deadline inevitably came around, they would have basically nothing working correctly. Sometimes I even warned them, and yet it still went wrong.