Targeting with intercepts

[Casamir]

I was wondering how I might code a target into an intercept prog. Similarly if I wanted to do something like an embroider-able handkerchief. Or if I wanted to have a magic kazoo shoot a sound burst at X for example, with the trigger word of 'humm', how do I get that to target X? Is there a place holder like with % in aliases?

Code: Select all

>intercept_prog embroider %~
mposet $o short a handkerchief embroidered with '%'
~
>intercept_prog humm~
if string(1) == X
  mpcast soundburst X
endif
~
|

[Harroghty]

You need to check for the correct subsequent phrase. e.g.

Code: Select all

>intercept_prog embroider~
if actorhasobjnum(i12345)
  if stringprefix($1) == handkerchief
    embroiders....
  else
    mpunintercept
  endif
else
  mpunintercept
endif
~

The embroidery itself could be done a couple of ways: you could create certain parameters that must be applied (think about some of the custom merchants) or you could give total free reign (think the dummies). I can look at your product and give you some suggestions based upon your desired goal.

[Levine]

I've been trying to figure out how I can have a customisable variable. I don't have a specific goal right now (I found a workaround), but theoretically, I'd like to know how, say, the handkerchiefs or wooden signs were achieved so I can streamline my scripts and have the option brewing in my mind for other uses.

I wrote something up below (the blank after == is intentional), and I want that to be whatever variable that the user inputs. So, I'm hoping this following script:

Code: Select all

>intercept_prog customise~
if stringprefix($1) ==
  mposet $o short a $1 birthday card
  mpechoat $N You customise a birthday card.
else
  mpunintercept
endif
~

Would produce this effect:

Code: Select all

> customise pink
You customise a birthday card.
You are carrying:
     a pink birthday card (perfect)

Would that work?

[Harroghty]

Yes, it's possible but I typically don't encourage it. Otherwise one finds:

A butt birthday card lies here.

For posterity though, one uses $0, not $1. e.g.

Code: Select all

>intercept_prog customize~
mposet on $n $o short a $0 birthday card
mpechoat $n You customize a birthday card (and it better be an acceptable, IC choice).
~

There are tons of things out there that give a player a range of choices. Pick (once) any color from these colors, then you just maybe have a prog like...

Code: Select all

>intercept_prog color~
if stringprefix($1) == pink
or stringprefix($1) == red
  if stringprefix($1) == pink
    mposet on $n $o etc... etc..
  else
    if stringprefix($1) == red
      mposet on $n $o etc... etc... etc..
    endif
  endif
else
  mpechoat $n That is not an acceptable color.
endif
~

[Levine]

In the first example, does this mean that instead of having an empty value after "==", I can just use $0 right away without an if string/stringprefix?

And, does that mean that if string/stringprefix isn't used, the intercept (in this case, "customize") would not be treated as $0?

[Harroghty]

$0 will be everything after customize: no if check is needed.