TehomCD
commented
5 years ago The implementation for this was pretty hacky - it's something like tags and then attributes that happen to match the tag names for associating strings to it. I'd kind of prefer migrating rphooks to something that actually has relational data - Different hook types that are searchable, then the join table/through model that has their description, as well as any other data we'd want to attach.
It's up to you if you want to bother with that. It just seemed like it might be sensible to do at the same time, especially since once they're actual models you could use generic class-based views for most of the boilerplate.
codersquid
Is your feature request related to a problem? Please describe.
I'd like to have an easy way to navigate rphooks. In AMA, someone brought up the idea of having finger information on character sheets. I've wanted that kind of information before. The rphooks info would be particularly nice.
Describe the solution you'd like
Add the information to the player details page.
On top of that, maybe have a tag cloud page for rphooks.
I can see about doing them assuming I can get a dev environment back up.
Describe alternatives you've considered
Not bothering and just using finger and rphooks as is.
I don't want to spend time implementing this if it's not something people would like/use. There are other things people might like more that I have an interest in.