Skip to content

Releases: stringdotjar/flixelgdx

0.1.0-beta

05 Apr 00:52
331ea56

Choose a tag to compare

This is the first MAJOR test release of FlixelGDX!

This first release provides the following:

  • Extremely simple asset management
  • Input for keyboard and mouse (touchscreen and controllers are next)
  • Complete audio manager for playing sounds using gdx-miniaudio
  • Box2D integration for advanced users (although flixelgdx provides AABB physics by default)
  • complete FlixelBasic/FlixelObject/FlixelSprite pipeline with full support for animations with sparrow sprite sheets and atlases
  • Custom logger built from the ground up (logs by default look just like Haxe logs path/to/file.java:80: *log in italics here* . when enabled, logs are stored in a .log file. when it detects its in the ide, it puts the log folder in the root project, and in an executable .jar or native, it puts it in the working directory!)
  • Full FlixelGame class with an update/draw loop and a single sprite batch to trickle down the entire framework (all visual objects, like FlixelSprites, have a draw(Batch) method)
  • Fully working state/substate system, with allowing substates to be stacked on substates
  • Text object system via FlixelText with a global font registry
  • Group system that supports all types (and it also has a FlixelSpriteGroup as well, which allows sprite groups to be added in other sprite groups)
  • A complete tweening system with reflection, getter/setter via lambdas, color, shake, flicker, angle, num and all motion tweens. tweens can be made either with a registered builder class with its own pool, or directly with a FlixelTweenSettings object, which holds the tween goals (for reflection and getter/setter tweens), settings that affect all tweens such as duration, easer, etc. easers are also not like other tweening engines. with flixelgdx, easers arent enums, theyre deliberately lambdas with the format easer(float t) so that way people can use their own custom easer functions as well!
  • Interface backend systems for things like alerts (notifications showing info/warning/error to the user), reflection (desktop builds use ReflectASM, while everything else uses the default Java reflection handler with aggressive caching to ensure it doesnt lag), etc
  • Reflection system to match Haxe's Reflect class (in flixelgdx, reflection is accessed via Flixel.reflect.field(o, "field") or a method with the exact name
  • Every utility such as FlixelSave, FlixelBar, FlixelSignal, etc
  • and much more!