aboutsummaryrefslogtreecommitdiff
path: root/bin/rand.rb
Commit message (Collapse)AuthorAgeFilesLines
* Make randomness a bit more randomMiquel Sabaté Solà2026-03-051-1/+4
| | | | Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>
* Update values on the RNG tableMiquel Sabaté Solà2026-02-131-3/+4
| | | | | | | This way enemies are a bit more off from the boundaries, avoiding visually distracting scenarios. Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>
* bin: improve the style and add more documentationMiquel Sabaté Solà2026-02-111-1/+11
| | | | | | And also run rubocop on the CI for good measure. Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>
* Simplify the random_valid_y_coordinate functionMiquel Sabaté Solà2026-02-101-0/+18
This function relies on a pre-computed table to get the "random" numbers from, but most of the times this is used, it needs to be between some safe boundaries. Before this commit, this was done inside of the function, correcting the fetched value to be above or below these limits. But there was a bug on the below the grounds limit, in which the 'sbc' instruction could subtract too much from the fetched value and make enemies appear below the sky. Now, this is easy to correct, but since we are cheating with a pre-computed table, I thought it would be vastly easier to just get a random table with the "proper" values. That is, random but within the required boundaries already. Plus, it makes the 'random_valid_y_coordinate' function much faster. This commit adds a ruby script in bin/ which produces a pseudo-random table when called, making sure all the requirements are met. We have to make sure to call this script if we ever change the boundaries at some point. Signed-off-by: Miquel Sabaté Solà <mssola@mssola.com>