rework input

[c8p2d01]

the given json file provides each tick

• which objects had value changes
• and what actions were executed
  when reading in the replay as of yet we only concider the objects and display their momentary position
  in order to use the information given in the actions we could either double part of the current code here in the visualizer
  OR before reading in the json we rework it a bit so that the object section also includes the changes brought by the actions

side Benefits:
tldr: move/attack might not have to be split in the gameserver

in the current version when a Unit moves it also attacks. in order to properly animate attacks we decided to change the gameserver to accomodate a differenciation of those actions in the replay file
if one inspects the current replay files one can see that the move/attack action can be found even when the unit is not mentioned in the object part
this may be interpreted as an attack because the unit does not move. this can be linked to the differenciation between the moves and as such might make the proposed chages to the gameserver obsolete

[FreddyMSchubert]

The gameserver changes are not for the visualizer, attack rework will happen either way.
However, since you will still be able to move & attack by moving into an attackable object, killing it & then standing where it stood, all 3 animations still meed to exist (move, attack, move & attack).
The logic here is that the game in my mind works somewhat like chess, except not all units immediately die, but bounce back to their original positions if the target they attacked is still alive.
It's still my primary wish to the Visualizer team to make the moves chess-figure-like, doing a big jump. This way, youd literally only need one jumping animation, with the sword out and pointing to the target if theres a unit on the target pos.
That would make the game behavior more intuitive I think.