Updates to Disabled Choice Conditions

I have good news and bad news.

I’ve updated the Disabled Choice Conditions plugin to improve efficiency, compatibility, and most importantly, more flexibility and ease-of-use when it comes to disabling choices.

Previously, if you wanted to use conditional branches to disable choices, you would have to start by adding a plugin command or a comment indicating which choice to disable, followed by the conditional branch. Take a look:


Which has a number of limitations:

  1. It only supports one conditional branch (so you can’t easily nest your conditions)
  2. If you wanted to disable more than once choice at a time with the same condition…sorry, make another conditional branch with the exact same condition
  3. What if you wanted to disable AND hide a choice? (yes, new plugin info leak)
  4. Those comments are OK, but not completely necessary
  5. When I switched to a plugin command, it made even less sense. Take a look:


Rather than doing all this, I’ve changed it so that the plugin command itself will disable a choice, and the conditional branches are up to you to figure out how to use it. This is just normal eventing, except you’re using a plugin command to disable a choice.

Take a look at the new and improved way of disabling a choice:

Now, when you say “disable_choice”, you are actually disabling a choice. Not, telling the engine that you want to disable a choice, and that conditional branch under it is the condition to use.

Unfortunately, if you have been using the conditional branch method, you will need to change where the plugin command is placed. But beyond that, that’s about the only change that needs to be made!

For those that are using script calls, nothing has changed: you can just use the script call as usual.

You may also like...

5 Responses

  1. Jachan says:

    Hi, I am using this plugin and… it works! Only except one thing – It won’t re-enable the choice when changing after see disabled choices.
    For example with checking actor’s stat requirements be great than or equal to… When false, it’s set to disable the choice to prevent player from choosing that. But after that, when player then met ALL actor’s stat requirements which I coded to AVOID the “disable choice” script, the choices in end are STILL disabled regardless. Looked around and tried “enable_choice ChoiceNumber” which does not work either. What or where did it go wrong?
    Please let me know, thanks!

    • Jachan says:

      Correction – I just found out it’s about param[2] being issue, not yours. My apologies. I sucks at lunatic writing, =(

  2. Lisette Scheffer says:

    I feel like crying. I can’t get it to work the way I want to. I have text with 4 choices. I want the choice text to be disabled and not ever re-clickable after I’ve clicked it once.
    But once I click choice text 2 I want that to be disabled to while choice text STAYS disabled. I’ve tried making a variable (DIALOGUE) and setting it to +1 (with an if greater than o = disable command) but that doesn’t seem to work either. Can someone show me how to disable things consecutively?

    I want this kind of dialog thing to be regular in my game, so I don’t want to spend a variable on each choice option if its possible…

Leave a Reply

Your email address will not be published. Required fields are marked *