Hacker News Reader

Comment by gafferongames | Hacker News Reader

These guys don't know what they don't know:

"Now let's make shots work. When I shoot, send the shot as a topic, and make it affect the target's HP. When the target HP goes to zero, they should die and respawn."

This is not how shooting is implemented in a competitive first person shooter.

View on HN

"At the end, all models built real a multiplayer FPS, with zero code written by hand! That’s pretty darn cool."

If you don't understand how a multiplayer FPS works, how can you tell if the AI has actually created one for you or not?

Many children who play videogames can tell you what a multiplayer FPS is, and most of them don't know how to code it.

I did not say what a multiplayer FPS is. I said "how a multiplayer FPS works".

There is a difference.

I agree that this is not how shooting is implemented in a production competitive shooter, but that wasn't the goal of the post. We wanted to test how far models could go, and I think this current version is the limit in a 2 hour time window.

I think you could have an infinite amount of time and you still wouldn't be able to create a real first person shooter.

Right, but you don't need to know how it works to know if it is one. Unless I'm misunderstanding this part: "how can you tell if the AI has actually created one for you or not?"

I interpreted that as "I asked the AI to make me one, and now I have one, so it did it," with the operative question being "is it really a multiplayer FPS?"

I'm a professional game developer who has worked on real multiplayer first person shooters. My bar for "is this a real first person shooter" is a lot higher than yours.

My bar is, does this actually work and is it best practice for how first person shooters are made by professional game developers.

Your bar is, does it kinda look a bit like the thing that I play?

Totally different things.

Agree to disagree, then.

Reply on news.ycombinator.com