[h1]Article Submission Guidelines[/h1]
[h2]General Guidelines[/h2]
In order to help you achieve the highest quality possible, we have produced a set of guidelines for you to follow when setting about writing an article. There is an extraordinary amount of talent to be found amongst our members and we wish to let you show your skills off to the community at large.

Please take the time to read these guidelines. Our proofreaders take them very seriously when approving articles for publication, so if you don’t follow these guidelines, the chances are your article will be rejected.

If you have a brilliant idea, but don’t feel you have the skills to put together an article, please contact one of the admin staff. We will be happy to help you get your idea of the ground if we can. The same goes for those members with English as a second language. We can help you with translating your masterpiece into English (this does take a fair amount of time though since none of us are particularly good linguists).

[h3]Why Write an Article?[/h3]
Ask yourself this question and try to be honest with your answer. If your answer is something to do with gaining points towards ranks or improving your standing within this community, then stop right there! We believe that the best articles are those that come about because the author wished to share their experience and skills with other members, not because they want to earn points towards a new rank.

We will reject any half-hearted attempts pretty much straight away, so save yourself the bother and us the hassle and don’t write articles for the sake of earning some benefit for the author.

[h3]What to Write About?[/h3]
If you have a genuine desire to see your work as a part of the community, you should probably already have answered this question. If you have to ask this question, the chances are that you are just seeking personal satisfaction, so go no further (see above).

The One Ring is a Lord of the Rings fan site centred around the Games Workshop Strategy Battle Game. Obviously the subject of your article should be contained within that topic. We have several categories of articles and so there should be something that would suit that is within your skills.

Before commencing however, take a look at the current month's theme (if applicable) and see if your topic is relevant.

Look also at existing articles in the library and see if your topic has already been covered. If it has, ask yourself if your article will bring anything new to the topic. Or does it explain things better, or whatever. We don’t want to have several versions of the same topic and so we will reject articles that don’t meet this requirement. We will, however, accept a number of articles on the same topic if they present significantly different ways to achieve the end result.

[h3]Spelling and Grammar[/h3]
We will not accept articles that have a significant amount of spelling errors. The same holds for articles with excessively poor grammar and syntax. We strive to provide the best fan site on the internet, and we expect you to take the same level of pride in your work as we do in ours.

Of course, we fully understand that this is a multinational website and our community comes from any number of non-English speaking backgrounds, so we will do our utmost to help you to achieve the best results possible.

Your word processor will have a spell checker tool. Use it! Read the article through a number of times to catch those errors that the spell checker missed. Get someone else to read your document also. The more people that review your work, the more likely it will be that the errors will be caught.

This will make our job a lot easier, and therefore increase your chances of getting your work published.

[h3]Photographs and Diagrams[/h3]
Not all articles will include images, but those that do must follow the guidelines given below:

Images must be in focus and must clearly illustrate the subject matter. Blurred photographs, or photographs that show insufficient details will be rejected. Images that are too dark or too light will also be rejected.
Images must be uploaded using .JPG, .PNG or .GIF formats. Other formats will not be accepted.

All images must be of a reasonable size to illustrate the subject matter (i.e, no postage stamp sized thumbnails), and must not exceed 600 pixels in either dimension.

[h3]Articles Rejected or Returned for Rework[/h3]
Don’t feel upset if your article has been rejected; there may be any number of reasons for this. The proofreader will provide some feedback to help you to improve the article for resubmission at a later date.

Articles may be returned to the author for rework. The reasons for this are many and could include; a lack of detail, poor photography, excessive spelling/grammatical errors, or whatever. When this happens, the proofreader has decided that the article has merit and just needs a bit more work to be of the acceptable standard. Do not resubmit the article using the submission form. Send the reworked article directly to the proofreader.

[h2]Specific Article Type Requirements[/h2]
Each type of article has different requirements and therefore needs to be explained separately. Refer to the specific document for the different article type.

Painting GuidesScenariosSculpting and Conversion GuidesHouse RulesTerrain Guides and DioramasStrategy and Tactics GuidesGaming AidsBattle Reports[hr]
[h2]Painting Guides[/h2]
The guide must include the following item list:

Paints Used

List each of the paints you used with the appropriate GW name (e.g. Bubonic Brown), in the order they were first required, one paint colour per line. For example:

[h3]Introduction[/h3]
Include a paragraph or two to explain the nature of the project and perhaps your reasons for creating it. If you have significantly deviated from the colour schemes portrayed in any of Games Workshop’s publications or from the motion pictures, here is the place to explain why. Include a photograph of the finished project to show the reader what to expect as an end result.

[h3]Step By Step Description[/h3]
Split your guide up into a series of simple steps, each one describing a single task or concept. The text should be easy to understand and clearly explain the process you followed (or are recommending) to achieve these results. Each step should include at least one photograph illustrating the concepts and should include close-ups for the fine details.

