Hi Makecode Team,
How to check overlap events for player overlapping on Enemy’s projectile and is there a way for this projectile to follow the player ?
I noticed that even though I have set the projectile to start from monster sprite (the sprite has bobbing animation), I see that the projectile is created from static location. Am i missing something?
Full code at https://github.com/mintgenie/daveawesome-throwback/tree/SpideyFire_lvl3
Seems to be working for me:
Make sure the variable you are passing to create projectile is assigned; you can use the debugger to check
as for following, we have a “follow sprite” block in the sprites category
@richard, thanks for the pointers, i made sure that i am using the right values but If both player and enemy have projectiles then there is no way to differentiate between player overlapping projectile and enemy overlapping projectile (ex. player shoots bullets and enemy throws fire). Here both enemy are player are triggerring their own events.)
I dont have a way to test for projectile from enemy or player.
is this a feature request or is there a work around.
Here is the latest code: https://github.com/mintgenie/daveawesome-throwback/tree/SpideyFire_lvl3
Please help. I want to move to next step but these are bugging a lot.
You need to change the “kind” of the projectiles. By default all projectiles have the kind “Projectile” but they can have their kind set just like any other sprite. Here’s an example:
Here I created two kinds: PlayerProjectile and EnemyProjectile. That lets me split up the overlap logic for both kinds of sprites.
Oh ok… now I see that i had (once again) completely missed this “Set mySprite to kind < >” block rather, i had only tried using the Set without any luck. I works now…
You saved my day again!!! Thanks.
Here is the update: https://makecode.com/_KMoKbhEE3U0A
The browser is sooo slow with this huge set of blocks and dont let me make quick changes. are there some tricks to speed this up (may be option for stopping live compilation)
The best way to speed things up is to collapse the simulator (the grey arrow tab next to it)