Hey,

As a few of you have recently fund out I am kinda new to this site let alone text game making in general. I want to start trying to figure this all out and have downloaded QDK. I have gone through the tutoria, yet still feel rather lost on how to use some of the techniques to its full advantage.

I was wondering if any of you have any good exercises or practices that i could try out that would help me learn some of the basics a little better, such as when and how to you a boolean vs a procedure or what not.

If you have any, let me know and I'll tell you if I figured it out, or if I hate you all and want to dig my eyes out with a spoon. Either way it should be fun...and educational.

Quest comes with a nice tutorial which covers a lot of the basic things you can do. By the time you work through the tutorial, you will already begin to think of ways you can apply what you learn.

Next, I suggest looking at some of the games which are available for download. Even if the theme of the game is not interesting to you, you can still learn a lot from how the author used the abilities of Quest to accomplish a task.

Scobert, it'll be difficult to learn by the tutorial (as you've already mentioned) or perusing others games (since you'll just get lost in the code). You need to learn by trial and error. Does it work? Doesn't it work? What happens if I...? I try to give the easiest explanations as possible, as you've read, because I've been there before, and know you're not going to understand some advanced jargon. I've answered a post in "Creating Games" (a recent one) entitled something like "Fishes in a pond". Open that post up and you'll see my post in logical form explaining how to create a pond with fishes that can be caught a percentage of the time. It uses some more advanced features, and you should be able to extrapolate some other ideas from it. Don't get disgruntled, but don't rely on everyone else to do it for you either (not that you have). Good luck. Tell me how the fishing went.

That's understandable...

I will check it out and let you know...

Basically I think it is going to result in me trying to accomplish something, not being able to get it right, and coming on here saying what I have done and what you suggest I do differently to get the needed result.

I guess I just wanted a jumping off point...but you can't learn to swim unless you dive into the deep end and do it yourself.

Well, that might be true, but you could also drown. I think you'll be safer with ASL though... I don't think the data stream is too deep :}

If you want to look at hand-coding ASL files, what you should do is first make a game in QDK so that you understand the basic principles. Use as many things as possible.

Then open the ASL file in Notepad and take a look at it.