| class Game | |
| attr_gtk | |
| def initialize | |
| @dvd = { | |
| x: 640, | |
| y: 360, | |
| w: 64, | |
| h: 64, | |
| dx: 5, |
| class Game | |
| attr_gtk | |
| def initialize | |
| # rng is sent to Random so that everyone gets the same levels | |
| @rng = Random.new 100 | |
| @solved_board = (1..16).to_a | |
| # rendering size of the cell |
| def tick args | |
| if Kernel.tick_count > 518 | |
| puts "#{args.state.dvd}" | |
| GTK.slowmo! 30 | |
| end | |
| args.state.dvd ||= { x: 640, | |
| y: 360, | |
| w: 64, | |
| h: 64, |
| # creation of a game class | |
| class Game | |
| attr_gtk # adds arg properties to the class | |
| def initialize | |
| # have the hero start at the center and the npc be at the far right | |
| @hero = { x: 640, | |
| y: 360, | |
| w: 80, | |
| h: 80, |
| class Game | |
| attr_gtk | |
| def initialize | |
| @player = { x: 30, | |
| y: -16, | |
| w: 32, | |
| h: 32, | |
| dx: 0, | |
| dy: 0, |
| # ~/.tmux.conf | |
| # * brew install tmux reattach-to-user-namespace | |
| # * C-e - Your leader <l> key. | |
| # * <l>: - Type command not handled by shortcut keys. Eg: <l>: kill-pane ENT | |
| # * <l>r - Reload this file/config. | |
| # * <l>j - Select split using number jump list. | |
| # * <l>{ - Swap splits left. | |
| # * <l>} - Swap splits right. | |
| # * <l>| - Create vertical split. | |
| # * <l>- - Create orizontal split. |
| CtrlShiftShortcuts=yes | |
| Font=Dank Mono | |
| FontHeight=14 | |
| Black=31,33,39 | |
| Blue=77,156,238 | |
| BrightBlack= 31,33,39 | |
| BrightBlue= 77,156,238 | |
| BrightCyan= 68,168,182 | |
| BrightGreen= 134,187,98 | |
| BrightMagenta= 185,89,216 |
| class Game | |
| attr_gtk | |
| def initialize | |
| # keeps track of particle states | |
| @particles ||= [] | |
| # keeps track of whether a render target for the specific number | |
| # has been created already | |
| @created_prefabs ||= {} |
Lua is a great language. Whenever someone asks me how they can get started with game dev, I immediately point them to Lua and PICO8. The simplicity of Lua comes with a potential downside. As your skills as a coder grows, you’ll begin to hit the language’s limitations. Lua is something you’ll eventually outgrow.
When you feel like you’re hitting the limits of the Lua, consider Ruby as your next goal. The syntax will come naturally to you given that you’ve used Lua.