From 4b8b9f9c33b155b8ce259438402b0a854669d49d Mon Sep 17 00:00:00 2001 From: Taoidal Date: Sat, 10 Aug 2024 19:37:17 +0300 Subject: [PATCH] Update 02-player-movement.md Fixed "tick is running once every 60 seconds" --- src/02-player-movement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/02-player-movement.md b/src/02-player-movement.md index a7c282c..57d50c9 100644 --- a/src/02-player-movement.md +++ b/src/02-player-movement.md @@ -51,7 +51,7 @@ That calls the `puts` method and passes our variable `name` to it as a parameter `||=` in English is "or equals". That code above, `args.state.player_x ||= 120` would be read as: assign the property `player_x` on `args.state` the numeric value of 120 unless it's already assigned a value. -Remember how tick is running once every 60 seconds? We don't want to always set `args.state.player_x` to `120`. We just want to set it to that initially and then we'll update that value when we press keys on our keyboard or buttons on our gamepad. We haven't done that yet, but that's what's next. +Remember how tick is running 60 times every second? We don't want to always set `args.state.player_x` to `120`. We just want to set it to that initially and then we'll update that value when we press keys on our keyboard or buttons on our gamepad. We haven't done that yet, but that's what's next. Wow! That was a lot of explanation for two measly lines of code. But I'm telling ya, they're two really important lines of code when it comes to game programming.