nvm he does @melohrush.bsky.social but he’s not active yeah

no comment, that’s a question better directed to the lead, Meloh, but I don’t think he has a bluesky account (that or he’s not active on it at all I dunno)

use the ground normal to calculate the angle of the ground rather than fetching data from the tiles. Of course we work in a 3D environment so in a 2D context you’d have to use a Raycast2D instead, but other than that it follows similar procedures to the guide, with adjusted coordinates

as for Unity functions, most of the things in that guide are math so you can get away with direct conversions. For collision, however, it’s a bit more complicated. The og games used a tile system with set data, but when I translated it over, I swapped them out in favor of Raycasts that

oh no its not all splines, the splines only tell the player what direction “forward” is, but the physics still do their own thing. Think of it as if the player moves on its own on the X and Y axis, and the splines rotate that X and Y movement to create the illusion of moving in 3D space

but adjusted to work* minor typo I just woke up mb

change to fit scenarios like going through loops. If you need an in depth reference of how the physics work, the Sonic Physics Guide on Sonic Retro is your best stop as it explains basically everything

I was the one in charge of player movement. The basic idea of it is that the player works like the Classic Sonic games under the hood (tweaked to fit the Rush physics of course) but adjusted your work in a 2.5D plane, as in the player is glued and tweaked to move along splines that dynamically-

yea fangame

fyi i know the camera in 2D is absolute garbage and i will redo it at one point but rn I'm lazy

can you see aaall of me walk intoo my mystery