you are viewing a single comment's thread
view the rest of the comments
[–] 34 points 3 years ago (4 children)
  1. Don't roll out your own crypto suite
  2. Don't write your own game engine
  3. Don't create your own OS from scratch
  4. Don't build another multipurpose framework
  5. ...

Whom am I kidding, go do all of that! Learn why you most probably shouldn't 😆

  • source
  • hideshow 8 child comments
  • [–] 25 points 3 years ago (3 children)
    1. Don't make an MMORPG as your first ever game with only you and your one friend as devs
  • source
  • parent
  • hideshow 6 child comments
  • [–] [S] 8 points 3 years ago (1 child)
  • [–] 8 points 3 years ago* (1 child)

    Yet depressingly common in MMORPG circles. People tend to vastly underestimate the amount of work needed to get an remotely playable MMO off the ground.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 3 years ago (1 child)

    What is this smell? Is that the smell of self experience?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 3 years ago (1 child)

    What if I make an OS that's also a game engine?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 6 points 3 years ago (1 child)

    Hear me out: a fully fledged desktop environment, like KDE Plasma or Gnome, but it's a 3D world - "windows" are just walls, the file explorer is just a bunch of procedurally generated condos, and you get a Gmod physics gun to move stuff around.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 3 years ago (1 child)

    I want to learn how to write a physics engine.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 3 years ago

    Those are easy, unless you want 128bit resolution, relativistic effects, collisions, or fancy stuff like that.

    PS: Bonus points if you write one without collision detection, then sell it as a game on Steam.

    PS2: Super Bonus points if you make it 64bit, then keep crowd-funding it for 10 years.

  • source
  • parent