FOV messed up if setted by client and server

If the client changes the FOV to anything other than the minimum and the server sets the walk speed (with Packet202Abilities, bukkit uses this for example) to anything higher than normal the FOV totally messes up, starting with the image being upside-down and ending with a totally weird tunnel view.

As a side note I think the FOV setted by Packet202Abilities is to high anyway: You feel way faster then you actually are.