I was looking through the forums and couldn't really find a desend newbie helpline so i though i'd start one.(i'm hoping i'll get some help from ste,coding masters and s1ay3r cos they no hell lot more than me!) so if your a newbie post your questions here and i'll try to answer them afterall everyone has to start somewhere!

actually, codingmasters knows stuff all, Slayer knows just about as much as me (so he says), and that wont be enough to really help. I can help where i can, but if you're looking for more complex things to add, i'd look to these people....

[list]
[*]Alex[/*:m]
[*]MadBrit/Al[/*:m]
[*]I Think Im Dead[/*:m]
[*]Computer Whizz[/*:m][/list:u]

Also, everything is explained in the manual, however, i never really read it i usually ask for help, but i really think i should go through it some time lol.

I totally agree. Those are the best people to go to. Everyone else will be glad to help as well, but they know more than any of us.

Thanks but my points still the same there isn't a decend newbie file and to be honest the help file provided with quest is ok once you no what your doing but for a complete beginner it's dead confusing so i think we should start a newbie file (i have actually been making games for a year or so but only reacently joined the forum)

Hey tom great idea

Ad harwood

So, like my ASL tutorial idea that you guys all thought was lame lol?

So, like my ASL tutorial idea that you guys all thought was lame lol?

I for one certainly didn't suggest it was a "lame" idea, seeing as though I wrote the previous ASL tutorial I'd be foolish to do so really

As I said, I'm no longer convinced that there is much of a 'readership' out there for a new ASL tutorial, it seems there aren't that many users of Quest who are both unhappy with using QDK and cannot already program to the level required to use ASL effectively.

I've no idea of how many downloads/registered users Quest can boast, but I'm pretty sure that the 'active' Quest community is very small indeed and of that small community only a few would be interested in/need a tutorial.

If you feel inclined to do so, go ahead and write a new ASL tutorial, I am sure there will be a few people who will appreciate it, but be aware you are taking on a LOT of work, for no reward and for the benefit of a very limited audience.

Al (a.ka. MaDbRiT)

Hey s1ay3r i think a asl tutorial sounds wicked you could almost like make a game tutorial thing usin qdk or sommat

Hmmm. Interesting. I was going to use the .chm (HTML Help) but I guess a in-game tutorial might be cool. Anyone think this is worth the time? I could start work soon (maybe after this weekend, I'm at a friend's)

I'm a newbie, having gotten into Quest in the last 3-4 weeks. I am using QDK, which I think is a great GUI, even though I understand programming concepts and a couple of non-ASL languages. I think a tutorial would be nice, as well as possibly a newbie forum (however, I have learned a lot quickly by going over this forum). I did have some difficulty in understanding the relationships between types and properties, but I am starting to get the hang of it. I also am mucking along with procedures and functions. In short, I think there are areas that could be addressed by the experts (if possible) that might help explain the "how to's" a little more thoroughly.
I must say that I fully understand the tremendous amount of work involved in creating a language and program like Quest, let alone prepare a huge manual to go along with it. That's why these forums are so great - to help us all find mutual help.
Anyways, that's my 2 cents, and I sincerely thank everyone for their posting here so this dumby can learn the ropes. I apologize if this is too long.

OK. Another question now:
What kinds of things are you especially having trouble with? I'll write a basic tutorial, maybe tonight. Then I may write some more advanced tutorials. Input is kinda helpful, though.

i have to disagree im afraid. i know what its like to be a complete newbie, and concidering i was a newbie when QDK wasnt all that good, i had to ask alot of questions. But, QDK now is more advanced and alot better. it's almost idiot proof!

I never read the help file for 3 years, and even now i fail to do so lol, but i dont think a tutorial is needed. I wouldn't waste your time. Plus, if somebody was to make a tutorial it would be best if the people who i listed did it as they know the ins and outs, and the depths of the language.

It's not hard to write a tutorial. Especially a basic one. You really don't think I'm capable? Sometimes you surprise me, Ste.

lol i never said anything! lol. do what you want who cares lol

If you want to write a tutorial, Slayer, write one. It'd certainly be a handy thing for newbies to have.

And, Ste? You've been using Quest for three years yet I don't see any games you've written. Have I missed them?

nope, i dont submit games to the archive, i'm not fond of single player games.

The whole reason of having these forums is so that newbies can ask questions. The Quest Documentation is also sort of a newbie tutorial!

Matthew G.

Thank you, Codingmasters. I thought that forums were around so that anyone (newbies included like me) could ask questions and get answers. In following some of these threads over the last few weeks, I sometimes get the impression that isn't the case - that what may seem like important questions by "newbies" are treated as dumb or below the current level of "expert" learning, or that maybe the questions shouldn't be asked because "we all got past that a long time ago - why bring it up again?". If that's how things are to be, then I don't think the Quest community will ever grow.

The quest community is small because most text-based makers are using Diku or Smaug. Also, not alot of people nowa days are really into making MuD games, but instead, making 2D RPG Maker style games, or 3D FPS games. Also, if you would like to give me some examples where we have slagged off newbies, that would be much appriciated, unless of course it's related to Codingmasters because he just wound up the whole community by being a spammer and a pain in the ass. he's seemed to have calmed down now though

Newbies questions are fine - and most of the time are answered just fine and dandy.

I ask the idiotic question every now and then, but I don't get everything blasted out of me.

Ste asks the sensible question every now and then (hahahaha) and get's the jolt taken out of him half the time because we know him.

Slayer - do a tutorial with a purpose (as you posted already askign for specification I know that YOU know this already). A general tutorial is useless for newbies because they should go through the help file - but don't because it's too big and forboding.... Which is what your tutorial will end up being.

Just have something like "custom commands" and having a brif overveiw on the things you pass on your way to doing them.
Also, maybe a "script" thing where you just say : "go through all these things, typing in different things and see the outcome. Learn that way" and stuff like that.

I pick stuff like this up naturally so I can't help you out really - but go for a way to BEGIN to create a game. Rooms, objects, commands, storyline and stuff.

Computer Whizz wrote:
Ste asks the sensible question every now and then (hahahaha) and get's the jolt taken out of him half the time because we know him.

Love you too.


OR...

just do an FAQ. i am good at writing FAQ's

S1aY3R wrote:OK. Another question now:
What kinds of things are you especially having trouble with? ...

I would agree with reelyor, types and properties would be a good tutorial subject. Unlike ste I have read the manual (twice) in the last coule of weeks while playing with the program and the relationship between types and properties are still somewhat foggy. While QDK does make the whole process much easier and the forms are available, having a some tutorials would be nice.

Heck, I'd like a tutorial on forum abriviations and how to get those really cool pictures with your signitures.

Erm - it's classic UBB tag's - there IS an FAQ for that and it's after you click on "BBcode" on the left of your screen when you reply to something... Under "options".

Right. Types are just present properties for objects.

Say you wanted something as a book, then you create a "book" type, with properties "obj=book" and "descr=Book", and assign the object with the type. Now it has the properties obj=book and descr=book.
..... I personally can't see a purpose in this because every object should be different... Except maybe money - which will be different amounts anyway. I don't see the benifit myself.