Hello all,
recently we noticed we do not have that many game templates, especially no adventure templates. To improve this situation we can make a sort of contest to create some of them.
The benefit is that nobody would loose:
- template creators get experience in game creation
- judges are able to compare different solutions
- readers can choose from different templates to create own games
My questions are:
What should be the minimum features of an contest entry?
Should all entries base on the same story?
Do you think it should be a context with a ranking (similar to BGMC)?
What would you judge and how?
My ideas on this:
Minimum features (game aspects):
[table=“class: grid”]
[th]Genre[/th]
Point&click adventure with rendered backgrounds
[th]Navigation[/th]
Fixed camera with scene switching
[th]User input[/th]
Point&click interactive objects
[th]Menu[/th]
Not required
[th]Interaction[/th]
Object selection, Dialogsystem
[th]Storyline[/th]
Linear
[th]Feedback[/th]
Animations, Texts
[th]Music[/th]
Yes
[th]Sounds[/th]
Yes
[th]Persistence[/th]
Savepoint
[th]User manual (game)[/th]
Yes
[th]Usage instructions (template)[/th]
Yes
[/table]
As said these are minimum features, better features (e.g. branching storyline) or more features (inventory, cutscenes, multilanguage, configurable input, object hover, in-game help) are welcome but not required.
Judging
a ranking is difficult and subjective, but not impossible. Maybe some reviews can help with notes to each aspect of the template.
The story should be very short (as it is a template) but still show what is possible (minimum: two screens). Open question: one story for all, or each one can come up with own stories. We might even collect stories each contributor can choose from.
The asset quality does not need to be high but good enough to attract people. I think papercut drawing style would show it is a template without being to demanding or frighten later users. [A scene full of cubes is a bit to primitive and should be avoided.]
Team entries: Yes.
This is pretty much work so a team is a good idea. A team gives feed back if the resources are understandable (as it needs to be when finished).
Time
How about two weeks?
Versions
Obviously an entry would be a single version.
I strongly suggest to provide a version to each entry before submitting (mostlikely 1.0). If you care your work I expect you or your team do some improvements pretty soon. With a version number you can show there is progress and old reviews might be invalid with it.
You should also think about how you want to update your entry with bugfixes. [Nothing complicated, a complete replacement can be sufficient enough]
Is it worth? What do you think? What would you add? What would you skip? What would you do differently?
Thanks
Monster
