Yes, but only in the case where _nearClip == _farClip.  What if _nearClip is > _farClip before the code enters this context?  That is: is it possible for a packet to provide malformed _nearClip and _farClip data?   It appears to be the case:  setNearClip() does no sanity checking.  We can punt this into the future, but if _nearClip is user-supplied data it really is only a matter of time until users experiment with sending bad values.  If it can cause a voxel server to assert, then it could be a useful way to grief your enemies.