Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Akura]

Might be problem with that. While trying to reproduce it, I got another one, this time opening the stats menu after loading.

Spoiler (click to show/hide)

Another odd one about this is that when I crashed before, I was traveling through a desert, but after a I loaded, very shortly after loading and traveling in the same direction as before, I ended up in a forest. The message for the first one looked much the same as the one I posted before(which probably doesn't help).

[Squeegy]

Ok, so quests weren't saving the enemy you need to kill. This resulted in a crash on your stats screen after you loaded. I've fixed this, and removed the debugging coins, and also fixed the bug where it wasn't saving your quest city, either, AND removed the debugging spam when you load a save, AND added a notice to the level autosave. This will probably fix your tavern bug too.

Please redownload from the website.

[Squeegy]

Here's a sneak peek of what I'm working on for the next version:

[BallC420]

Why don't you just release the Ruby instead of only packing it into a Windows executable? Then everyone could play it, Mac or not. Okay, maybe not everyone. But me! I could!

A) I run challenges and if I release the source code (and Ruby is not actually natively compilable), people could cheat very, very easily.
B) People could cheat very, very easily in general.
C) I would much prefer to keep control over it. There are unscrupulous people out there and as nice as it would be to let anyone take a look at it and learn from it, I'd rather not have it stolen. And that's a one way thing; of I release the source code, I cannot ever un-release it. You can criticize me for that if you want, but I'd rather be safe than sorry.

You may want to look into what "compiling" a ruby to exe actually does. All it does is bundle the interpreter and any used ruby packages with the source files and puts a wrapper around it that automatically extracts the files and runs the ruby interpreter. It's not really a security mechanism and it is trivial to get the source code (just look in your temp dir when you run the exe).

[IronyOwl]

Well that was interesting.

First adventurer faffed around a bit, got killed by I don't even remember what.

Second adventurer got an excellent steel machete and proceeded to one-shot nearly everything. Eventually retired him at Level 18. Never did fulfill his lifelong dream of actually getting to use any of his craft skills, though.

[Squeegy]

Why don't you just release the Ruby instead of only packing it into a Windows executable? Then everyone could play it, Mac or not. Okay, maybe not everyone. But me! I could!

A) I run challenges and if I release the source code (and Ruby is not actually natively compilable), people could cheat very, very easily.
B) People could cheat very, very easily in general.
C) I would much prefer to keep control over it. There are unscrupulous people out there and as nice as it would be to let anyone take a look at it and learn from it, I'd rather not have it stolen. And that's a one way thing; of I release the source code, I cannot ever un-release it. You can criticize me for that if you want, but I'd rather be safe than sorry.

You may want to look into what "compiling" a ruby to exe actually does. All it does is bundle the interpreter and any used ruby packages with the source files and puts a wrapper around it that automatically extracts the files and runs the ruby interpreter. It's not really a security mechanism and it is trivial to get the source code (just look in your temp dir when you run the exe).

Well, the best security is obscurity.