I had a good time this weekend coming up with a new way to visualize armor stat distribution in my Destiny 2 profiler tool. 🎮
Just learned of {httr2} (https://github.com/r-lib/httr2), a rewrite of R’s httr package, and am excited to try it out! The pipeable API looks like a nicely improved way to build complex requests.
I’ve had a nice afternoon working on my hobby R/Shiny project, a loadout finder for the game Destiny 2. These improvements make it a lot more flexible and informative: It can now optionally include armor that would otherwise be filtered out of configurations by the minimum stat threshold, and it will show current mods used in displayed loadouts.
I’m sure it poses some benefits for systematic parsing (and I’m certainly much more comfortable working in R and markdown, for what it’s worth) but Jupyter’s reliance on json for its file format seems like a big disadvantage for readability and portability.
I: Spend days carefully curating config files, reinstalling homebrew and trying variations of arm and x86 binaries
RStudio: Do you even ODBC, bro?
I: Just profanely put the path to the driver in the dbConnect call, disregarding all documentation and common sense.
RStudio: Yah here’s your SQL Server.
Dearest Ada, it has been two days since I began editing odbcinst.ini, and still SQL Server repels me. Tomorrow, we will sudo brew reinstall FreeTDS. With our persistence, someday, odbc::odbcListDrivers() shall yield results and I will be at peace.
/wistful violins
This revision of ArmoreR is really turning into something I’m happy with and proud of. I’ve learned so much since the very first iteration of this about a year ago. It’s really fun and rewarding to come back to it with a bunch of new expertise and make it much better in all ways, including a new approach to dealing with such a large amount of information.
(best Letterkenny voice)
Sundays are for fixin’ Shiny!
I spent a bunch of the weekend beginning a redesign of my ArmoreR project, which aims to be a Destiny 2 armor stats profiler built in R and Shiny. A year on from when I began it, I have a much better understanding of how a Shiny app works, and have also incorporated a proper, working oauth2 workflow into this revision (incorporating the things I figured out for my power level tracker). It’s really, really satisfying to be rebuilding it with all the things I’ve learned. I think the application is going to be so much better and less complicated than the first iteration. I still have a ways to go, and am happy with just how much I have transformed it with a year of learning and practice on other things.
Last fall I wrote a bit about a Destiny 2 power level tracking tool I built using R. I’ve now converted it to a full-on Shiny app and solved some issues with the oauth2 flow that stumped me in my intermittent tinkering with it. I’m super satisfied to have been able to get this to work! Now that I have the authentication process figured out, I’m eager to also convert my armor profiling tool to use it. Look out!
You can check it out here: traveleR