Discuss Scratch
- Discussion Forums
- » Help with Scripts
- » continuation of https://scratch.mit.edu/discuss/topic/906235/
- chickenandcheesesand
-
Scratcher
100+ posts
continuation of https://scratch.mit.edu/discuss/topic/906235/
- leog20162
-
Scratcher
100+ posts
continuation of https://scratch.mit.edu/discuss/topic/906235/
dude i gave you the code to fix it
- chickenandcheesesand
-
Scratcher
100+ posts
continuation of https://scratch.mit.edu/discuss/topic/906235/
dude i gave you the code to fix itdoesnt work
- dem_bot
-
Scratcher
1000+ posts
continuation of https://scratch.mit.edu/discuss/topic/906235/
I am rather confused by ur code. A few things I noticed:
1: cube 1 and 2 seem very similar, can't they be clones?
2: there's a lot of broadcasts, which seem to not really do a lot important
3. a few threads have a forever loop in a loop EX:
5: your main sprite determines the current collider, meaning each frame you only check collisions with one thing
6. a bunch of custom blocks look very similar and have similar names, so it'd be nice if you add some comments explaining what exactly they're for as now it seems you just got several physics engines.
1: cube 1 and 2 seem very similar, can't they be clones?
2: there's a lot of broadcasts, which seem to not really do a lot important
3. a few threads have a forever loop in a loop EX:
forever4: you have a few poinless things like a stop this script at the end of a script
do awesome stuff
end
define do awesome stuff
forever
do thing
end
5: your main sprite determines the current collider, meaning each frame you only check collisions with one thing
6. a bunch of custom blocks look very similar and have similar names, so it'd be nice if you add some comments explaining what exactly they're for as now it seems you just got several physics engines.
- Discussion Forums
- » Help with Scripts
-
» continuation of https://scratch.mit.edu/discuss/topic/906235/
