It would be great if either `print` or `puts` worked.
I have to admit I kind of like that it doesn't. All games have artificial constraints and I feel like keeping you from inspecting too much of the internal state is a reasonable one for this.
RubyWarrior - Bloc
21–30 of 70 posts
Re: RubyWarrior - Bloc
#22Feature request: After you've beaten it once let you go through all levels with the same code. Right now it doesn't let you use the features it hasn't told you about.
Re: RubyWarrior - Bloc
#23Cool idea, but I don't think it makes sense for there to be both a Player class and a warrior object. They seem like they are/should be one in the same. At the very least, I think behind the scenes, the Player class should look more like this such that the warrior object is always available, and I don't need to pass it around from method to method that I define. e.g.: class Player attr_reader :warrior def initialize(…
You could always just do that.
Re: RubyWarrior - Bloc
#24Oh man, I love this!
I especially loved this: "warrior.feel.empty?". Allova sudden my RubyWarrior's getting all existential!
Re: RubyWarrior - Bloc
#25Had a lot of fun with my rusty Ruby on this game. Here's my solution to beat level 3 onwards:
Re: RubyWarrior - Bloc
#26It would be great if either `print` or `puts` worked.
I have to admit I kind of like that it doesn't. All games have artificial constraints and I feel like keeping you from inspecting too much of the internal state is a reasonable one for this.
I would like it to debug my own code. You are more aware of the artificial nature of the variables you create, so it’s not as world-breaking to inspect their contents.
I saved a `health_change` variable in my code, and decided what to do based on that, but the warrior did the wrong thing. I wanted to see if my variable was being set correctly by printing it each turn, but I couldn’t. My normal tool for understanding what was going on is missing, so I was forced to guess at the bug. I finally got it to work by reversing the order of two terms in my formula for `health_change`, but it was a lot harder to understand what was going on when I could only guess at or simulate the values of the variables.
Re: RubyWarrior - Bloc
#27Very cool! Proud to see that it's made with ImpactJS[1] (my game engine :)) [1] http://impactjs.com/
Hey! You made ImpactJS? That's very cool, but it's really hard to commit $99 to buy an engine when I can't even try it! It looks super-rad and I'd love to give it a shot, but it's a bit high of a bar for a casual game dev.
If you buy it and don't like it for whatever reason, I can give you a full refund within the first month. That's easier for me to handle than a separate trial license.
Re: RubyWarrior - Bloc
#28Great...but how about turning down the music volume. It's 2:20am here, I opened the page and had a trouser changing moment and woke up the neighbours.
Re: RubyWarrior - Bloc
#29Earlier quoted context omitted.
Hey! You made ImpactJS? That's very cool, but it's really hard to commit $99 to buy an engine when I can't even try it! It looks super-rad and I'd love to give it a shot, but it's a bit high of a bar for a casual game dev.
If you buy it and don't like it for whatever reason, I can give you a full refund within the first month. That's easier for me to handle than a separate trial license.
I never thought about it that way.
Totally stealing that idea.
Re: RubyWarrior - Bloc
#30They should also add the intermediate levels as well
https://github.com/ryanb/ruby-warrior/tree/master/towers/int...