This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 234
add more mob when score increase #19
Open
yosiasm
wants to merge
1
commit into
tasdikrahman:master
Choose a base branch
from
yosiasm:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -494,7 +494,7 @@ def update(self): | |
## now as we delete the mob element when we hit one with a bullet, we need to respawn them again | ||
## as there will be no mob_elements left out | ||
for hit in hits: | ||
score += 50 - hit.radius ## give different scores for hitting big and small metoers | ||
score += 50 - hit.radius -int(score/3000 ) ## give different scores for hitting big and small metoers | ||
random.choice(expl_sounds).play() | ||
# m = Mob() | ||
# all_sprites.add(m) | ||
|
@@ -505,7 +505,8 @@ def update(self): | |
pow = Pow(hit.rect.center) | ||
all_sprites.add(pow) | ||
powerups.add(pow) | ||
newmob() ## spawn a new mob | ||
for m in range(int(1+score/3000)): | ||
newmob() ## spawn a new mob | ||
Comment on lines
+508
to
+509
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So, you have increased number of mobs at 100% of initial value every 3000 score. Maybe it will be better to make more smooth switch? 100% at a time is a lot, it can like "no mobs" and "a lot of mobs" transition, because of x2, while reaching every new barrier will give us +33%, +25% or total amount of mobs and it may be unnoticeable. |
||
|
||
## ^^ the above loop will create the amount of mob objects which were killed spawn again | ||
######################### | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can it be that an expression
50 - hit.radius -int(score/3000 )
gives a negative value?Plus: is it unconvinient to add whitespace inside brackets as well as no space around minus sign.