cube-tube/SCALE_DOCS.md

Scale Docs

Everything you need to get started with using Scale.

Check out the CHANGELOG for the summary of recent changes!

Quickstart

Once you've got your game from the Scale template dropped into your mygame directory in your DragonRuby GTK game, here's what you'll want to do next.

Configure

Start by specifying your name and game title in metadata/game_metadata.txt. The following properties are useful:

• devid — your itch.io username, no spaces
• devtitle — your name, spaces are okay
• gameid — the URL slug of your game on itch.io that you must already create, no spaces
• gametitle — the name of your game, spaces are okay!

Now when you start the DragonRuby engine for your game, you'll see what you've set.

Lay of the Land

Because all of Scale is included with your new game, you can just browse through the source code to get the lay of the land. You'll notice in the app/ directory a bunch of files! It's okay, don't worry. It's pretty sensibly organized, and there are plenty of comments.

Explore, be curious, and change things to suit your needs.

Scale is structured to follow the default DragonRuby GTK way of working with methods and args.state. That drives how much of it works. Most of Scale is organized into modules so that there aren't method name conflicts in the global space.

Gameplay

Open up app/scenes/gameplay.rb, as that's where you'll actually add the fun parts of your game. Scene.tick_gameplay is just like the regular ole #tick in DragonRuby GTK. It takes args, and you go from there. It does include some handy stuff though, but just let that be.

You'll code your game just as you normally would. If you're new to DragonRuby GTK, check out the book to get started.

Input

Scale comes with some helper methods to make checking for input from multiple sources (multiple keyboard keys and gamepad buttons) easy. That code lives in app/input.rb, and out of the box, you get:

• primary_down? — check if J, Z, Space, or Gamepad A button was just pressed
• primary_down_or_held? — check if J, Z, Space, or Gamepad A button was just pressed or is being held
• secondary_down? — check if K, X, Backspace, or Gamepad B button was just pressed
• secondary_down_or_held? — check if K, X, Backspace, or Gamepad B button was just pressed or is being held
• pause_down? — check if Escape, P, or Gamepad Start button was just pressed, which pauses the game

You could add more methods for various inputs in your game. Maybe there's a secondary button you use. Or any number of them! These input methods make it really easy to support various input methods without worrying about the keys/buttons that are being pressed. Want to add a new key for a given layout? Just change it.

Here's an example of how you'd use it if you wanted to have your player swing their sword:

if primary_down?(args.inputs)
  swing_sword(args, args.state.player)
end

Text

You'll very likely need to display text in your game to show health or the player's level or to give instruction. It's a fundamental part of game user interfaces. app/text.rb contains a few helpful constructs to make working with text easier.

First is the TEXT Hash constant. It contains key values of the text to display in your game. This is preferable to putting strings everywhere because you can more easily review the text for typos and eventually translate your game much more easily. It takes a little time to get used to putting your text here first, but it'll become second nature quick enough. You'll see text for what already exists in Scale.

#text is a method you call to access the values in TEXT. Example:

text(:start)

returns "Start".

Then we've got the #label method. It contains sensible defaults for outputting labels quickly with DragonRuby GTK. It's got a friendlier API than the default data structure in DRGTK. There are multiple ways to use it.

In its simplest form, you can pass in a symbol key for TEXT and specify the position to render it:

args.outputs.labels << label(:start, x: 100, y: 100)

You can also pass in a value, like a number that will display:

args.outputs.labels << label(args.state.player.level, x: 100, y: 100)

Additional parameters are supported too, all the way up to something like this:

args.outputs.labels << label(
  :restart, x: 100, y: 100, align: ALIGN_CENTER,
  size: SIZE_SM, color: RED, font: FONT_ITALIC
)

In app/text.rb you'll find the constants for text size and the various fonts. Change them as you'd like!

Sprites

A lot of games need sprites, and when making them, it's so helpful to see them in the context of your game. DragonRuby GTK allows you to reload sprites in your game, but you need to specify which ones to reload. To get around this, in Scale you track your sprites in app/sprite.rb's SPRITES hash. It's a little tedious, but by having a dictionary of sprites, they can easily be reloaded with i when developing your game.

Get the path for your sprite with Sprite.for(:key):

args.outputs.sprites << {
  x: 100, y: 100, w: 32, h: 32, path: Sprite.for(:player),
}

Scenes

The app/scenes/ directory is where different scenes of your game go. There are scenes for Paused, Main Menu, Settings, and Gameplay. Scale uses args.state.scene to know which scene the game is in.

You can switch scenes by using Scene.switch(args, :gameplay) where the parameter is the symbol of the scene you want. It must match the name of your scene method after the tick_ prefix. So if you wanted a :credits scene, you'd define it like this in app/scenes/credits.rb:

module Scene
  class << self
    def tick_credits(args)
      args.outputs.labels << label(:credits, x: args.grid.w / 2, y: args.grid.top - 200, align: ALIGN_CENTER, size: SIZE_LG, font: FONT_BOLD)
    end
  end
end

