Change Details

mapGridPosition will return wrong coordinates for SOME NOT ALL positional data input with floored edge case values, e.g. mapGridPosition [8500,4700] will erroneously return "084046", whereas mapGridPosition [8600,5000] will correctly return "086050".

mapGridPosition will return wrong coordinates for SOME NOT ALL positional data input with floored edge case values, e.g. mapGridPosition [8500,4700] will erroneously return "084046", whereas mapGridPosition [8600,5000] will correctly return "086050". EDIT2: Severity could arguably be 'Major' if returned values from script-generated sources are used in hashmap key generation/retrieval (and go unnoticed). I noticed this as I was writing an algorithm that should not have produced duplicates in a tree, but did, but only after using mapGridPosition. I've remedied that so far by just _pos vectorAdd [50, 50] before converting to grid coordinates. str _pos also works as a surprisingly reliable key, at least when using floored multiples of 100 in position coordinates.

mapGridPosition will return wrong coordinates for SOME NOT ALL positional data input with floored edge case values, e.g. mapGridPosition [8500,4700] will erroneously return "084046", whereas mapGridPosition [8600,5000] will correctly return "086050". EDIT2: Severity could arguably be 'Major' if returned values from script-generated sources are used in hashmap key generation/retrieval (and go unnoticed). I noticed this as I was writing an algorithm that should not have produced duplicates in a tree, but did, but only after using mapGridPosition. I've remedied that so far by just _pos vectorAdd [50, 50] before converting to grid coordinates. str _pos also works as a surprisingly reliable key, at least when using floored multiples of 100 in position coordinates.