If you've done any work in X and Y positioning, you'll notice that there are some SERIOUS issues that you can run into. Sometimes you want to program an objects movements from scratch. But then, you run into a SERIOUS problem that cannot be fixed. The object will COMPLETELY ignore any solid objects.
When I studied GML (I didn't get very far) I learned of a very useful line of code. I can't remember how it went exactly, but basically it checked to see if there was any free pixel space from the object. And it'd check it on a certain side of the object. If this was added into PB, that would be AWESOME! We could say,
"If block 1 left free space => 1"
That would say, if the left side of block 1 is further than 1 pixels away from something solid (counting pixels) then do something. Just imagine the possibilities that could be unlocked just by making this one addition.
Another thing.
Sometimes somehow in certain special situations, the player can get spawned into something solid or have something solid get spawned over the player. This can A: Make the player get stuck B: Cause the player to need to get out (if even possible). This could be fixed for ground tiles by PB checking what tile the player is stuck on. Depending on the tile, it can move the player out. Yes, it'd be complicated, but this is a serious issue that needs to get resolved. If it's a custom block, than we can define if it's a top, down, left, or right block. In other words, if the player gets stuck in the block, in which direction should the player get out from?
TingThing, these are essentials. Please strongly consider adding these sometime hopefully in the near future. You can't leave these out.
(Not an 8.0 suggestion)
