Author Topic: CMD_DURING  (Read 6600 times)

TheThingIs

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 278
    • HCS Voicepacks
CMD_DURING
« on: May 09, 2016, 05:29:44 PM »
You gave us CMD_BEFORE and CMD_AFTER

I could really do with a CMD_DURING

This way, when a command is called I can use one command and use the random reference to tell me what I should do.
The Singularity profile - One profile to rule them all and at HCS we bound them ;)

You see, TheThingIs, eventually you'll be allright.

Pfeil

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4826
  • RTFM
Re: CMD_DURING
« Reply #1 on: May 09, 2016, 06:23:46 PM »
So, you're looking to get only the command name, without wildcards?

I.E. when the command is "Test*" and you speak "Test One", {CMD_DURING} would return "Test"?


EDIT: I was going to suggest working around this by using:
Code: [Select]
{TXTREPLACE:{CMD}:{CMD_AFTER}:}However, this returns "Not set".
« Last Edit: May 09, 2016, 06:36:41 PM by Pfeil »

TheThingIs

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 278
    • HCS Voicepacks
Re: CMD_DURING
« Reply #2 on: May 10, 2016, 09:17:54 AM »
It's the wildcard part I am after.

command: Astra to [flight;comms;tactical] please

CMD_BEFORE gives me "astra"
CMD_AFTER gives me "please"

so I wanted the wildcard bits in the middle as they are the ones that can change. Or even all the wildcards, maybe seperated by a space, if you are using multiple in a command.

the TXTREPLACE is a good option but VA crashes when you use a variable for the replace parts...although this could just be a bug.
The Singularity profile - One profile to rule them all and at HCS we bound them ;)

You see, TheThingIs, eventually you'll be allright.

Gary

  • Administrator
  • Hero Member
  • *****
  • Posts: 2840
Re: CMD_DURING
« Reply #3 on: May 14, 2016, 09:49:40 AM »
There is a new {TXTREPLACEVAR:textVarSoure:textVarSearch:textVarReplace} that will be in the next release to be used in the place of {TXTREPLACE}.