Remove State on Action

Help spread the word!Share on FacebookShare on TumblrTweet about this on TwitterShare on Google+Share on LinkedInShare on RedditFlattr the author

Do you have a buff state that will allow you to unleash a guaranteed critical strike, but only for the next action that you take?

Or perhaps a state that will increase the effect of all healing spells, but only after a healing spell has been used, the state wears off?

This plugin allows you to assign a new “auto removal” condition to your states: Remove State On Action.

You can choose how many actions it takes for a state to disappear, and also whether only certain actions will affect the state.

You can combine this removal condition with other auto-remove conditions such as checking for a certain number of turns, or taking damage, and so on.

Download

Plugin: download here (right-click and save-as)

Related Plugins

Installation

Download the plugin and place it in the “plugins” folder in your project’s “js” folder. Then open your Plugin Manager (F10), double-click an empty row, and select the HIME_RemoveStateOnAction plugin.

Once it is in your list of plugins, turn the plugin on.

Usage

removeStateOnAction2

To create states that will automatically remove themselves after a certain number of actions have been used, note-tag the state with

<remove by action count: minCount maxCount>

Where the minCount and maxCount represent a range of action counts before the state is automatically removed. For example, you can say

<remove by action count: 1 1>

If it should only last for one action. If you write

<remove by action count: 1 3>

Then it can randomly last anywhere between 1 and 3 actions.

Check for Certain Skills

removeStateOnAction3

By default, every action that you perform will update the countdown. For example, if your state should last 2 actions, and you perform two actions in one turn, then the state will expire.

What if the state should only consider certain skills to update it? You can use the following note tag:

<update action count skill: SKILL_ID>

Where the SKILL_ID is the ID of the skill that will affect this state. For example, if Attack is skill 1 and Guard is skill 2, and you wanted your state to only be removed when you actually attack, you can write

<update action count skill: 1>

This way, if you just keep guarding, the action countdown won’t be updated. You can add as many tags as you want if you want multiple skills to count towards it.

Help spread the word!Share on FacebookShare on TumblrTweet about this on TwitterShare on Google+Share on LinkedInShare on RedditFlattr the author

You may also like...

1 Response

  1. SirCumferance says:

    When I get home, i am gonna experiment with Sealing all skills not related to the Charge, so that that ‘Charging’ a spell requires that you cast, not attack. I likes it man, I really do

Leave a Reply

Your email address will not be published.

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax