Shooting (3) about tankgame

[konkit]

Estimation (3)

[raddyr]

To handle shooting, we need to get 2D vectors (with start_point and collision_point).

[slakomy]

@raddyr Could you please explain more? I don't get the idea. Isn't it enough if front-end sends information about new shot to backend and backend sends information about positions and directions of missles as well as position of collisions that occured in current time step?

[raddyr]

Thats correct, frontend sends only information about shot (occurrence) and back-end will calculate trajectory from position and angles. The idea is that the backend will response the start point (simply: actual tank position - it is nice to have to maintain consistency) and end point where bullet disappears (due to collision or max bullet range). We assume that velocity of bullet is constant, so there are no need to send position of bullet every time step.

[tep-pl]

Ready to test with frontend.
Listening on 'shoot' channel for:
{ x: MISSILE_INITIAL_X, y: MISSILE_INITIAL_Y, angle: ANGLE_TOWARDS_X_AXIS }

Sending responses to 'missile shot' channel with:
{ ownerId: OWNER_ID, initialPosition: { x: MISSILE_INITIAL_X, y: MISSILE_INITIAL_Y }, target: TARGET_PLAYER | undefined }

EDIT (after some discussion):
Target would be always defined as point (dependend on max missile's scope in case of collision lack)