Further optimisations for WorldPositionGenerator - For each potential set of input values passed into the WorldPositionGenerator, each keeps its own array of potential areas in the map. Discard any element which will never pass for that set of input values, saving on computation on all future runs with those input values - Testing the most problematic WorldPositionGenerator (ocean) on a 4.5k map shows that 98% of the potential candidates can be discarded - Need to iron out an issue with the list of candidates always getting smaller when artificially checking every single candidate in each attempt