Hello,

I’m just starting to learn ChatScript, and I haven’t found a solution to a problem I’m having trying to use ^argument(n) from within an outputmacro to loop through all its arguments.

^argument($_argIndex) will return matching variables _0 to _3 for $_argIndex = 1 to 4.

However, I couldn’t find a way to read the value of _0 rather than the matching variable name. I have tried ^$_argValue to no avail.

Enabling :trace all gives me:

How should I proceed if I want to use the value of an argument within the outputmacro itself?

Apologies in advance if this is answered in the docs, I did do my research and came out empty.
Thank you

EDIT: I should note that when accessing _0 directly (in a comparison for instance, or logging something like ^“value is: _0”) I get the value of that argument just fine.

I figured out a workaround for now. I just parse an active json string containing all arguments into an array so I can iterate through it the same way I would iterate through them with ^argument. Not very elegant though as I have to edit the json string to match the arguments

I’m assuming I’d need to wrap the variable in two layers of active strings so $_argValue can become ^“_0” on the first evaluation then the actual value on the 2nd evaluation. I don’t know how though.

I did manage to get the right value printed out, but it’s because it was going through a custom log method which would use the argument passed to it within an active string, doing exactly what I describe above. ^logvalue(^”$_argValue”) would work because in ^logvalue it’d do something like ^log( OUTPUT_ECHO, ^”^arg”)

If anyone has a code snippet of a successful usage of ^argument(n) I’d love to see that.
Thanks

EDIT: Another workaround is to run the variable through an outputmacro that returns the active string containing the argument passed to it:

The following code worked for me:

outputmacro: ^test( $_t1 $_t2 $_t3)
^argument($_t3)
^argument($_t2)
^argument($_t1)

topic: ~INTRODUCTIONS keep repeat (~emogoodbye ~emohello ~emohowzit name here )

t: Greetings
u: (test) ^test(1 2 3 )

I went back to the basics like your example and realized my problem comes from the fact that I call that macro with the matching variables from a pattern as arguments

CASE 1:

^argument(1) returns ‘_0’ and I have to play tricks with active strings to get the value out of it (as described in previous posts)

CASE 2:

^argument(1) returns 1

CASE 3:

^argument(1) returns 1

I guess I’m still a bit confused about how variable references vs. values work in ChatScript, I guess _0 doesn’t automatically print out its value because it’s in a macro call, not directly in the output.

Thanks for your help!

Its a CS bug. will fix for next release.