Zugg Software :: View topic - using temp variables / #local to create new variable and/or update variables

Wanderer Joined: 05 Sep 2008 Posts: 53

i am trying to make a one and done counter trigger that creates and/or updates.

my mud sends You think your language#mouse skill has improved.

so I simply use (*) to grab language#mouse as %1

I have also found that some characters break my scripts, namely apostrophe, pound sign/hashtag, and blanks, so my first step was to use use #local

Apprentice Joined: 03 Jul 2006 Posts: 110

There are a couple issues. First, as a general rule, just use your local variable $FixedIt for a single purpose - capturing and storing the variable name. Use other variables your math. Splitting it up into separate steps makes it much easier to read AND TROUBLESHOOT (especially for old guys like me, who can barely tell curly and regular brackets apart, and then barely remember the differences).

$TempInt = @{$fixedIt}
$TempInt=($TempInt+1)
will grab the variable you want and increment the value, storing it in $TempInt

Now we come to the bigger issue - while you can REFERENCE the variable indirectly, it doesn't seem that you can ASSIGN it. So you can pull the data out, but can't change the value of the variable itself.

{$fixedIt}=$TempInt
#var {$fixedIt}=$TempInt

Both of these cause the trigger to fail when compiling. Perhaps Shalimar or one of the other experts can chime in on how to manage an indirect assignment,

Mike

Wanderer Joined: 05 Sep 2008 Posts: 53

Thank you Mike, every little bit helps. I had something come to me while I was reading your post...seems maybe hackey, or may its just me finally understanding how coding works a little better, but %exec($fixedIt) seems to be the solve. the following allows #local variables to be used within my #var command

#var %exec($fixedIt) (@{%exec($fixedIt)}+1) {} {skillNumbers}

also, thank you for inspiring me to learn how to increase the font size so the brackets are easier to read...sadly cannot be combined with the code business

Apprentice Joined: 03 Jul 2006 Posts: 110

Glad you got it worked out. The use of the exec function is a bit of black magic to me - I can read through and figure out what it MEANS, but I am not nearly knowledgeable enough in the workings of CMUD's parser to figure out why it is NEEDED.

Mike

Wanderer Joined: 05 Sep 2008 Posts: 53

Hahahaha....same

Posted: Wed Aug 10, 2022 4:02 pm

Due to the indirect way they are referenced, exec forces things to evaluate/be parsed that otherwise wouldn't.

Personally, I would use a dbVar to handle storage, which means the local variables can be used directly.