• Stars
    star
    246
  • Rank 164,726 (Top 4 %)
  • Language ActionScript
  • License
    Other
  • Created over 13 years ago
  • Updated about 11 years ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

The Flixel Power Tools are a set of plug-ins for Flixel 2.5+ to assist with your game development

Flixel Power Tools

Version 1.9 (final release)

November 28th 2013

By Richard Davey, Photon Storm

The Flixel Power Tools are a package of classes designed to provide extra functionality to your Flixel 2.5+ games.

Quick Install Guide

Copy the src and lib folders into your ActionScript project. All the classes for Flixel Power Tools should be contained in

src/org/flixel/plugin/photonstorm

Now read the "Getting Started Guide" in the Docs folder; it contains important information that will help you compile!

Getting Started Guide

There is a comprehensive Getting Started Guide in both Word and PDF format in the Docs branch:

https://github.com/FlixelCommunity/Flixel-Power-Tools/tree/docs

Documentation is also provided built-in to the classes. AS3 IDEs such as FlashDevelop will provide context-sensitive help for all classes and functions in the Flixel Power Tools.

Finally check out the home page at http://www.photonstorm.com/flixel-power-tools for updates.

Test Suite

Get the full Test Suite from here:

https://github.com/FlixelCommunity/Flixel-Power-Tools/tree/test-suite

The Flixel Power Tools come with a comprehensive Test Suite. Use it to visually see the tools in action, and then learn from the source code and comments within.

To run the Test Suite launch the following SWF:

Test Suite/bin/FlixelPowerTools.swf

If you don't have Flash Player installed locally then open index.html in a browser.

Classes

The following classes are currently in the Flixel Power Tools:

  • FlxBar
  • FlxBitmapFont
  • FlxButtonPlus
  • FlxCollision
  • FlxColor
  • FlxControl (includes FlxControlHandler)
  • FlxCoreUtils
  • FlxDelay
  • FlxDisplay
  • FlxExtendedSprite
  • FlxFlod (includes FlxFlectrum)
  • FlxGradient
  • FlxGridOverlay
  • FlxLinkedGroup
  • FlxMath
  • FlxMouseControl
  • FlxScreenGrab
  • FlxScrollingText
  • FlxScrollZone
  • FlxSpecialFX
  • FlxVelocity
  • FlxWeapon

APIs Include

  • FlxKongregate

Special FX Includes

  • BlurFX
  • CenterSlideFX
  • FloodFillFX
  • GlitchFX
  • PlasmaFX
  • RainbowLineFX
  • RevealFX
  • SineWaveFX
  • StarfieldFX

Contributing

I'm afraid that the Flixel Power Tools are no longer maintained by myself. I have moved on to other things.

I would strongly suggest you start using the Flixel Commmunity version of Flixel which contains updated versions of these tools.

License

Copyright 2011 Richard Davey. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY RICHARD DAVEY ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RICHARD DAVEY OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the FreeBSD Project.