The steps are to be numbered from 1 through to whatever and may include a sub-heading to help describe the step better. For example:

Step 1 - Preparing the Figure

[h3]Conclusion [/h3]
It is desirable (but not strictly necessary) to have a small gallery of photographs at the end of the article showing the finished model from various angles.

[hr]
[h2]Scenarios[/h2]
Scenarios must have a reasonable background and be detailing an event that occurred in (or was a lead up to events in) the books or the films, or "what-if" situations where players can explore alternative storylines etc. They must depict situations that fit into the world of Middle-earth.

Scenarios that are merely points matches or excuses to field large armies will not be accepted, neither will scenarios that mix units from different armies in an unrealistic manner.

They must be playtested and the evidence of that testing submitted with the article. If no supporting playtesting notes are provided, then the article will not be accepted. The reason for this is simple. We do not have the time or resources to playtest a scenario for you, so you must do it yourself (or make sure it gets done). A scenario must be well balanced, with both sides having a reasonable chance at winning; playtesting is the only way to ensure this.

The scenario must be prepared in the following format:

[h3]Description[/h3]
A paragraph or two is required to set the scene and describe the background for the scenario.

[h3]Participants[/h3]
List the participants together with their wargear here. The general approach is to list the Good side first, then Evil.

[h3]Layout[/h3]
Describe the area in which the battle takes place. The size of the gaming board is required, as is a description of any distinguishing features, such as areas of difficult terrain, buildings, hills etc.

A scenario map is essential, but doesn’t have to be drawn to a magnificent standard. Don’t panic! Just a sketch of the area is all that is required; we can draw it up for you to the appropriate standards.

[h3]Starting Positions[/h3]
Describe the starting positions for the various models and any special set up rules.

[h3]Objectives[/h3]
Explain how the scenario can be won by each side. The best scenarios generally have a major victory condition, a minor victory condition and the condition for a draw.

[h3]Special Rules[/h3]
Explain any scenario specific rules in this section. These can include new troop types, overrides to standard rules (such as Moria Goblins scaling castle walls), and new rules that are not part of the core game rules.

[h3]Playtesting Results[/h3]
We are basically looking for a mini-battle report here, where the outcome of the game is shown (but not a blow-by-blow description) and a brief analysis of the strengths and weaknesses of the characters and troops in the game. Play the game several times, swapping forces with your opponent and see if one side wins consistently. Try alternate approaches and strategies in the games. Each of these attempts should be documented, and any adjustments made to the forces or layout should be noted as well.

In order to balance a scenario, you might try adding or removing troops, moving the terrain around into more strategic positions, changing the starting positions of certain troops, or staggering the arrival of reinforcements. There are many different ways to do it.

[hr]
[h2]Sculpting and Conversion Guides[/h2]
The guide must include the following headings:

Tools UsedMaterials UsedPaints Used

List the tools you used and all the materials for the project. It is desirable to list them materials first, then tools, each in the order in which they were required (where possible). List each item on its own line. Where an unusual item is listed then include an explanatory paragraph after the list.

List each of the paints you used with the appropriate GW name (e.g. Bubonic Brown), in the order they were first required, one paint colour per line.

[h3]Introduction[/h3]
Include a paragraph or two to explain the nature of the project and perhaps your reasons for creating it. It may include a brief history of the person/creature if it is a model of a specific character in Middle-earth. Include a photograph of the finished project to show the reader what to expect as an end result.

[h3]Step By Step Description[/h3]
Split your guide up into a series of simple steps, each one describing a single task or concept. The text should be easy to understand and clearly explain the process you followed (or are recommending) to achieve these results. Each step should include at least one photograph or diagram illustrating the concepts.

The steps are to be numbered from 1 through to whatever and may include a sub-heading to help describe the step better. For example:

Step 1 – Making the Armature

[h3]Conclusion[/h3]
It is desirable (but not strictly necessary) to have a small gallery of photographs at the end of the article showing the project from various angles.

