SpaceCowMedia / commander-spellbook-backend

The Commander-Spellbook editor dashboard made with ❤, Python and Django.
https://spacecowmedia.github.io/commander-spellbook-backend/
MIT License
13 stars 3 forks source link

Modify Attributes to Only Show Those Used in a Feature on Combo Page #549

Closed GordonsKitchen closed 1 week ago

GordonsKitchen commented 2 months ago

On the combo page, it would be nice if the attribute boxes for a feature would only show attributes that the named feature has. So for example, "Free Sacrifice Outlet" would only show: "affects-artifact", "affects-creature", "affects-enchantment", "affects-land" and "adds-mana" when you go to type something into any of the three attribute boxes. This would make it much easier to find the attribute we need, and also would make it much easier to see the options available for a particular feature, rather than always pulling up the feature page to see what attribute is needed to be used. If an attribute isn't in the feature, then it doesn't need to show up for that feature. I envision this would take the name entered for the feature and use that to filter what attributes show up. The criteria would be that an attribute must show for at least one card in the feature for it to be displayed. If the feature name box is empty, either show nothing or everything at your discretion, or even a message like "Please specify a feature for attributes to show here". You'd probably want a message for no attributes for a feature as well - like "There are no attributes used in this feature".

thirdpolice commented 2 months ago

This is another idea but since it also relies on associating attributes with a specific feature we decided to add it here:

Feature pages could have a second attribute field in the "produced by cards" section, call it "specialized attributes" as a placeholder.

This field would work just like attributes, and could hold any attributes. The only difference is that, when a user creates a combo with that feature, all attributes in the "specialized attributes" field of that feature would autogenerate into the combo page's "None of attributes" field.

This would make it much, much more tenable to make our feature pages comprehensive, without requiring editors to remember and manually enter a large number of "None" attributes, or to navigate a byzantine system of hyperspecific features and feature—>feature combos.