|
Axe Software Forums
Quest Developer Forum using Quest 2.0
|
Author | Topic: using Quest 2.0 |
passerby |
posted 03-06-2001 18:58 GMT
hello everybody, This post is rather long, so u might want to skip if short on patience. i have just started using Quest, as a first time game writer, and had a couple of things to say about it. first, the good. Thank you for Quest 2.0, which is a brilliant program, that both succeeds at simplifying creating adventure games without reducing the power to create complicated interactions. Secondly, though i admit i have not used any other graphical adventure scripting languages, i have seen screenshots, and can not find anything that looks like it has a better user interface. The QDK 2.0 interface makes building games easy and, well, almost as much fun as playing them afterward. second, the bad. I have encountered a few bugs in the QDK, but i will describe only one because the rest are trivial by comparison. I'm sorry to say something so bad about a product that is in every other way so good, but this is a serious error that could easily lead to a new game writer losing their entire work - especially since this error will not show up until after a considerable amount of work has been done on a game. It means that the writer has to have a complete design of their game, and can create it all at once, without need to reconsider any part of that game. I doubt those on this board who have written any games will consider this realistic. thank you. |
MaDbRiT |
posted 04-06-2001 02:03 GMT
Hi there, I must admit I tend to code Quest games in a text editor, so I have little experience of using Q.D.K. beyond the more basic functions. What I do know is that Alex (Quest's creator) is very responsive to bug reports, and makes every effort to correct problems when they are reported to him. Something as complex as Quest /Q.D.K. will inevitably have some bugs that only emerge in 'real world' usage, not in beta testing. My first thought is to ask if you using the very latest versions of the Quest software? I think Quest 2.19 & QDK 1.02 are the current issues. If you don't have these, it might be a good idea to download them forthwith! If you do have these, then a bug report is probably in order Al |
Alex |
posted 04-06-2001 11:58 GMT
quote: What precisely are you trying to remove? In all my tests things are removing properly.
quote: Everything works fine in my own tests - would you mind posting the exact steps you went through so I can reproduce the problem? As MaDbRiT says, please check that you are running the latest version of Quest and QDK - the latest version of Quest is v2.19 and the latest QDK is v1.02. |