Currently, we use the #sumbit-a-combo discord channel to track updates users submit to existing combos. Eventually, we will probably want to move away from this and to a system that can send this reports directly to the backend. There, editors can access everything they need in one place. This is a combination of front-end and back-end design.
For this we would need a form that the users could visit and provide the following information:
The combo(s) that need updated. We could ask them to list the cards in the combo, or provide the ID, or implement some sort of search that they can select the combo(s) in question. There would neeed to be an option to have multiple combos in this field. To start, this could just be a text field that we could update to something more sophisticated at a later date if we choose.
A field to detail the updates to the combos. Just a simple text box, probably with a character limit.
(optional) Maybe a check box for if a combo is not functional. We could use this to prioritize fixing major errors before worrying about minor misspellings, mana cost errors etc. Something simple like "[] Check this box if the combo is not functional in its current state" would be sufficient.
All this information could then be translated to the backend, probably in a separate ticketing tab that Deloo would need to design. There's no rush on this, just documenting it for the future.
Currently, we use the #sumbit-a-combo discord channel to track updates users submit to existing combos. Eventually, we will probably want to move away from this and to a system that can send this reports directly to the backend. There, editors can access everything they need in one place. This is a combination of front-end and back-end design.
For this we would need a form that the users could visit and provide the following information:
All this information could then be translated to the backend, probably in a separate ticketing tab that Deloo would need to design. There's no rush on this, just documenting it for the future.