Unrandomize enemy shooting #13
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… used to determine which row/column enemy will shoot. Currently there are difficulties with computer ticks still creating random results that are fairly similar to each other.
|
|
# Conflicts: # spaceinvaders.py
|
I added in a flag (-u) which will turn on the un-randomized enemy shooting. If the flag is not specified in the args then the default is off (enemy shots will be random). |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unrandomized enemy shooting by using an array of random numbers that are seeded the same each time (in function reset), and the row/column of the enemy shooting is determined by this random array (in function make_enemies_shoot).
Unrelated, but I auto-formatted the file to convert all tabs to spaces to get rid of some annoying issues with my interpreter. Hopefully this shouldn't affect anyone, and should be able to be safely merged in.
resolves #12