(Don't forget to require it in app/main.rb too!)

Then when you want to show the Credits scene, call Scene.switch(args, :credits).

Collision Detection

Scale provides you with a collision method that executes the passed in block for each element that intersects:

collide(tiles, bullets) do |tile, bullet|
  bullet.dead = true
end

It takes arrays or single objects as parameters.

Menus

You'll find examples of menus throughout the Scale codebase for common scenes like Settings and the Main Menu.

Menus support cursor-based navigation or buttons for mouse/touch.

How they work is pretty simple, you just call Menu.tick and pass in an array of menu options.

options = [
  {
    key: :attack,
    on_select: -> (args) do
      # do the attack
    end
  },
  {
    key: :defend,
    on_select: -> (args) do
      # defend
    end
  },
]
Menu.tick(args, :your_menu_name, options)

The options array is just a collection of hashes with a key and an on_select lambda that gets called with args for doing anything in your game that you need to have happen.

Menu.tick also supports an optional menu_y for positioning the menu.

Colors

A simple color palette is provided in app/constants.rb. Most of the primary colors are present, along with some variants. They return Hashes with r, g, and b keys. If you have a sprite that you want to change red, you'd do this:

args.outputs.sprites << {
  x: 100, y: 100, w: 32, h: 32, path: Sprite.for(:player)
}.merge(RED)

Sound Effects & Music

Scale comes with a few helper methods to make playing music and sound effects easy, as well as settings to enable or disable their playback.

Play a sound effect:

play_sfx(args, :enemy_hit)

the symbol (or string) file key for the file must correspond to the file's name in sounds/.

Here's how to play music:

play_music(args, :menu)

the symbol (or string) file key for the file must correspond to the file's name in sounds/.

You can pause and resume music easily with:

pause_music(args)
resume_music(args)

Scale assumes only one music track can be playing at a time.

Adding New Files

When you add new code files to app/, just be sure to require them in app/main.rb.

Debug Tick & Development Shortcuts

When you're making a game, you often want to have easy shortcuts to toggle settings. Maybe you want to make your player invincible so you can easily test changes out. app/tick.rb contains a method called #debug_tick that's only called when you're game is in debug mode (a.k.a. not the version shipped to players). Anything you put in there will run every tick but only while you make the game.

You'll see there are already three shortcuts Scale gives you:

• i — reloads sprites from disk
• r — resets game state
• 0 — displays framerate and other debug details

Use those as templates to add your own development shortcuts.

You can check for Debug mode in your game anywhere with the debug? method.

#debug_label Method

It's common to need to display debug-only information about entities in your game. Maybe you want to see a value that changes over time. This is what #debug_label is for. It putputs text that's shown when you toggle on debug details with the 0 key.

Here's an example of how to use it to track the player's current coordinates:

# assume we have args.state.player that can move
player = args.state.player
debug_label(args, player.x, player.y - 4, "#{player.x}, #{player.y}")

Tests

The test/tests.rb is where you can put tests for your game. It also includes tests for methods provided by Scale. Tests are powered by DragonTest, a simple testing library for DragonRuby GTK. You'll see plenty of examples in there, but here's a quick overview:

Write tests:

test :text_for_setting_val do |args, assert|
  it "returns proper text for boolean vals" do
    assert.equal!(text_for_setting_val(true), "ON")
    assert.equal!(text_for_setting_val(false), "OFF")
  end

  it "passes the value through when not a boolean" do
    assert.equal!(text_for_setting_val("other"), "other")
  end
end

You've got these assertions:

• assert.true! - whether or not what's passed in is truthy, ex: assert.true!(5 + 5 == 10)
• assert.false! - whether or not what's passed in is falsey, ex: assert.false!(5 + 5 != 10)
• assert.equal! - whether or not what's passed into param 1 is equal to param 2, ex: assert.equal!(5, 2 + 3)
• assert.exception! - expect the called code to raise an error with optional message, ex: assert.exception!(KeyError, "Key not found: :not_present") { text(args, :not_present) }
• assert.includes! - whether or not the array includes the value, ex: assert.includes!([1, 2, 3], 2)

Run your tests with: ./run_tests — test runner script for Unix-like environments with a shell that has proper exit codes on success and fail

Your tests will also run when you save test files and be output to your running game's logs. Nifty!

Debug Shortcuts

You'll find these in the README, too. Scale comes with some handy keyboard shortcuts that only run in debug mode to make building your game easier.

• 0 — display debug details (ex: framerate)
• i — reload sprites from disk
• r — reset the entire game state
• m — toggle mobile simulation

Mobile Development

Use the #mobile? method to check to add logic specifically for mobile devices. Press m to simulate this on desktop so you can easily check how your game will look on those platforms.

Example:

text_key = mobile? ? :instructions_mobile : :instructions

There are convenient methods and tracking for swipe inputs on touch devices. Scale automatically keeps track of them, and if you use the up?(args), down?(args), left?(args), right?(args) methods, they're automatically checked. Otherwise, you can check to see if a swipe occurred with:

if args.state.swipe.up
  # do the thing
end

Make Scale Yours!

This is your game now. Scale is just here to help you out. Change Scale to meet your game's needs.