Doors!
iaindickinson
10 Sept 2011, 15:54Hi all
I know it's a very simple problem but I'm only just getting started and can't seem to find a simple explanation in the tutorial.
What is the easiest way of creating a door and allowing it to be opened/closed (enabling access to an exit accordingly) without running a script if possible???
I'll deal with the lockable door (I can do that but it can still be opened/closed before it's unlocked at the moment) after that.
Thanks
I know it's a very simple problem but I'm only just getting started and can't seem to find a simple explanation in the tutorial.
What is the easiest way of creating a door and allowing it to be opened/closed (enabling access to an exit accordingly) without running a script if possible???
I'll deal with the lockable door (I can do that but it can still be opened/closed before it's unlocked at the moment) after that.
Thanks
Alex
10 Sept 2011, 16:58One way of doing it would be this: For your "door" object, on the Container tab, make it "Openable/Closable". Then in "Script to run when opening object", unlock your exit. Similarly in "Script to run when closing object", lock the exit.
I know it's a script but it's only two commands!
I know it's a script but it's only two commands!
iaindickinson
10 Sept 2011, 18:01Thanks Alex.
Can I just say first of all what a genius piece of work Quest is. When I was younger playing on a Spectrum 48K (you probably can't remember it) I used to love text adventure and tried to program in Basic to create one, never quite mastering it. Now I have the ability to combine two ambitions; creative writing and making my own interactive game. Thanks again.
Anyway, that sounds easy and I guess if it is not a "lockable" door (in the game from the player's perspective) I can change the default messages from "It is locked/unlocked" (or whatever, etc) to "the door is shut/open"? Otherwise a simple open/close door would seem like you needed a key?
I'll get back on here with the (inevitable) further problems.
Cheers
Can I just say first of all what a genius piece of work Quest is. When I was younger playing on a Spectrum 48K (you probably can't remember it) I used to love text adventure and tried to program in Basic to create one, never quite mastering it. Now I have the ability to combine two ambitions; creative writing and making my own interactive game. Thanks again.
Anyway, that sounds easy and I guess if it is not a "lockable" door (in the game from the player's perspective) I can change the default messages from "It is locked/unlocked" (or whatever, etc) to "the door is shut/open"? Otherwise a simple open/close door would seem like you needed a key?
I'll get back on here with the (inevitable) further problems.
Cheers

guzmere
28 Jan 2012, 18:31i remember the spectrum 48k and the commodore 64 I also learned to program in basic and try to create an adventure. But while this quest is a powerful program I too am having slight difficulty with it. All the best with it I'm sure it will sort itself out just got to stick with it I suppose.
derekb
29 Jan 2012, 08:09Apparently, there are many who are discovering Quest at the same time (as I) ...
I find it equally interesting that those discovering it came from the time when BASIC was a key program for text-adventures and the systems we worked on when making them. In part, I think that is why I am so happy to find Quest, as it reminded me of those days and it also reminded me that I still remember virtually everything in programming from those days and how extensive my games were.
I know this doesn't fit into the topic of 'doors!' but it is nice to know that I wasn't the only one who enjoyed making and playing text adventure games when home computing appeared for the first time.
For myself, it was the Vic-20 and then the Commodore 64 and eventually Basic+ on the early IBM Comp. I still have most of the Compute!, Compute Gazette! and Run mag'es store in boxes .... and if I really looked for it, my text adventures (on tapes and floppys, which were written in Basic and then coverted to machine language [with a different program from one of those mags]) ....
Cheers,
derekb
I find it equally interesting that those discovering it came from the time when BASIC was a key program for text-adventures and the systems we worked on when making them. In part, I think that is why I am so happy to find Quest, as it reminded me of those days and it also reminded me that I still remember virtually everything in programming from those days and how extensive my games were.
I know this doesn't fit into the topic of 'doors!' but it is nice to know that I wasn't the only one who enjoyed making and playing text adventure games when home computing appeared for the first time.
For myself, it was the Vic-20 and then the Commodore 64 and eventually Basic+ on the early IBM Comp. I still have most of the Compute!, Compute Gazette! and Run mag'es store in boxes .... and if I really looked for it, my text adventures (on tapes and floppys, which were written in Basic and then coverted to machine language [with a different program from one of those mags]) ....
Cheers,
derekb
