While the effects of the "Do not allow key to be passed through" option cannot be changed dynamically, as mentioned before, you can partially work around that by having VoiceAttack send the keypress for you instead, as part of the command, which I'll assume is what you've already done at this point.
Those methods don't require anything special in your inline function, not even the default includes. You do need to specify the classes that method can be found in, so the compiler can look for them.
E.G.
public class VAInline
{
public void main()
{
VA.Command.SetSessionEnabled("my command", false);
}
}
to disable "my command" (this also disables any other command phrases linked to the command, it's just used at the identifier to find the command you're referencing)
public class VAInline
{
public void main()
{
VA.Command.SetSessionEnabled("my command", true);
}
}
to enable "my command" again
If you want to check whether a command is disabled, that can be done using something like
public class VAInline
{
public void main()
{
VA.SetBoolean("my Boolean variable name", VA.Command.GetSessionEnabled("my command"));
}
}
which should set the Boolean variable "my Boolean variable name", to "true" if the command is enabled (the default state), or "false" is disabled
Do note that all of this is advanced functionality. If you intend to use inline functions, you'll want to learn at least the basics of C#/.NET, and keep in mind that there are much fewer protections (E.G. you can easily set up an infinite loop that uses up all the CPU time it can)