Extending the event system

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

The built-in event editor is nice, but it can be better. I’ve put together several scripts that increase the flexibility of events and allow you to create more advanced events that previously may be impossible.

This post will list a couple scripts that I think will be useful. However, compatibility may not be guaranteed although I’ve tried to make them as flexible as possible.

Event Trigger Labels – Allows you to assign multiple action triggers to a single event page. Action triggers include different key presses as well as key item selection.

Parallel Pages – Allows you to set pages as “Parallel Pages”, which will be assigned to other event pages to be run concurrently. This is an extension of the page’s “move route” concept.

Common Event Arguments – Allows you to call common events and set extra arguments that the common event might use. You will need to use script calls, but this makes common events much more re-usable since now they can accept parameters.

End Phase Triggers – This is a simple add-on to the battle scene that forces the engine to do a final check after all enemies (or actors) have been defeated, whereas previously the battle end processing would occur immediately and ignore any last events that should be executed. Compatibility patches may need to be written for custom battle systems.

Page Note Conditions – This script adds additional page conditions in the form of ruby statements. It requires my Note Manager, but it allows you to assign page conditions independent of the event commands.

Extended Page Conditions – However, if you don’t want to use the Note Manager, this script allows you to reserve the first command of the page as an extra page condition.

Large Script Call – Interpreter sequential script calls as one large script call.

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

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