This is not about moddability. That is being discussed in another post.
Suppose we have our "vanilla" mod working. Users (players) may be perfectly happy with the available cards, and that will likely be the case with the majority of users. But one may get an idea for a card that may be desirable and request that it be added.
First off, I think the GUI should reflect the fact that this is something users request from mods, rather than just have a free reign. Different modders may do it differently, of course.
Consider this:
|
Start a game |
|
My cards |
|
Create a new card |
|
Exit |
Versus:
|
Start a game |
|
My cards |
|
Request a new card |
|
Exit |
That way it is (hopefully) instinctual to the user that this is not a "free creation" mode but rather a request to make a new card available to the user base.
Now, here are the steps I think would be reasonable to include in the new card request approval:
1) DB Admin checks to make sure the requested card is not a duplicate of a card which already exists.
2) Game logic admins check to make sure the new card doesn't create an exploit or anything like that.
3) Algorithm admins check to make sure implementation is possible.
4) Theme admins check to make sure the card name, description, etc. works within the mod theme, and that graphics can be supplied or created for the card.
5) After approvals are supplied, the card is created, and most importantly, posted to the whole user base as being a new card available for purchase/trading. Importantly, the requestor would also have to buy/trade the card, it would not be given to the user for free just for requesting it.
Thoughts?
EDIT: I meant to mention this would most likely be done on the DB side, with the new card request being held in a table set up for this, and inserted into the main card library upon approval. That way we can keep track of approved and denied requests.