Ok, found a work around that works.

%forage =%forage
setvariable %foragex=%forage%%c

>>put %bulionvar%c

Depending on which FE you use is how to resolve this.

For Avalon/YASSE, I think it would work as $bulion%c$.

~Kyn (Kynevon)

---

Info Page http://kynevon.info
Grimoire of Echoes: http://tinyurl.com/2ac987
Hunting Info: http://tinyurl.com/44jlt
Armor Info: http://tinyurl.com/2h5jcp

Actually tried all four ways.
%forage%c%
%Forage%%c%
%forage%c
%%forage%%c%%

Only doing it the aforementioned way did it actually work.

You're talking about Stormfront, right?

%Forage%%c%

is different from

%forage%%c%

Caps matter in variable names, looks like you made the typo in the one that actually works ;)

Here's a test script that illustrates it working correctly:

setvariable forage yelith

counter set 5

echo ### forage = %forage%

echo ### counter is %c%

echo ### forage+c = %forage%%c%

exit

[Script test is running, Esc to cancel, Shift-Esc to pause]
setVariable: forage=yelith
### forage = yelith
### counter is 5
### forage+c = yelith5
[script done]

Mmmm I think we're talking about two slightly different things. FWIW I can't really agree that you're depicting 'my way' accurately without seeing the code of the 'countertest' script, the pre-existing values of all the variables in use in that example, and without knowing precisely what you're trying to achieve ;)

I think there are two overlapping peculiarities in how SF handles variables at play here.

1) If a variable is undefined in SF, then it will echo back the raw text with percent signs instead of the variable value (Wizard would return null text as I recall).

example:

setvariable forage yelith

echo %forage%

echo %forage

deletevariable forage

echo %forage%

echo %forage

>[Script test is running, Esc to cancel, Shift-Esc to pause]
>setVariable: forage=yelith
>yelith
>yelith
>DeleteVariable: forage sucessfully deleted.
>%forage%
>%forage
>[script done]

Do you actually have a variable named 'forage' you want to use, or only numbered ones eg 'forage1', 'forage2', etc.?

2) Recursive variable names, where the value of one variable is intended to call the value of another variable, doesn't work directly in SF, and I think this is another issue at play.

>It is important to note that "does not work directly" is definately still "works"

Thanks for the assist, Woody, that is absolutely correct. I wrote that post at work and had to log off and leave before I could put in a nice example of that issue ;)

I spent a while tearing my hair out trying to get recursive variables to work properly before I came upon the correct workaround, as you illustrate.

>so as long as it's defined, I don't have to place %forage inside it?

>No, I'm not using %forage%%null%

I'm still having trouble understanding exactly what you want to do.

I was asking if you use %forage% all by itself, without any other numbers or text after it. I think that's what you were saying, but %forage%%null% will be interpreted as "the value of the variable named 'forage' concatenated to the value of the variable named 'null'. Which is different than %forage% by itself so those two are not identical. Gotta be extremely precise and literal when dealing with syntax, you know ;)

Put another way... Do you have a variable named 'forage' or only variables named 'forage1', 'forage2', 'forage3' etc etc?

If there is no variable named 'forage' then I think this is where the problem is/was. In SF it is very important when dealing with compound variable names to always use % on both sides of your variables. It helps the parser precisely identify which part of a text string is a variable call, and which is not. Additionally, the bug that Woody and I were talking about has to do with some weirdness when you have two or more % signs in a row. In those cases, the SF script parser can get easily confused about what part of your string is intended to represent a variable value, and what part is plain text. Basically in those cases you can't call nested variables directly and have to use temp variables to get the parser to do what you intend.

When assembling the correct text for nested variable calls, I find it helpful to work from the inside out.

If I understand what you intend correctly, you have a series of variables forage1 forage2 forage3 etc. whose values you wish to call. So starting from the inside, you have %c%, the value of the counter. Adding 'forage' to that you get forage%c%. Then you want the value of the variable named forage%c%, so put % marks around the whole thing and you get %forage%c%%.

As I mentioned however this gets you into the parser bug that Woody and I referenced so you need to use a temp variable to work around it. And as if it weren't already confusing enough, the results will be different depending on whether you have 'forage' defined as a variable or not. The following script illustrates these bugs and the workarounds, and hopefully will be helpful for what you wanted to do with your script:

setvariable forage1 yelith

setvariable forage2 nemoih

echo

echo Case 1: 'forage' variable undefined:

deletevariable forage

counter set 1

setvariable temp %forage%c%%

echo item is %forage%c%%

echo item is %temp%

counter add 1

setvariable temp %forage%c%%

echo item is %forage%c%%

echo item is %temp%

echo

echo Case 2: 'forage' variable defined:

setvariable forage root

counter set 1

setvariable temp %forage%c%%

echo item is %forage%c%%

echo item is %temp%

counter add 1

setvariable temp %forage%c%%

echo item is %forage%c%%

echo item is %temp%

echo

echo Extra workaround for Case 2:

setvariable temp forage%c%

setvariable temp2 %%%temp%%%

# yes, %%%temp%%% is weird but that's what works

echo item is %temp2%

[Script test is running, Esc to cancel, Shift-Esc to pause]
setVariable: forage1=yelith
setVariable: forage2=nemoih

Case 1: 'forage' variable undefined:
DeleteVariable: forage sucessfully deleted.
setVariable: temp=%forage1%
item is %forage1%
item is yelith
setVariable: temp=%forage2%
item is %forage2%
item is nemoih

Case 2: 'forage' variable defined:
setVariable: forage=root
setVariable: temp=rootc%
item is rootc%
item is rootc%
setVariable: temp=rootc%
item is rootc%
item is rootc%

Extra workaround for Case 2:
setVariable: temp=forage2
setVariable: temp2=%forage2%
item is nemoih
[script done]

Correction Three...

Should really be

%%forage%c%%%

double the % signs, remember; as it will concatenate them down to one when setting, and then expand it when expanding %temp%

Basically as your output shows, its echoing as "foragec%" because of how that "bug"/"feature" (whatever) works.