Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs

DragonRuby Game Toolkit

An intuitive 2D game engine. Fast, xplat, tiny, hot loaded. · By DragonRuby

Feedback thread

A topic by connorshea created Apr 20, 2019 Views: 436 Replies: 14
Viewing posts 1 to 11
(+1)

I don't want to make a new topic for every little thing I want to suggest, so I'll just start posting comments in this one :)

(+1)

It'd be nice to have built-in aliases for a few basic colors, essentially you'd be able to provide symbols as the argument for colors, e.g. :red, :orange, :blue, :green, :yellow.


Would that work, or do we want to keep to just RGB values?

(1 edit) (+1)

I'm not sure if it's just me, but it doesn't seem like golf_with_musical_notes is actually playing sounds. macOS 10.14, not sure if I can provide any other information here.

What version of mruby is this running on? Also, is there good documentation anywhere for what features mruby is missing from cruby?

(+1)

This file has a list of mruby limitations https://github.com/mruby/mruby/blob/master/doc/limitations.md

(2 edits)

The currently used mruby version is 1.9 https://twitter.com/icculus/status/1119557536804483072

(+1)

I feel like doomwipe could be a little bit less seizure-inducing...

Developer

Right?!  This was a last-minute "I need animation to demonstrate that this goes into a render target" and it's awful. The original looked like this, but uh, copyrights:


I'll make that suck less when I get a moment.

I think I've discovered a bug?

Video:


Reproduction steps:

- Open a game on macOS

- Have another application open full screen

- Drag the game into the application's fullscreen space so it takes up part of it

- Resize the game so it takes up less space (more might also work)

- The game will now go back to windowed mode and be stuck with the resize cursor displaying. It no longer takes inputs, as far as I can tell.


macOS 10.14.4 Mojave, I can provide more info if needed.

(+2)

I'd definitely appreciate documentation of all the available methods for the built-in classes, right now it definitely feels like working with a black box :P

(+1)

I'm working on revealing as much as I can in the tutorial at dragonruby.school

(+1)

Oh and I should mention: hotloading is cool as hell, thank you so much for that!

(+1)

If you want to get the available methods of a class you could do this:

def tick args
  # do this only once
  if args.game.tick_count == 1
    # print class of args.grid object
    puts "The class of args.grid is: #{args.grid.class}"
    # print all methods of args.grid object
    puts args.grid.methods.sort.join("\n")
  end
end

Developer

I'm adding all the feedback in this thread to our TODO list to sort through. Everyone feel free to keep adding more!

Developer

Just posted updated builds with most of this feedback incorporated: https://dragonruby.itch.io/dragonruby-gtk/devlog/77694/new-build-4222019