Shooting by mouse de-synchronization

[xPaw]

If you shoot using mouse keys, it will make both players shoot in multiplayer, and by doing that it will cause de-synchronization in player origins.

[zorro300]

So no more mouse-shooting in MP ? Or is it fixable

[xPaw]

Should be fixable, i didn't look. I need to setup egit for eclipse properly, then i will be able to fix moar bugs!

[zorro300]

I have that setup but my fork queue keeps bugging through , whenever I want to apply the new forks , they all turn red

[framp]

I'm trying to fix it, I don't think I'm too far

What I've done (schematically) until now:
In network/packet:

• define a ChangeMouseCommand in network/packet/ChangeMouseCommand.java which copies the mouseButtons data
  In MojamComponent
• use a synchedMouseButtons array instead of mouseButtons
• synchronizer.addCommand(new ChangeMouseCommand(mouseButtons));
• edit handle(int playerId, NetworkCommand packet) to save the mouseButtons in the right synchedMouseButtons

The mouse data is sent succesfully and I'm able to print it succesfully. The only thing which isn't working is the remote player aiming right now (probably due to offset problems I believe)
If you have suggestions: https://github.com/framp/Catacomb-Snatch-1/commit/2f2f5459d4808504330358960462d4aa3a33c10e

[Borsty]

Commented.

[framp]

Added a pull request
#219
The players now have the right mouse events mapped correctly, but there is still something in the mouse implementation which make the multiplayer game go out of sync.

[richie3366]

Probably because the new facing direction is not transmitted to the other player ?

[framp]

Well the Player.setAimByMouse should calculate the new facing using the sent mouse data.
I tried sending the new facing direction together with the mouse values (I even tried sending aimVector) but the problems persisted.

[framp]

Woah! Looks like Flet definitely fixed it:
4485792

[zorro300]

Theres already a new bug with the latest update about the mouse ---> #239

[richie3366]

I think you should try to edit the setPosition method by doing the same system for the states (eg. currentX, currentY, nextX, nextY), it should probably work better ;)
Edit : And by the same, change the tick() method

[Flet]

@richie3366 yep, would be more prudent. Go ahead and fork/push if you want to give it a go :)

[Flet]

closing issue, but @richie3366 has a good point