Come up with Official list of Runes

[jdoleary]

Go through https://github.com/jdoleary/Spellmasons/issues/778

and come up with a list of runes that we plan to implement. Have them categorized by "desirability" (how cool it would be to have in game) and "implementation complexity" (how hard it would be to make / how easy it would fit into existing systems).

Arivia from Discord came up with an AMAZING list of recommendations: https://github.com/jdoleary/Spellmasons/issues/778#issuecomment-2162749844

And I'm doing research on Slay the Spire here: https://docs.google.com/spreadsheets/d/1WrOYUulT5AWF-fniyNFF1OcMwIpFayQeDJTm8u2YlTA/edit?gid=1371933487#gid=1371933487

Ideally, we'd start with ones that would have low implementation complexity and high desirability, but this task is just to compile an "official" list that we can go through together to decide which we want to make. I'd recommend doing this in Google Sheets so that we can collaborate on it in a table format

[SoulMuncher]

Rune Sheet

[jdoleary]

@SoulMuncher another thing we'd want to consider is if we'd let users choose a rune more than once (Risk of Rain 2 does this, allows stacking and it gets wild and fun)

[jdoleary]

From discord, so we remember

On another note regarding the rune list, there's a lot there so I'd say don't worry about choosing a "feasibility" or "desirability" unless there's particular concern for one. Most can be left blank, let's just use those columns to call out particular exceptions Also: maybe runes should be "drops" (like pickups) so that they don't scale in multiplayer. For example, if everyone gets a rune every level it'll get way too easy but if the team has to pick who gets what that could be more strategic / pushes players to try new strategies (rather than choosing them like they do with cards). Players could even drop them if they picked them up on accident maybe