Another Strange Error Found
Shoal
10 Aug 2003, 00:10Whenever I try to drop an undroppable object, the game crashes, saying that an overflow has occurred (Runtime error '6').
This used to work; I've changed nothing in the "drop" properties of my game.
Any ideas?
Thanks,
Shoal
This used to work; I've changed nothing in the "drop" properties of my game.
Any ideas?
Thanks,
Shoal
GameBoy
10 Aug 2003, 00:13assumingly, concidering its the Beta of 3.5, there will be hundreds of errors which cause the game to crash. what you need to do is just post the errors on here, and wait patiently for the beta 2. hehe.
Another option, due to the mass amounts of bugs in the new version (no offense alex its obvious there will be bugs at first), is to use 3.12 until 3.5 is 99% bug free, this way, you can get things done without having lots of errors.
Plus, there is a major error with the rooms, where if you change one of the rooms 'player enters room' scripts, it changes another rooms 'player enters room' scripts, so it will be quite difficult to use, in my case anyway.
So your best bet is to use 3.12 for now. If its not priority that you need to get your game done, i guess you could look around QDK for errors. so far ive spotted 3, and i will be posting topics with names such as "Error in QDK (1), Error in QDK (2)" etc.
Another option, due to the mass amounts of bugs in the new version (no offense alex its obvious there will be bugs at first), is to use 3.12 until 3.5 is 99% bug free, this way, you can get things done without having lots of errors.
Plus, there is a major error with the rooms, where if you change one of the rooms 'player enters room' scripts, it changes another rooms 'player enters room' scripts, so it will be quite difficult to use, in my case anyway.
So your best bet is to use 3.12 for now. If its not priority that you need to get your game done, i guess you could look around QDK for errors. so far ive spotted 3, and i will be posting topics with names such as "Error in QDK (1), Error in QDK (2)" etc.
Shoal
10 Aug 2003, 04:05Um, I AM using 3.12, NOT the Beta.
I think Im Dead
10 Aug 2003, 04:35Yeah, generally when you see those errors, also the subscript out of range (runtime error '9') or whatever, it's not a problem with Quest or QDK(directly atleast) but a problem with the code.
If you are coding by hand, than it's probably a small error in your syntax somewhere presumably around the default response for dropping a non-dropable object.
If you are using QDK it may do you good to try and define a response to trying to drop a non-dropable item. I believe it's located in the Text > Standard Messages... section of QDK.
If you are coding by hand, than it's probably a small error in your syntax somewhere presumably around the default response for dropping a non-dropable object.
If you are using QDK it may do you good to try and define a response to trying to drop a non-dropable item. I believe it's located in the Text > Standard Messages... section of QDK.
Shoal
10 Aug 2003, 04:55Strangely enough, I HAVE defined text for that. I've defined individual text for each object *as well as* common undroppable text.
When I don't define individual text, the no text doesn't appears -- not even the common text I entered! It just skips a line and shows the prompt! :?
I assumed it was a program error of some kind, so I defined individual non-drop text for every single object to work around it. It worked for a while, then died suddenly without warning.
I edit using the QDK.
When I don't define individual text, the no text doesn't appears -- not even the common text I entered! It just skips a line and shows the prompt! :?
I assumed it was a program error of some kind, so I defined individual non-drop text for every single object to work around it. It worked for a while, then died suddenly without warning.
I edit using the QDK.
Alex
10 Aug 2003, 12:20I'm not able to reproduce this. When I try:
and
both work fine.
Are you using any libraries which override the "drop" command at all?
If you send me your code I can take a look into it for you.
define object <vase>
take
drop nowhere
end define
and
define object <vase>
take
drop nowhere <Don't!!>
end define
both work fine.
Are you using any libraries which override the "drop" command at all?
If you send me your code I can take a look into it for you.
GameBoy
10 Aug 2003, 15:04do you have error log enabled? maybe it will say something in there
Alex
10 Aug 2003, 17:16The error log won't help when Quest or QDK has generated a run-time error. This means the error is within Quest or QDK itself. It may actually be caused by the game author not entering something correctly, but Quest or QDK should be able to cope with that and print an appropriate message. Since they're not, this indicates a "bug" in Quest, albeit one which I'm not yet able to reproduce.
GameBoy
10 Aug 2003, 21:51albeit?
so if this is quest 3.12 how come ive never seen this error?
so if this is quest 3.12 how come ive never seen this error?
I think Im Dead
10 Aug 2003, 22:27Paste the complete ASL file in code brackets or send it to my email(listed in my profile). I've got a feeling it's related to the syntax, and if it is, I'll figure out what is causing it. Often another line of code will foul things up for a previous one(well not that often, but it can happen).
So, if you feel like it, send it along, I'll give it a shot.
So, if you feel like it, send it along, I'll give it a shot.
Shoal
11 Aug 2003, 11:45ASL sent.