1. We have moved to a new forum system. All your posts and data should have transferred over. Welcome, to the new Serebii Forums. Details here
    Dismiss Notice
  2. Be sure to join the discussion on our discord at: Discord.gg/serebii
    Dismiss Notice
  3. If you're still waiting for the e-mail, be sure to check your junk/spam e-mail folders
    Dismiss Notice

Welcome to the Warstory section!

Discussion in 'Warstories' started by Reno, Jan 23, 2010.

Thread Status:
Not open for further replies.
  1. Reno

    Reno so adorable...

    This section is for any logs of awesome battles. There are obviously rules to this section, but they aren't hard and are pretty fair. This section is moderated. This means that no threads get through without a mod giving them the all clear. Unless you want to waste your time, follow these rules.

    1. Don't just post a log. Make it a warstory. Don't post something you don't think you'd like to read.

    2. Don't just post a clean sweep showing how bad someone else was. It should be a close match, an exciting game, not a 'LOL THIS KID USES KAKUNA WHAT AN IDIOT'.

    3. Not really a rule, more of a tip. You don't have to be the winner to post a warstory. If the battle was close but you still lost, it doesn't matter, it'll make a good warstory.

    4. Make sure it is easy to understand.
    4a. Don't use nicknames, as they confuse the reader and make it harder to read.
    4b. Using a colour code makes it clear when skimreading what happens in the battle. Red for your opponents moves, blue for your moves. Stuff like that.
    4c. At the start of your warstory, have your team and your opponent's team shown in the form of sprites. This makes the teams you both used clear to the reader.

    4c example.
    Reno's Team-[​IMG][​IMG][​IMG][​IMG][​IMG][​IMG]
    Misaki's Team-[​IMG][​IMG][​IMG][​IMG][​IMG][​IMG]

    5. An ending summary of how you felt the battle went is great. A Pros and Cons of the battle.

    More rules will be added as this section gets bigger.
     
Thread Status:
Not open for further replies.

Share This Page