accidentally included the same picture twice in the second post, so here's the corrected version.

last one is rather vile.

Reason move_and_slide has been causing me grief in the first place is b/c I started work on a custom solution for handling upward stair steps—and needing to handle that logic either entirely before or entirely after the full move_and_slide call has made it that much more awkward to implement.

Yeah, I’ve been considering switching to a series of move_and_collides instead—I’ve just been dreading the thought of needing to reverse-engineer a lot of move_and_slide’s unique (and useful) quirks.

Like, it’s great how it can condense multiple loops of convoluted collision logic into a single function call. On the other hand, it feels like a black box whose inner workings you’re not allowed to tinker with. You want to insert your own custom code between the individual collisions? No. Too bad.

anyway I realized shortly after posting this that Class isn't even a valid Object/Variant type to check against. oops.

i was waffling between that and this

I *know* about exports, but the sliders and text boxes are frankly annoying to manage when I'm setting up foundational systems and classes—trying to keep as much as I can neatly contained in the actual scripts, where all the other important stuff is.