Complete #2 first, then both of you browse to the game URL and duel it out.

It should duel out. If something doesn't work, fix it, until you can really duel and win/lose.

I should be able to detect collisions between two arbitrarily-rotated sprites (player and projectile).

Using the Rectangle class seems to be the way to go.

http://abrarsyed.github.io/octowar should have an index.html and reference the latest JAR.

We just need a gh-pages branch with an uploaded index file and JAR file for this; it's quite possible to run libGDX games as applets.

All of the amazing functionality (eg. auto-scale to screen preserving aspect ratio) should be integrated into this project. This will be THE definitive source.

But, it's not necessary for the MVP.

Missing Features

From Java

• Game sends update time to systems.
• Systems should be an interface (init construction with entities, update method with delta time)
• Chunking big elapsed times into smaller pieces like 10ms max
• Dynamic resizing to fit the display space
• Fade in/out methods and onComplete event handlers
• Audio component with play method
  • A way to chain-play some audio components in serial
  • A method to (automatically?) preload all audio files from a dir
• Flurry analytics wrapper/helper
• Physics component with velocity and acceleration
• Better sprites
  • Sprite sheet component
    • Set the frame/cell currently
    • Play an animation (loops)
  • Sprite components have alphaRate and rotationRate
  • Sprite components can be rotated around their center
  • Uniform scaling of sprites (disable texture filtering, and getting their original size)
• Text component
  • Colour-changable
  • Outline by drawing 4x
  • Dynamic font generation
• EntityFactory to create a touch button given two sprites
• Ditto, but toggle button
• The whole io package (includes file reading and persistent storage)
• Singleton logger

From C Sharp

• Spatial manager (quad tree)
• Collision detection events (when two specified objects overlap, invoke method)
• Lighting with masks
• Camera

Create an entity-component system. For now, leave it in a separate package, not the OctoWar one. It should have:

• Base classes (Entity with a bunch of Components)
• Screen or Scene class (same thing)
• SpriteComponent for sprites, with a SpriteManager to draw them

In terms of data-oriented architecture, make sure the managers keep a simple list of sprite components.

• When you add an entity, you should extract the sprite into the flat list.
• When you remove an entity, you should remove the sprite from the list.

This is the minimum we need.

• Sprites and sprite system
• Scene changer and titlescreen
• Input component: WASD + space
• PoC: move around, space to attack

Note: Game class will eventually be used for Android/etc., and will have "Content size" vs. "physical display size" properties. So subclass libGDX classes.