Unity Top Down Colliders and Character Movement - Tutorial 

Thank you! :)

Thank you! :) I wanted to make it a bit more entertaining.

I'm happy too! 😃Welcome to my channel!

Hey, thanks! :) Well, it depends on what kind of jumping you are talking about. If it's a tumble like dodging arrows fast, then it's pretty easy and I'm planning to do that. However, I have a feeling you are thinking about real jumping like between platforms an such. It remains simple as long as the overall world of the game is flat. Like in this game, the map is flat and there are no hills, the "terrain" is flat. But if you want to have hills or platforms that are taller to jump in between them, then it becomes very cumbersome in this game's full 2D solution. And I would recommend a 3D isometric solution with the same sprites. You couldn't tell the difference in looks. It's a bit harder to implement the basic mechanics but handles the 3D space way better (because it's literally 3D) so any kind of jumping would be possible to implement. All in all, if your jumping remains in a flat world then it's easy, but if it requires upwards and downwards motion in a 3D space like in Monument Valley, then this 2D solution makes it hard and not feasible.

I've found it not long ago, such a great component. :P Solves all the previous problems.

I'm glad you liked it. ^ - ^ I think I'll mention Time.deltaTime and stuff like Update() FixedUpdate() more in the future. They are just such frequently used things.

when you get the hang of it I'd also recommend writing your own wrapper for the delta time in general. that'll put you in much more control over the time flow in your game. as an example, while setting time scale to 0 is useful to pause the game, it would also freeze all of your animations in place (because they rely on this scaled delta time), and you'd probably want to keep some of them in your pause menu. you could also use the so called unscaled delta time, but oh boy, rolling your own is always much more handy. and can be fun as well.

Thanks! I’ve been playing hide and seek on RU-vid, that’s why. :D

I'm glad it helped! :)

I only have plans for local multiplayer. It would be fun to have online multiplayer, but it would take a lot of time to get it right, and with that time I could develop the next game instead. :) Thanks for the sub, and welcome to my channel! ^ - ^

Thanks! Yeah, I'm thinking about the entertainment part of the video a lot. I don't want to have you guys to fall asleep. :D But because I write the scripts for the voiceover beforehand, and I'm not an actor :D the little jokes doesn't really end up being good in the end. I plan to go off script soon, let's see how it will go. :)

@@CouchFerretmakesGames heck yea, gdluck with that ' w')b

You are right! The individual walls didn't need to be kinematic they could have remained as static objects. I messed it up, I'll make sure to have a dedicated episode on the collision matrix to sort this out once and for all. :) Thanks for pointing it out! Odd, I know, but the CompositeCollider requires a RigidBody2D component. It was strange for me as well and I tried to remove it, but no luck.

Godot is a good and free alternative, but you could use most of the game engines out there probably.

ok thanks!

mine too :(

I think I would go for the 2 separate game objects, or even 3. The third one begin the bridge which will be turned of if the player has opened the bridge.

i'm having the same problem, did you ever figure out how to fix it?

@@goingsillymode No I did not, sorry

@@shockingshinx12 alright, thanks anyways!

Hey Kiwi! I missed you! :D I hoped that you haven't stopped working on your games, I'm glad you didn't. :) In a collision, you can access the exact colliders that were participating in it, and based on that you can handle the different scenarios. So for example: void OnCollisionEnter(Collision collision) { // This will be the sword's collider for example when the enemy hits your sword // But it will be your body's collider when the enemy hits you Collider myCollider = collision.contacts[0].thisCollider; // And this one is the enemy's sword's collider, this could come in handy Collider myCollider = collision.contacts[0].otherCollider; } But instead of checking the exact participating gameobjects, I would go with checking their tags and decide the damage taking based on that. Like for example, there would be "weapon" and "player" tagged objects with collider on them. Hope this helps! Let me know if not. :D Cheers!

@@CouchFerretmakesGames Hey, I've missed you too! It's been awhile since me met, but it feels like just yesterday you had only 400 subs! Now you have 4,000?! Well done and well deserved! And I don't imagine I'll stop programming anytime soon, I've had some success with my game on Itch.io: I reached 250 views :D , and there's no way I could've done it without you. 250 thanks you's! I'm a bit confused about the Collider myCollider = other/this Collider How does the other/this argument work? And I do use the tags "weapon" and "player" to deal damage; the enemy's weapon has a script "Weapon", which runs like this: if col.gameobject.tag = player, col.getcomponent player.HP-=10 but its still an issue because when the enemy weapon collides with the player's weapon, the weapon counts as tag = player since its a child object of the player, and the player takes damage.

@@kiwioverlord9519 Hey Kiwi! I've put together an example for you and sent it in an email. However, the code looks like this and is attached to the Player gameobject (the parent): using System.Collections; using System.Collections.Generic; using UnityEngine; public class MyScript : MonoBehaviour { public Collider2D playerCollider; public Collider2D swordCollider; void OnCollisionEnter2D(Collision2D collision) { ContactPoint2D contact = collision.contacts[0]; if (contact.otherCollider == playerCollider && contact.collider.tag == "Weapon") { Debug.Log(gameObject.name + " get hit"); } if (contact.otherCollider == swordCollider && contact.collider.tag == "Weapon") { Debug.Log(gameObject.name + " parried"); } } } And the swords are a simple child object with a collider. Oh and yeah the Players have rigidbody2d components because they are necessary for collisions. :)

@@kiwioverlord9519 And thank you for the support :). I really appreciate it, and I'm glad that my work helped you. I'm happy to hear that. :) Don't forget to link your game so I can check it out.

