|
Link's Dirty Sock
Join Date: Jun 2008
Location: England
Posts: 40
Reputation: 10
MMOFaces Profile:
None Yet
|
Detailed Template
Quote:
How to: Present a Game idea, WIP, Team Requests or Program Announcement and handle comments, flamers and moderators.
Some of these things are most likely common spread over all of us, forum dwellers, some are purely personal preference. However, seeing that many still fail to post their work in an attractive or inviting way, I thought this might as well be worth the try (and I was bored). This post is about what creates a good, fun place to stay. Most of it will be pretty obvious but hey, I've learned from recent experience that having it written down somewhere strengthens the just.
Posting
Titling is half the work. The first view of the page is another 25%. Now you need that last 25% to make perfect project posts. Here's how.
Game Idea
First of all, a game idea differs greatly from a story (which is also allowed on the specific boards, but still). You could write a Tolkien-beating epic story, but a game has specific needs for the story. What a game idea is, is a short and powerful summary of gameplay, setting, story and atmosphere. Lets analyse a Game Idea post similar to the kind you see a lot on the Game Theory board:
Quote: "The evil king of the Northern lands assaulted the Southern Empire and the hero (the player) tries to stop the invasion. A long adventure awaits as the player goes and defeats the evil king."
What is wrong here?
* First of all, it says completely nothing about any game. This could be a book, a movie, a comic series or whatever, but it is not a game. There is no element of gameplay described at all - what genre is the game, who does the player represent. What motives are there?
* Second of all, even if the post were formatted to include genre and the like, why would this game stand out? Your game idea is posted to attract people who like the idea, I assume, not to post a random story as someone once stated. Why is this idea so much better than the other ideas around?
That's what's wrong. If we'd fix that, we'd have something along the lines of:
Quote: "In a fictional Dark Age world, the evil king of the Northern lands assaulted the Southern Empire and the hero (the player) tries to stop the invasion in a first person standard RPG-adventure (grind, level and farm) in the Southern lands. An important and rather unique feature of the game would be a gesture-based magic system, which would also allow for customisation. A long adventure awaits as the player goes and battles from his homelands to the castle of the evil king."
Much better. Now let's take a look at how it could be even better. What makes a Game Idea stand out? Media, details, basically any sign of careful working on an idea or a well worked-out idea. For the above RPG, you could for example add a description of the lands, add a sketch of a land map or the like. The more the better: Engulf the reader in your world, your idea.
Work In Progress
A thread on when a WIP is ready for posting: Here.
A WIP is a post notifying the community of a project in an advanced state. Advanced state means the project is in actual development, and has shown significant progress. Anything with less than these requirements is considered a Game Idea and should be in the Game Theory boards. For some, a WIP motivates to finish a project, for others, silence in their WIP thread means the end of their enthusiasm for a project.
So, let's start by saying what nót to do, basic WIP rules:
* Do not post without any sign of progress on the actual game.
* Do not post without media. All media goes, as long as it is relevant and usable. A paint-drawn 2D image of how the high-poly main character should look is a big no. Basically, even a very detailed list of characters counts, but the usual tendency is to have screenshots.
* Do not use anything that can be held against you. Don't lie, don't claim things that aren't true.
* Do not post WIP's for projects that you are not at least planning to finish and/or capable of finishing.
Next, let's look at what makes a WIP interesting.
* A well-described game idea. What are you making anyway? The editor looks cool, and it's programmed perfectly, but what does it create and for what game?
* Attractive presentation. Have a game-logo, website and the like. Take care of the layout of your post, make sure it all makes sense. Locate images on regular intervals and post code in the code brackets. Use the available options to make the post as readable and attractive as possible.
* Media. Images are good. Video is better. (Tech-)Demo is best.
* Clearness. Use the 'icon-setup' to indicate what is done, what is being done, what will be done and what would've been done but isn't being done. Make a list of everything that is needed and use icons to indicate any of those statusses per item. Don't forget to add an explanatory list of what each icon means.
* Updates. Keep people close to what is being done. Again, use screenshots or start a regular update interval (weekly or monthly). Do not overdo this - post only if something impressive comes up (unless using the regular update interval). In most cases, overdoing the updates is considered bumping and will result in people turning away from the thread.
* React. Good WIP's are distinguished by friendly and responsive posters. They take time to react to any comment they feel is necessary and take constructive critisism, even if harsh, happily.
A good WIP thus depends on what you've got to show. If you've got nothing, don't. Don't post your story with an image of Final Fantasy XII, we won't buy it. People around here know every spot on the web and every rip or theft will be found out. Work in Progresses are for projects that have already taken off and are in development - personally, I've found waiting with posting a WIP until you're at 50% of development or more seems the smartest thing to do - basic rule: Wait until you can blow us away!
Team Requests
Team Requests are a special form of Work in Progresses. You can only post Team Request if you've adhered to the rules of the WIP forums and have any progress. Again, keep to the above rules, except for the progress one. The difference between a Team Request and a Work in Progress is that in a Team Request, the poster need assistance in a project. However, the poster himself will need to be capable of showing progress. Let's analyse a team request:
Quote: "I'm XYZ and I'm creating a Dark-Age RPG. I need someone to code the engine and some artists to create the media for the game. I promise all teammembers a percentage of the sales profit!!!"
There's nothing good about this Team Request, first of all, it does not adhere to the WIP rules (no progress, no detailed game idea, nothing), but it has some specific Team Request errors.
First of all, in this example XYZ is doing nothing - he fails to explain his part in the creation of the game. Producer or 'the man with the plan' isn't good enough, you need to be either an artist or coder to work on a game. Second of all, the chance of any profit at all is near zero - do not promise what you can't give. Be realistic and realize most idea's here never earn anyone a penny.
Finally, the post is very unspecific. What do you need? Textures? Models? 2D artwork (buttons ect.)? Menu code? Engine code? What task does everyone get?
Logo.
Quote: "I'm XYZ and I'm creating a Dark-Age RPG. Game Idea Here. I personally have created a basic engine Icon-list progress or features here. Also, I created all of the 2D artwork (screenshots go here), but my modelling, however, is terrible, and I need some artists to create the media (textures and models) for the game. Besides crediting, I can promise nothing, but might the day ever come that the game yields any profit, ofcourse I'd share."
Much better. Again, the more detailed, the more specific, the better. For Team Requests, I can only advice you to contact a mod in advance. Explain what you want, what you need and let them tell you what they advice. Having a mod at your side is always a good sign.
Finally, make sure you can run and lead a team, and cap the team at a max of what you think you can handle. I can tell that having a team is hard work - keeping everyone happy and synchronized will require extensive planning and organisation, instant messenging or the like will always help. Keep the team small and efficient.
A last tip, thoroughly scan any new offer - test them if needed. Give them a test and be patient. Do not rush when accepting help - especially on long-term projects. You might never know if someone better comes along.
Program Announcements
First, check the following:
* The game starts well on different systems and is as bugfree as possible.
* The game is complete or at showable state.
* You've created a zip-file or installer which contains all required files.
* You can handle critics.
Your game is done. Perfect. You've done it - it's there. Now, time to present it.
First of all, is it commercial or freeware? Depending on that, you might need a demo version and change the tone of your post. A commercial game will need to really 'sell' the game with the presentation.
Ideally, the layout would resemble something like:
Quote: "
[Logo]
The logo of the game.
[Introduction]
Short summary or introduction of setting, story, atmosphere, genre and the like (i.e. price).
[News]
Updates, patches, whatever? Goes here.
[Features]
What makes the game special? List it as clearly as possible.
[Media]
Screenshots, Video, Music, whatever.
[Relevant Links]
Where to buy, website, forums, ect."
What you'll need most is media - us downloaders stay away from what we can't see in advance. Again, the more detailed, the better.
Why do you need to be able to handle critics? Simple: Because you're going to get some anyway. No game is perfect and there'll always be people who are going to dislike things. As with the WIP's, be honest, fair and understanding. Don't attack constructive criticism.
|
This is taken from the TGC Apollo Forums, i think it may be a good help to new posters, please take your time to read it.
Thank you
Svothe |
06-24-2008, 04:27 PM
Linear Mode
