gyril / canon Goto Github PK

At the moment, you need a keyboard (ASDW space) to play.
The mobile experience requires some kind of joystick to be present, or a native interface.

We could do: left-right movements with left thumb, angle and power with right thumb.

To fix: attach timeouts to web workers instead of the window object

If we're to design a new HUD, a new map, new sprites for the characters, then we need to define first what is the flavor, style, ambiance of the game.
Is it retro? Futuristic? Both? Cartoonish? Steampunk?
Past & present sound boring to me. Mages could do, with a medieval fantastic style, although the ballistic part makes little sense (you "launch" a spell above the mountain?!).
Gunbound is cartoonish, not too serious, borderline absurd (the mobiles have eyes and mouths, just like small pets manned by their owners). I like it but we have to find something different.

The simulation runs twice as slowly in FF

It's fugly right now and doesn't give accurate information (who is our player, HP left, last shot's power & angle).

The viewport size should dictate the size of the camera.

We must use JS to detect the width and height of the player's window, then feed it to the viewport + camera.

The current system is unclear: players don't realize that they must hold space to shoot. Even if they to, they can't cancel the action so they have to shoot to full power / overshoot.

The game is very deterministic at the moment. Wind will bring randomness, skill and fun.

The HUD should overlay the game as little as possible. If anything happens in the left corner or y>=500, we can't see the action & players anymore.
Camera movements should fix that, but for the vertical part, the HUD should be on top of nothing, and the game should be above it.

We don't have the rights to the current music and should probably find something different anyway (less... heavy?)

Ever since implementing collision from http://higherorderfun.com/blog/2012/05/20/the-guide-to-implementing-2d-platformers/ the movements when climbing a slope have become noticeably not smooth.

With two instances of the client + 1 server my computer starts heating off badly.

Could come from various things, but I'm confident we could fix most of it considering the game is a small 2D simple-physics simulation.

Beyond world bounds, the bullets should disappear without exploding

Mobiles are ugly and don't really make sense right now.

Not sure what the cause is yet, but the effect is that the server and the client don't agree on an explosion, and hence disagree on the map and the collision.

The client keeps predicting movements according to how he sees the map, and the server keeps sending corrections for the clients' positions.

This problem never happened before we resized the viewport. Maybe the calculations are different now?

The current cannon is OK-ish, a bit boring though. We don't have a clear idea of what should come next.

To repro:
on branch planet
be red player
go to edge of planet, fall
from there, do a full power 0° shot

from then on, round 2*n will be skipped

Current map was a nice filler, but it's ugly and not optimized for the game mechanics.

Only two sounds implemented, one for shooting and one for explosion. They are both terrible. They should be replaced by something better.

at the moment, gravity goes down the screen, and movements on X axis are left-right movements only. for slopes and stuff like that, it's going to be a problem

Is it a hard soil then? How is that fun?
Is it the void, and the player dies? Can we make this mechanic fair? I think it's fun.

Currently the player camera sees the entire battlefield. It should

1. follow the current player more closely
2. loosely follow the bullet that is fired, even if it means unzooming
3. let the player take control of it somehow (arrows? drag and drop?)