Pre-Skill Effects

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

By default, effects assigned to skills or items are executed after skill or item is executed.

This script allows you to specify that certain effects should be executed before the skill or item is executed.

Download

Script: download here

Installation

In the script editor, place this script below Materials and above Main

Usage

Note-tag skills or items with

<pre-skill effect: ID>

Where the ID is the effect the ID of the effect.

effectIDAssignment1

You can figure out what the ID of the effect is by counting their position in the list from top to bottom. The effect at the top has ID 1, the one under it has ID 2, and so on.

Examples

To have effect 2 run before the skill is executed, note-tag it with

<pre skill effect: 2>

Notes

By default, the engine does not support multiple common events in a single skill. You can use the Common Event Queue script or any other script that allows you to run multiple common events to overcome this limitation.

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...

14 Responses

  1. Alex says:

    Can someone help me with this?

    I have downloaded this script and then installed in the plugin center of rpg maker mv.

    I am using the command

    <

    pre skill effect: 2> in the skill notetag, but it doesn’t work.

    I am using all the plugins from YEP.

    Any ideas?

  2. Ray says:

    I cant seem to download it… help?

  3. LazzXion says:

    I was wondering if it’s possible to set this up so you can get different cut-in images on the same skill depending on the actor?

  4. Alter says:

    Hey Hime. First of all, thanks for making this script! There’s a lot of really neat things that can be done with it. However, after playtesting my game, I noticed that battle events that used the Force Action command were not working anymore (If a Force Action was called, it would simply freeze the game). I tried checking my scripts and it seems that if I put this script above Yanfly’s Ace Battle Engine script, then Force Actions would work again, but the Pre-Skill Effects script would stop working (The common event doesn’t get called). This probably falls under the category of a compatibility issue and I know you said that you wouldn’t do any compatibility patches, but it would help me a lot if you could help clarify the issue for me and I can try to work around it. Thanks!

    • Hime says:

      I will need to look at the issue, but have you tried adding yanfly’s core engine?

      • Alter says:

        Yes, I am already using Yanfly’s Ace Core Engine script. The problem seems to persist with and without the core engine script.

    • Patrick says:

      Hello, I have the same problem, it would be a pity if not have solution.

      • Patrick says:

        Ok, I found a solution: Replace “Force Action” command for this script call:
        battler = $game_party.members[a]

        battler.force_action(b, c)

        a = ID of the party member who performs the action.
        b = ID of the skill.
        c = Select the target: -2 for the last target; -1 for random target and 0 or more for each enemy of the troop.

        This works for me 🙂

  5. TenWren says:

    Hello! Under the heading “Usage,” you have the example written as ”

    <

    pre-skill effect: ID>.” This script doesn’t work if you include that hyphen, so you may want to remove it. Thank you for this script, and take care!

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