this post was submitted on 08 May 2024
104 points (99.1% liked)

Games

16785 readers
850 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. 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
you are viewing a single comment's thread
view the rest of the comments
[–] meteokr@community.adiquaints.moe 29 points 6 months ago (5 children)

After this article I've started binge watching this whole channel. Extreme in depth analysis and code walking of NES games in assembly is so interesting. Really makes you appreciate how small and simple the platform was. "Optimizing" a game really feels like a noticeable difference. I also learned how Gameshark codes work, they're just editing addresses and OP codes directly.

[–] Theharpyeagle@lemmy.world 1 points 6 months ago (1 children)

Not quite the same, but if you're into this stuff, I highly recommend the channels pannenkoek2012 and Retro Game Mechanics Explained. Both very in depth channels about Nintendo jank,

[–] meteokr@community.adiquaints.moe 3 points 6 months ago

pannenkoek2012, the legendary half an A press guy! I watch a fair bit of retro game speedrunners so he's practically required viewing in that space.

load more comments (3 replies)