smackem/jobotwar

A RobotWar clone using JavaFX, REST and Blazor WebAssembly

jobotwar's Issues

Ideas for v2

v2 may be a multiplayer game:

• Robots are run on graphic clients, where they may be controlled by programs or interactively by users
• They exchange state-changing actions to the remote server (aim, shot, radar, speed, random)
• Go for a RTS-like design (since game is completely deterministic)
  https://www.gafferongames.com/
  https://www.gamasutra.com/view/feature/3094/1500_archers_on_a_288_network_.php

Use JTS for geometrical calculations

https://github.com/locationtech/jts

Write simulation log

Log events like "robot X got killed" and robot's log messages.
Also record random numbers to enable #11.

Support logging from language v2

use OUT register for statement
@log(@speedX())

Add more icons

Display robot log messages in robot's color

messages logged through the OUT register should be displayed in the emitting robot's color

"New Game" button when game is complete

Log messages below game board

Example:
Robot X was destroyed by Robot Y
Robot X was destroyed

Validate arguments for built-in functions

sqrt(100, 100) works :$ - fix it

Better color distribution of random color for new robots

new color should have a certain minimum distance from all other robot colors

Winning animation: Particle Explosion

Show a nice animation when a game is over

Nicer robot explosion

use smaller ParticleExplosion with hues 0 to 30 (or robot hue) for robot explosions

Add hypot and atan2 functions

get distance from current position to destination:
hypot(@x() - destX, @y() - destY)
this is a less verbose alternative to sqrt(dx * dx + dy * dy)
get angle to destination:
atan2(@x() - destX, @y() - destY)
this is a less verbose alternative to atan(dy / dx); // add 180 if dy < 0

Progress bar for simulation mode

when running a simulation, show a progress bar in the "running"-overlay

Remember robots when starting a new game

Replace embedded robots with persisted jobot files

Mix V1 and V2 robots

• mover (v1)
• shooter (v1)
• corner (v2)
• patrol2 (v2)
• batteringram (v2)
• bumblebee (v2)

Turn RobotStatisticsWidget and RobotGauge into custom controls

More math functions

add sign, min and max

Extend robot persistence for language v2

Extend JSON format with meta information like version and source code language.

Ensure that robot names are unique

In the EditController, make sure that robot names are unique. This is a must for the GameRecorder, which should assert on the condition.

Load/Save Robot

Limit number of robots

something like 64 should be ok

V2 language optimizations

• initialize variables with rhs expression if rhs is literal (LD_F64 123 for def x = 123)
• only emit RET in state if last stmt was not RET

New Language (Syntax2)

State-based language:

def aim

state main() {
    yield scan(@damage(), 0)
}

state scan(damage, radarAngle) {
    distance := @radar(radarAngle)
    if distance < 0 {
        @fire(radarAngle, abs(distance))
    }
    radarAngle = radarAngle + 7
    if @damage() != damage {
        yield newDest
    }
}

state newDest() {
    destX = @random(10, 100)
    destY = @random(10, 200)
    @speedX(destX - @x)
    @speedY(destY - @y)
    yield move(destX, destY)
}

state move(destX, destY) {
    arrivedX := false
    arrivedY := false
    if abs(destX - @x) < 30 {
        @speedX(0)
        arrivedX = true
    }
    if abs(destY - @y) < 30 {
        @speedY(0)
        arrivedY = true
    }
    if arrivedX and arrivedY {
        yield main
    }
}

function xFromAngle(angle, length) -> @x() + cos(angle) * length
function yFromAngle(angle, length) {
    return @y() + sin(angle) * length
}

Play/Pause/End Game

UI support for language v2

• CodeEditorV2
• tab for language version in EditView

Save As... shows an OpenDialog instead of a SaveDialog

Fix FileChooser usage

Detect Draw Outcome

When all robots have been killed in one tick, mark the match as draw.

Empty source code in V2 program leads to invisible compiler error

New V2 programs should contain

state main() {
    // your code here
}

also, the error should be reported

Draw initial board in simulation view

Graceful handling of robot errors

Catch exception when ticking a robot, write message to log window, stop program.

Replay a simulated game

Robot icons

select icon from list for robot on creation (editcontroller). display icon in robot circle.

Add shooter and corner robots to standard selection

gosub/endsub keywords

Simulation Mode

add simulation mode:
as soon as the board is ready:
instead of just starting the game with the ticker, simulation calculates the outcome as quickly as possible, not restrained to ticks. if no winner can be determined, simulation ends after a few million cycles.

Add test for v2 recursion

Make damage from explosion depend on distance

Split into multi-module project

one module jobotwar-model and one module jobotwar-gui

Add documentation

• link to original robotwars
• new animated gif in better quality
• language documentation for v1 and v2