[hr]
[h2]House Rules[/h2]
Modifications to existing official profiles will not be accepted without exceptional reasons ("cos they suck" isn't good enough, sorry).

House rule submissions must be supported with playtesting documentation. New characters or troop types must be balanced for their points and the only way to ensure this is by playtesting. We cannot do it for you (we have neither the time nor the resources to do this), so you must ensure that your characters are well balanced. Articles with no playtesting documentation will be rejected.

Only characters suited for Middle-earth will be accepted (sorry, no Matrix, Star Wars, or Harry Potter characters, etc). When considering a new character or troop type, please keep the stats reasonable and in keeping with other existing characters of the same type: no Balrog-strength Goblin captains please.

House Rule articles must follow the guidelines below:

[h3]Profile[/h3]
Character/Troop Type Name
Points Value
Profile including Might, Will and Fate

[h3]Description[/h3]
Include a brief history of your character to enable him/her/it to fit into the world of Middle-earth.

[h3]Wargear[/h3]
List the items permitted for your character and their points value.

[h3]Playtesting Notes[/h3]
This is a mandatory requirement. Simply put - no playtesting results means your work won't get published.

We are basically looking for a mini-battle report here, where the reults of using your new character in a game is shown (but not a blow-by-blow description) and a brief analysis of the strengths and weaknesses of that characters or troop types. Play several games using a number of different situations, swapping forces with your opponent and see how well the new troop performs in each battle. Each of these attempts should be documented, and any adjustments made to the character’s profile or abilities should be noted as well.

[hr]
[h2]Terrain Guides and Dioramas[/h2]
Terrain Guides and Dioramas follow the same basic structure and so are grouped here together.

The guide must include the following item lists:

Tools UsedMaterials UsedPaints Used

List the tools you used and all the materials for the project. It is desirable to list them materials first, then tools, each in the order in which they were required (where possible). List each item on its own line. Where an unusual item is listed then include an explanatory paragraph after the list.

List each of the paints you used with the appropriate GW name (e.g. Bubonic Brown), in the order they were first required, one paint colour per line.

[h3]Introduction[/h3]
Include a paragraph or two to explain the nature of the project and perhaps your reasons for creating it. It may include a brief history of the site if it is a model of a specific place in Middle-earth. Include a photograph of the finished project to show the reader what to expect as an end result.

[h3]Step By Step Description[/h3]
Split your guide up into a series of simple steps, each one describing a single task or concept. The text should be easy to understand and clearly explain the process you followed (or are recommending) to achieve these results. Each step should include at least one photograph or diagram illustrating the concepts.

The steps are to be numbered from 1 through to whatever and may include a sub-heading to help describe the step better. For example:

Step 1 – Building the Basic Framework

[h3]Plans - optional[/h3]
Any plans included with the article must be accurate, drawn to scale and show appropriate measurements. If the plans are not drawn at 1:1 scale, then the appropriate scale must be shown on the diagram.

[h3]Conclusion[/h3]
It is desirable (but not strictly necessary) to have a small gallery of photographs at the end of the article showing the project from various angles.

[hr]
[h2]Strategy and Tactics Guides[/h2]
Your Tactics Guide should be a detailed study of the topic and not just a list of strengths and weaknesses. The study should focus on one or more aspects of the game and explore how to use that to advantage during a battle. There should be examples included that illustrate the point.

If your tactic guide takes up only a few lines, it would be better suited as a post in the Tactics Forum. This section of the article library is aiming to provide a definitve guide to battlefield tactics and as such we are looking for only the highest quality articles.

Diagrams that show how the tactic is used in battle are highly recommended also.

[hr]
[h2]Gaming Aids[/h2]
This category is fairly open and there are no specific guidelines about what to include, except perhaps a photograph of the gaming aid in use and an explanation of how they are to be used or prepared.

[hr]
[h2]Battle Reports[/h2]
These types of articles are basically stories about what happened during battles, and therefore they must be interesting and entertaining. Articles that are basically a list of the dice rolls for each turn will be rejected.

The article must include the following headings:

[h3]Description[/h3]
A paragraph or two is required to set the scene and describe the background for the scenario. Include a brief introduction to the players also.

[h3]Participants[/h3]
List the scenario participants here. The general approach is to list the Good side first, then Evil. It is not necessary to list their wargear, unless it is of special interest or relevance to the game

[h3]Layout[/h3]
Describe the area in which the battle takes place. The size of the gaming board is required, as is a description of any distinguishing features, such as areas of difficult terrain, buildings, hills etc.

[h3]Objectives[/h3]
Describe the victory conditions for each side.

[h3]The Game[/h3]
This is basically a description of the game as it was played. Explain the actions taken during each turn, who won priority, what tactics they employed, their moves, the success or failure of their attackes etc. Don’t list each dice roll and model killed, unless something very unusual was achieved, (such as 10 sixes in a row or whatever).

Photographs of various stages of the battle are highly recommended.

Diagrams of each turn are also highly recommended. They should provide a plan view of the battlefield and show the movements of the troops and where combats or missle fire kills occurred.

A touch of drama and comedy will help to make the article entertaining also, as will adding a personalised touch to the results of dice rolls. For example: instead of saying

“Evil won priority and so attacked first. The Uruk captain got a 6 and won his combat again the Rohan captain on the causeway, and then rolled a five killing him. The turn ended and Good won priority for the next turn.”

Try this:

“The giant Uruk finally crashed through the shield wall and slew the brave Captain Theobald at the foot of the causeway. A great cheer arose from the ranks of the Isengarders, but it was cut short as the men of Rohan gathered their strength and pressed the attack once more.”

[h3]Outcomes[/h3]
The results of the battle should be described here together with a brief analysis of the reasons for the win or loss.

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum