i did a bunch of work managing preferences for keybinds, comments, and other weird quality of life changes in Rider to make sure it was working the way i wanted. i ran into some issues here and there, and fussed with them longer than i probably should have. ultimately, things feel right, but the program consumes a surprising number of resources. it got worse as i made changes, so maybe it's just related to those changes and not the typical performance of the program itself. other programs started hanging up and at one point Unity just straight up crashed on its own (unsure if it was related to the constant 100% CPU uptime that Rider was asking for). even now i'm still getting weird IO lag trying to type stuff into this box.

afterwards, i started putting together a little UI thing to display some data out of the player physics in real time. i ended up needing a lot of little tools like displaying arrows for normal, velocities, etc. so having a box with checkboxes to click and current states listed would be very convenient. plus i get an early check on how i want HUD stuff to respond to game changes!