Difference between revisions of "User:Chase-san/Roboflight"

From Robowiki
Jump to navigation Jump to search
Line 9: Line 9:
 
In case you want to take a peek at what I have been up to here is the [http://www.mediafire.com/?dscc2aktas6wp6f latest demo].
 
In case you want to take a peek at what I have been up to here is the [http://www.mediafire.com/?dscc2aktas6wp6f latest demo].
  
=== TODO ===
+
== TODO ==
 
:'''MILESTONE 1'''
 
:'''MILESTONE 1'''
 
#Create a simple battle starter
 
#Create a simple battle starter
Line 27: Line 27:
 
:'''MILESTONE 2'''
 
:'''MILESTONE 2'''
 
#Individual robot coloring for robot, missile and bullets (perhaps thrust as well).
 
#Individual robot coloring for robot, missile and bullets (perhaps thrust as well).
 +
#Battle Scoring
 
#...
 
#...
  

Revision as of 21:04, 14 February 2013

Roboflight is a programming game planned as a spiritual successor to robocode. The name might change once it gets further along.

From Demo 20130214

http://i.minus.com/iyS8vO2B5D1BR.gif

This is the second draft of roboflight. Everything is up in the air at this point.

In case you want to take a peek at what I have been up to here is the latest demo.

TODO

MILESTONE 1
  1. Create a simple battle starter
    • Loading of robots from classes
    • Loading of robots from jars
  2. Add support for multiple robots of the same type to not share static data
    • I have a vague idea how to do this. May be related to #1
  3. Get missiles working again
  4. All those misc events... (on death, on other death, on hit by, on hit with, ...)
  5. Retweak UI to display energy in a nicer way.
    • Add UI support for more then two combatants while I am at it
  6. Add robot debug print support to UI
  7. Move current debug options into a menu/dialog.
  8. Add the ability to save options.
  9. Add pause/stop/restart options
  10. Add FPS slider
MILESTONE 2
  1. Individual robot coloring for robot, missile and bullets (perhaps thrust as well).
  2. Battle Scoring
  3. ...

Note, I will fix bugs where I find them.

Would be nice

  • Eventually move rendering to a scene graph solution
  • Find something to replace slick-ttf.jar
  • Clean up some of my messier code
    • As I add options, this should happen automatically in some places.