After editing my game for a while in notepad I tried to load it with QDK again and got the following error:

FATAL ERROR: Too many > in for each object in <#quest.currentroom#> if is <property;lt;#quest.thing#; character>> then ...

I've searched file several times but can't find the error. I've tried searching for '>>' 'if is' and a few other phrases but found nothing. It's even worse because I remeber seeing something that looks strange when scrolling past it but ignored it, and I'm sure that was what the error is. Can anyone help? I can send you the file if you need it.

Search for #quest.thing#

That error is a bit mixed, but basically it's saying there's an error in an if, which has the comparison less than ( < ).
maybe you have an "if (property<#quest.thing#; character>)"...

One thing Quest is crying out for is better error messages. I've had them myself sometimes and they've been so vague it's difficult to figure out just what's wrong.

Christopher wrote:After editing my game for a while in notepad I tried to load it with QDK again and got the following error:

FATAL ERROR: Too many > in for each object in <#quest.currentroom#> if is <property;lt;#quest.thing#; character>> then ...

I've searched file several times but can't find the error.

Ahem... QUEST is actually SHOWING you where the error is in that error message

Look at the second if - then part of your code, you have TWO ">"'s right after the word 'character' - Quest is telling you you have too many ">"'s...

Count the "<"'s and ">"'s in the whole block of code... TWO opening "<"s and THREE closing ">"s.

Now these < & > should always be in complete pairs, so remove one of those two ">"s that are together and try that.

F.W.I.W. I cannot think of instance in Quest where one should ever have two "<"s or two ">"s together like this, so it is one to watch for.

Al (MaDbRiT)

I'll repeat myself for clarification: I've tried searching the file using notepad for '>>', 'if is', 'property;lt' and a few other combinations and found NOTHING. I've had to start searching my 100k + file by hand... this is going to take a while... (sigh).

Ahem... QUEST is actually SHOWING you where the error is in that error message

A change to what I said before:

"One thing Quest is crying out for is nice and clear error messages that don't require a degree in computer science to understand what's wrong."

Kind of reminds me of the Windows XP error messages I used to have flash on screen, the kind that go along the lines of:

"Windows has encountered an error at 011100348844050 in dxggggxgxg and must terminate"

Ah! Crystal clear!

I think CW is on the right track. The line in the ASL file probably looks something like:

if (property < #quest.thing#; character>)

which looks pretty messed up.

I'd do a search for "#quest.thing#; character". It sounds like there is a malformed "if" which is being mutated into something peculiar as Quest parses it.

If you can't find it, email me the ASL file and I'll take a look.

I finally found it! (does a small dance)

And now I've got a regular missing } message instead!

(sigh)

This is going to set my demo release date back a least another week. Oh well, thanks all.

Yes, I've had some awfully wrong if's go wrong... Giving messages of "if is not <#something#;lt;#otherthing#>" and things like that.
The only real reason I know about that lt - although I can't remember why it was an error in the first place.

If your "if"s go wrong, please see if you can reproduce the problem consistently - if so, send me an email and I'll look into the problem.

Oh don't worry, it was my own fault not the programs. I was scripting by 'hand' in Notepad.

Alex, did you ever fix that bug I had with if procedures? That would be the one where you would get missing brace errors and such when you had multiple if/else nested within each else.
Example:
If jfhjsd
then fjsdhd
else {
if sdie8d
then jfjdjdf
else {


Obviously that isn't even coding but it gives the general idea. After this it would either:
A.) Erase my procedures, or
B.) missing brace or some other error (read past posts)

But that doesn't always happen does it? Could you please send me some instructions for reproducing this error consistently?

I'm not sure if it happens anymore. When I first reported this it happened every single time I had at least 7 of those nested within an else. Also, it was only in QDK.