Reposting a YouTube comment from vitriolicAmaranth on Part 3 of the series, as he brings up a few interesting topics for discussion:
Maybe you already changed this in a later part or maybe I’m gonna kick myself later because there’s a reason you did it differently (not really- I implemented your style of code, then commented it out and did it my way, so it’s all still there if I need it later), but wouldn’t it be better to adjust the direction of the projectile (and potentially the player sprite facing) using Mathf.Atan2(x, y) * Mathf.Rad2Deg? That way it supports analog aiming on controllers (like Vampire Survivors does) and uses way fewer lines of code, and you could even more easily adapt the code for a top-down 3D Survivors clone with a full range of player model rotation or add more player facings later on (sprites for up, down, upleft, etc). One issue with this method (but an easy one to fix, in one of two ways) is sprite rotation. This overrides any rotation you make in the prefab, so you either need to rotate the sprite in the image file itself (for some reason the Unity sprite editor does not have this capability, at least as far as I can tell) or add an offset to the rotation.
//eg my ProjectileWeaponBehaviour.cs code has
rotationDegrees = Mathf.Atan2(dir.x, dir.y) * Mathf.Rad2Deg;
rotation = new Vector3(0, 0, -rotationDegrees + 90);
//because the rotation you get this way is reversed (you need to use -float instead of just float with its output) and my sprite faces right, meaning I need to rotate it left (positive)
//90 degrees on the z axis to make 0 rotation match the "up" direction; yours would be -rotationDegrees + 45.
//This still saves a lot of work and turns about 18 lines of code into 2 lines of code in the projectile weapon script.
My bad, just saw that someone else made a similar comment 4 months ago.
I also feel like there should be a more efficient way to handle chunk generation, but having no idea where to even start with procedural generation is a lot of the reason I started watching this series in the first place, so I don’t have any bright ideas there yet (plus I know that in a later part you have returned to and improved that, at least with regards to being able to jitter ungenerated corners onto the screen).
Only other gripe I have so far (and I am more confident that this one isn’t going to cause any problems down the road, but more strongly suspect later in the tutorial it’s something that would get addressed) is that you can resolve a lot of the issues people have with their player or props or projectiles being hidden by the terrain by using sorting layers. Add layers like “player”, “enemies”, “projectiles”, “terrain” and so on and put each prefab or object on the appropriate layer, then just drag them into your preferred render order in the layers window so that for example the player renders on top of everything or almost everything and the terrain renders under everything (I left mine on “default” but this is incredibly easy to change later on if later on I want to make maps where there is something visible underneath the terrain, which I feel like I probably will for background parallax on maps meant to evoke a sense of height).
.
