Brido's Biographist

The max charge tosses that pumpkin way further than you ever need to. The max charge toss should probably match up with the outer most limit of where a crate can spawn

You just have to hit the crate at all, not necessarily get the pumpkin into the top of it. Would be more satisfying if it actually went in the crate, imo

I wanted to do a particle system in front of the camera for the falling leaves, but didn't have time to figure out how to do that, so instead I used multiple game objects with movement routines that reset themselves upon hitting the ground plane.

Handy solution for quick handling of a multitude of UI menus: collect them in a List, then when Escape or other key of choice is pressed, you can close out the last opened menu until none are left, then allow for pause/options to open like so:

@pro-forma-nails True, I don't tend to use cyclical references; in that case, instead of rejecting duplicate entries, you could set them to the top like this:

but if you find yourself in such a twist, I'd switch to using a Stack; the above would pretty much simulate a Stack with our List by manually managing its order, but we can eliminate such need and potential for error by using a Stack. Stack has some nifty functions such as Pop and Push that make it ideal for order-concerned usage: Pop removes and returns the top item, Push adds an item to the top of the stack. Here's what it could look like:

(I added some safety checks for the while loops, they ideally shouldn't be needed but of course the road to hell is paved with "that shouldn't happen"s 😅)

In the simple approach I use List for its easy Remove functionality, which Stack does not have; you can only Pop or Peek at the top most item (Peek retrieves the top item without removing it). But by creating a tempStack to rebuild from we can mimic List.Remove behaviour for closing out a selected menu. Then Escape usage looks like this:

This 'snippet' got a little verbose so if you'd like you can take a gander at it on github~ in that version I've turned the loops into a shared RemoveFromStack function so we don't have to write the loop logic twice, and added a ToggleMenu function.