Zugg Software :: View topic - OK, so I can't seem to handle a simple IF statement

Apprentice Joined: 03 Jul 2006 Posts: 110

I am foraying into the region of writing some more complicated triggers than "If the mud says I can't move, then delete the direction from the que and don't try to move."

I am trying to grab use gmcp info to help me with mapping, finding areas (zones), terrain types, etc. I am starting by trying to make a trigger that captures the zone, compares it to a list of zones, and then adds it and notifies me that I have changed zones if I actually entered a new zone with the last move. Below is the trigger so far - as you can see it isn't very long, but I have already blasted my head against a wall, and made several changes to no avail.

Apprentice Joined: 09 Apr 2008 Posts: 168

Start with each line and do a #SHOW so your first line $newarea=%gmcp.Room.info.area test with #SHOW %gmcp.Room.info.area if this does work then you can move to the next line. should help figure out where it's derping out.

Apprentice Joined: 03 Jul 2006 Posts: 110

The gmcp variable is being captured correctly and transferred to the temp variables- the #SAY command spits out the correct values for the current and previously entered room. It is just everything after that where I run into trouble. For some reason I am missing the correct syntax on the #IF statements and just can’t find what it is.

Mike

Posted: Mon Mar 06, 2023 9:31 pm

You need a space between one closing bracket/parentheses and the next opening bracket.

Apprentice Joined: 03 Jul 2006 Posts: 110

Yes, just found that out...

Formatting will be the death of me, and proofreading your own code sucks. I once spent five days in college going over a simple 30 line assembly program with no luck only to have a TA look at it for 5 seconds and then give me a rather glib "You used JUMP instead of JMP in that second to last line of the program..." In my own defense, in that case the assembler didn't even throw an error, it just threw a bunch of meaningless machine code into the card that I was trying to interface to a keyboard matrix (or something like that - it's been 30 years).

Thanks for the help.

Mike

At least I can now get both IF statements to work. Also, the documentation for #ADDITEM should be changed to indicate that it WILL add duplicate items to a stringlist.

Posted: Mon Mar 06, 2023 10:57 pm

#ADDITEM does not add duplicates, but %additem does.
Might be the difference of a trailing space if #ADDITEM seems to make a duplicate.

Apprentice Joined: 03 Jul 2006 Posts: 110

Didn't use the function, only the command, and using the $newarea temp variable pulled directly from the gmcp data on repeated looks without moving I ended up with about 10 copies of the area name. I did have the settings editor open, viewing/editing either the trigger or the variable - I wonder if it could have affected the ability of the program to detect the fact that the entries were duplicated? In any case, with the formatting of the if statement working, I can check it before trying to add it, or do more testing to see what was happening.

Apprentice Joined: 03 Jul 2006 Posts: 110

OK, I can confirm that, for some reason, the #ADDITEM command does indeed add duplicates for me.

Continuing on and adding to the trigger I have been working on, here is the trigger:

Posted: Thu Mar 09, 2023 6:40 pm

Very odd behavior. as the #HELP file explicitly states it won't do that.
Try using %trim on the value to trim away any whitespace padding.

If that doesn't work, suppose it's possibly a corruption issue.

Apprentice Joined: 03 Jul 2006 Posts: 110

Thought I'd come back and add a conclusion to this thread, in case someone sees it later and wonders what is going on.

As covered in another thread, the issue with the #ADDITEM command turned out to be a variable type issue. When adding a variable of a type that is NOT a string, the variable will be added but the built in process that checks for duplication will fail. This specifically includes a stringlist, even if it has only a single entry. A stringlist compared to a string will show as unique, but when added, will become a string, which will then not be matched against the next time that same stringlist is added (wash, rinse, repeat). In this case a single entry stringlist was created because it came in a gmcp packet that identified it as a stringlist - entries enclosed in square brackets are interpreted as stringlists regardless of how many elements are included, and entries in curly brackets {} become database variables.

Mike