@@CouchFerretmakesGames Hi, oh yeah here's the link: kaiway.itch.io/spintowin It's pretty sophisticated if I do say so myself, so take a look at the Controls page. Also, I've got to add you to the Credits section! Is there a way to make Unity redirect to a link, like your RU-vid page? And how do you want to be addressed in Credits? Just "CouchFerret"? And my support is the very, very least I could offer for the absolutely priceless help I've received from you! :)

I'm working on it to have the scripts available online. Unfortunately, until then they are only visible in my videos. :/ I'm sorry!

@@CouchFerretmakesGames can u load them on cloud or github for now? Ты случайно русский?

might need to click the 'is trigger' for oncollisionenter function? Or make sure the 2d vs not 3d's match for collision types. Those are my usually things that cause me problems but I'm not expert

Welcome! :)

I'm glad to have you here!

Как и везде )

Hello! ^ - ^

I agree!! I don't know either. :D

It's 1.6k now! :D Thanks man! I think I'm growing in a healthy manner. :)

Yep, it should be enough to just put an rb on the player and do the walls without one. I think I'll dedicate a whole episode to the collision matrix in Unity and I'll fix this then. Thanks for pointing it out though! :)

Thanks for the suggestion. I should have mentioned it in the video. I'm aware of the SerializeField decorator, but I'm coming from a Python background where there are no access modifiers and you are also allowed to do almost anything. I like this kind of freedom, and I think it's a bit clearer too (but more error-prone too). However, both the SerializeField and public are accepted and commonly used practices. I think I'll mention it in the next programming episode. :) Thanks!

Hey! :) Well, it depends on what kind of jumping you are talking about. If it's just a simple jump like jumping over a fence, then it isn't that difficult, just a few tweaks with the colliders for a short amount of time to let the character go through the fence. However, I have a feeling that you are thinking about jumps between platforms and such. The thing is that it remains simple as long as the overall world of the game remains flat game mechanics wise. For example in this game the map itself is flat, there are no hills. But if you want to make the character jump between platforms with various heights and fall if he fails to jump long or high enough then a 2D solution like this game have will be tough. I would recommend making your game in 3D isometric perspective but using 2D sprites to still keep the 2D feeling. In 3D you can simulate the correctly the positions and not just fake the third dimension like I did in this game. However, if your platforms and the ground remains flat in your game, and you only have a flat surface with holes in it, then that could be managed in this 2D solution. Hope I make sense! :D Let me know your plans in detail so I can suggest a solution for it. Like reference existing games, or describe the limits of the system, so we can decide that a 2D solution works for you or it would be wiser to switch to a 3D but 2D looking game. :) Cheers!

@@CouchFerretmakesGames Thanks for your response! Looks like im going to make it flat then! haha, You caught me, i was thinking in simulating that kind of 3D. Mostly for pits or cliffs so the player can jump them down, (just like in Hyper light drifter or in CrossCode) However i dont think im going to add it, but the curiosity got me to ask you. Thanks again for your time to answer me. it really helped me a lot!

Did you find a solution?

make player and walls layer = position.y

That's a tough one, but pretty cool idea. I'll think about it to have it in the game. Thanks! We could achieve that with collision detection functions like OnCollisionEnter2D, and with a new animation parameter. However, I think the main struggles with this would be to find out that the character actually running into the walls or just running near the walls.

@@CouchFerretmakesGames (didn't watch the video yet but) the animation should stop only when the character velocity stops. if the character sprite stops due to hitting a collider (velocity = 0), its animation should also stop (animation = 0). if it doesn't stop (velocity > 0), the character is either sliding along the edge of the collider or not hitting the collider at all, so the animation shouldn't stop as well (animation > 0). the result will look natural, and the game will play as expected, with no major changes (not even OnCollision events are needed). you already have the case where velocity = 0 and animation > 0, which is basically the idle animation. (if you don't have it already, it's well supported anyway), and the only case where you want the case of velocity > 0 and animation = 0 is if you want to have a character fly off due to damage (maybe bounce in the air slightly like a ragdoll) or some other physical force that might act on him (you know, like spring traps etc). in that case the walking animation might appear uncanny, simply because his legs are detached from the ground, and in general, this is how you convey the notion of an involuntary movement in such games (if no other animation is dedicated to this context).

That's true, thanks for pointing it out! I should have covered static colliders (without rigidbodies) in this episode. I'll try to talk about it in the future. Although at the end of the video I have only 2 rigidbodies, 1 for the player, and 1 for all of the walls (on the Grid). Sadly, CompositeCollider2D requires a RigidBody2d. :/ But, and extra rigidbody or even a couple of extra rigidbodies won't have a huge difference in performance. Usually I try to keep things simple, but want to cover more advanced stuff in the future too. The Collision action matrix would be awesome to cover with all of its 6 different kinds of gameobject setups. Thanks again for the critic! :)

@@CouchFerretmakesGames no prob im enjoying your vids tho they are really well put together. :)

@@irishbruse Thanks! I'm still seeking ways to improve it.