#The question is how to do this {@test%number%loop}

1 messages · Page 1 of 1 (latest)

candid pendant
#

the answer is "what"

still lynx
#

Pretty sure you can’t

#

Atleast I don’t think

fervent ridge
mortal topaz
candid pendant
#

we need more context

still lynx
#

Code and error would be usefull if there is one

mortal topaz
#

bro

#

{@test} is an option

fervent ridge
mortal topaz
#
options:
  test: sus

command sus:
  trigger:
    message "{@test}"
candid pendant
mortal topaz
#

if you increase the verbosity of skript, script literally sees this code as message "sus"

#

it's never changed after the script is loaded

#

and it'd require a complete rewrite of options to change

#

(probably)

candid pendant
fervent ridge
mortal topaz
#

and u define questlore before quest1givemoney?

fervent ridge
mortal topaz
#

then...

#

use variables instead of options??

candid pendant
#

why are i and o not local

still lynx
candid pendant
#

then just make a list of them

mortal topaz
#

options are just set to their value when the script is loaded

#

not when the code is run

candid pendant
#

{test::1} = a, {test::2} = b

#

etc

mortal topaz
#

huge difference

fervent ridge
mortal topaz
#

solution: replace 'options:' with 'variables:' and remove the @

#

and maybe use a logical order

candid pendant
#

(theyve marked this as solved)

mortal topaz