Work in progress update to my Destiny Stats Machine: a point-n-clicky app for armor profiling and loadout finding. 🎮📊
@bsag Yes! Thanks, my first try at doing anything in Shiny. Being so used to moving linearly through things in R and Rmarkdown, getting my head wrapped around Shiny's structure has been kind of an adventure.
@peroty Indeed! I don't like using the DIM loadout builder, so I made something that would let me spec for totals in certain attributes and see the impact on my other stats at the same time. It also shows me what armor is in common across multiple builds. I'm working on being able to export loadouts and save them back to DIM, but that's really kludgy, so for now it's mostly a tool to find that kind of insight that I would otherwise miss. Wanna try it out? I have to write up some instructions but I think it's reasonably usable now.
@alans Yes, Shiny reactive functions really strain my brain! I've created a multi-page Shiny app for work, organised into modules. It's fun to write, but much more challenging to test and debug than RMarkdown documents for sure. Over the time I've been building it, I've found that building Shiny apps as R packages and ruthlessly separating the server and UI functions from all the other code makes it easier to test the code outside of the shiny environment.
@alans Once I finish turning in my 18,000 Crucible tokens I need to figure out a way to look at the pile of gear.
My vault needs cleaning. I'd be curious to try it out. Always looking for cool things people make for the game.
@peroty I only had 12,000 crucible tokens! I got them turned in last week.
There are some light intructions at the bottom of the sidebar for the loadout thingy. I really don't know what will happen when someone who's not me tries this out, but I'm excited to hear what you think! You need to start by exporting an armor CSV file from the DIM preferences page, and then can walk through the app. It doesn't yet have the last mile to produce output that DIM can read back in to make loadouts from this tool more easy to use -- I may get to that today. deardestiny.shinyapps.io/ArmoreR/
@bsag Debugging is hard. I need to figure out a method so I don't have to reload the whole thing and step through each action before I know if my change worked or not. If I'm going to keep at this thing, I'm definitely going to have to get more disciplined and organized so that I have a chance of doing what you describe.
@peroty I think I got save/export working. The format's a little clunky to use in DIM at the end of the workflow, but perhaps useful.