Rewrite the client-side chunk-management.
The chunk-management in jme-client is currently beyond abysmal, it must be rewritten to be halfway sane.
It should...
- ...take the camera location, angle and FOV into account.
- ...take a viewing distance into account.
- ...load and mesh chunks in two threads (with neither being the jME thread), ideally supporting multiple loading/meshing threads.
- ...prioritize chunks which are currently being looked at.
- ...minimize the creation of new objects, ideally it should never create new ones with the exception of the chunks itself.