EPT
+ Show Spoiler +
SC2 Strategy Forum Guidelines
Release is upon us! For now the rules from the beta are still in effect.
Rule No 1
Everything you say must be supported by evidence
This game is still fairly new and evolving all the time. No one has a definite answer for every strategy related question for SC2. Thus it is extremely important that you back up everything with sound reasoning, a replay, a VOD, anything that supports the point you are making. Your word is not enough - you know just as little about the game as everybody else.
That said, there are already people much more qualified to talk about strategy than others. You will see their posts in this forum highlighted with a darkish blue background. Statements by these individuals will be weighted differently than had they be posted by complete unknowns. Thus, the less reputation you have the more you need to back up your claims as described further up (Note however that this does not excuse outrageous claims by a good player – in the end everything will need proof).
Also keep in mind:
- This is no place for balance discussion.
- B.net league placements aren't that relevant. Your diamond top spot doesn't mean anything.
Categorization
Always put the right tag ([H][D][G][Q]) in your thread title
Tagging your threads is very important. The difference between [D] Bisu Build and [G] Bisu Build is worlds apart. Please use thread categorization correctly as described below. Not only will the expectation to your thread depend on it but of course you will get feedback faster also.
Categorizing thread makes it easy to find threads later using the search. You can search for “[H] Bisu Build ” and there you are.
[L] Low Level
You know you aren't a star player and you need help with fundamentals
Use the [L] tag if you are still learning the basics of the game and if you have fundamental problems / questions. There is no clear cut line where "Low Level" starts - it's up to you. Do you feel you need input from a top tier player, or are you still working on mechanics? Judge your own skill.
Please note that making a [L] thread does not exclude you from obeying the rest of these guidelines or allows you to ask stupid questions.
[H] Help threads.
Post a replay, give your own analysis, get help!
The classic “Why did I lose this game?”. For these threads it is absolutely required that you post a replay. No exceptions. Nobody is going to be able to help you if you won’t post a replay.
Additionally, first put some thought into what happened in the game, and include your own analysis into the thread. It might be wrong, but try your best. It doesn’t have to be long, a few point form lines is enough to give people a starting point to give you advice. Your thread won’t last if you won’t put any effort in it.
If you have specific questions, ask them along with your analysis. It’s always easier to reply if we know what exactly you need help with.
[Q] Question threads
Ask for help with or against a specific strategy
In a [Q] thread you may ask about a specific, situational strategy, whether that is executing it yourself of playing against it. It is very important that you keep these threads specific. A general "How to FE against Zerg?" is not acceptable. This is the most important distinction from the [H] threads. As with [H] thread you must post one or several replays.
Post some analysis of the problem, and what you have tried so far. This not only avoids redundant advice but also shows people you have put some effort into this yourself.
As with the [H] threads, it makes it a lot easier to help you if you ask a couple of specific questions regarding the strategy you are unsure about.
Feedback on [H] and [Q] threads
Be respectful and accept the advice you get
Be respectful of the opinions people give you – you came here looking for help. If you disagree with a reply, cite examples or give some sort of analysis supporting why you disagree.
Experienced players should be direct and give advice that is generally accepted as standard. Their advice should be as specific as possible, as open-ended advice (“play faster”) isn’t very helpful.
Only reply to a help thread if you are an experienced SC2 player, and if you have watched the replay. Otherwise, these threads are simply no place for you to post.
[D] Discussion threads
Be clear about the topic and the feedback your are hoping for
This is the most open form of thread. Use a Discussion thread if you are not certain about some game mechanic and you want to get the feedback from other players. This can be about strategy and tactics, the role and viability of certain units, rock paper scissor counters, etc. The building blocks of what becomes sound SC2 strategy.
While the thread is less formal, please be clear and concise on the topic you want to discuss about, and open with your own opinion. Don’t make the topic too broad.
This is the perfect way to post a strategy you came up with that is not quite ready to be turned into a guide (See below). Post your strategy and point out the areas where you are not sure about it’s validity and ask for feedback.
Feedback on discussion threads
Be respectful and remember Rule No 1
You wanted to generate discussion, so please don’t brush off suggestions you don’t agree with. Post your counter argument and back it up (Rule No 1). The same goes for people replying to such threads.
Threads like these are a welcome place for people less experienced to ask for opinions, make suggestions and engage in discussion.
[G] Guides
Know what you are talking about
Guides are complete, detailed, and comprehensive advice for a specific strategy or tactic that can be generally executed and is not situational. Guides are held up against the highest standards of quality in this forum. They are the most valuable resource for the average player. Writing a good guide may yield you wide appreciation and e-fame, but comes with a lot of work and responsibility.
Naturally, do not write a guide about something you are not experienced with. If you have come up with a new build and you just won 6 games in a row with it, do not start writing a guide. Play your build more, tweak it, find out it’s weaknesses and follow-ups and branches. A good rule of thumb is to play a strategy until you lose a couple of times with it against different counters, then modify it until you win most games again, then start to think about writing a guide.
A good guide does not necessarily have to be written about a build in a specific matchup, although that is most common. If you have found a new, incredibly effective way to micro Helions you can write a generic Helion micro guide.
Most of the time guides will introduce builds in specific matchups though. Look through our legacy Strategy forum to get an idea on how to write good matchup build guides. There is no perfect recipe, but a few things to take care of: State the goal of the build, strengths, weaknesses, possible follow-up, and adaptations to what the opponent does. Dedicate a chapter to scouting and how to react to what you see within your build.
To give you an idea of the quality we are eventually aiming for have a look at this incredible SC:BW guide:
http://www.teamliquid.net/forum/viewmessage.php?topic_id=89265
Feedback on Guides
Be respectful and remember Rule No 1
A guide is always evolving as the game is being more and more understood and as people find counter strategies. As the author it is your job to keep the guide up to date. If other players find weaknesses or suggest changes to the build, it is your job to alter it accordingly. If you disagree, fall back to Rule No 1: Post a replay or some other form of proof that the criticism isn’t valid.
If you think you found a hole in a posted guide, describe your findings and why you think the guide is weak there. It makes your point incredibly more believable if you post a replay along. Also don't be lazy: Make a suggestion on how to adapt the guide to address your criticism. This is how the best guides that stand the test of time are created.
Contribute
Contribute to this forum! Give good and meaningful advice when you can. Write good introductory OPs to spawn discussion. Even when your thread does not follow these rules here at all, if it's still a well written OP it will stay. We will always reward effort put into our forums.
This site has been the number one resource for Starcraft strategy for one reason: Because it's base of enthusiastic players put an indescribable amount of combined effort into it. Be a part of the best source for Starcraft2 Strategy from the beginning!
Release is upon us! For now the rules from the beta are still in effect.
Rule No 1
Everything you say must be supported by evidence
This game is still fairly new and evolving all the time. No one has a definite answer for every strategy related question for SC2. Thus it is extremely important that you back up everything with sound reasoning, a replay, a VOD, anything that supports the point you are making. Your word is not enough - you know just as little about the game as everybody else.
That said, there are already people much more qualified to talk about strategy than others. You will see their posts in this forum highlighted with a darkish blue background. Statements by these individuals will be weighted differently than had they be posted by complete unknowns. Thus, the less reputation you have the more you need to back up your claims as described further up (Note however that this does not excuse outrageous claims by a good player – in the end everything will need proof).
Also keep in mind:
- This is no place for balance discussion.
- B.net league placements aren't that relevant. Your diamond top spot doesn't mean anything.
Categorization
Always put the right tag ([H][D][G][Q]) in your thread title
Tagging your threads is very important. The difference between [D] Bisu Build and [G] Bisu Build is worlds apart. Please use thread categorization correctly as described below. Not only will the expectation to your thread depend on it but of course you will get feedback faster also.
Categorizing thread makes it easy to find threads later using the search. You can search for “[H] Bisu Build ” and there you are.
[L] Low Level
You know you aren't a star player and you need help with fundamentals
Use the [L] tag if you are still learning the basics of the game and if you have fundamental problems / questions. There is no clear cut line where "Low Level" starts - it's up to you. Do you feel you need input from a top tier player, or are you still working on mechanics? Judge your own skill.
Please note that making a [L] thread does not exclude you from obeying the rest of these guidelines or allows you to ask stupid questions.
[H] Help threads.
Post a replay, give your own analysis, get help!
The classic “Why did I lose this game?”. For these threads it is absolutely required that you post a replay. No exceptions. Nobody is going to be able to help you if you won’t post a replay.
Additionally, first put some thought into what happened in the game, and include your own analysis into the thread. It might be wrong, but try your best. It doesn’t have to be long, a few point form lines is enough to give people a starting point to give you advice. Your thread won’t last if you won’t put any effort in it.
If you have specific questions, ask them along with your analysis. It’s always easier to reply if we know what exactly you need help with.
[Q] Question threads
Ask for help with or against a specific strategy
In a [Q] thread you may ask about a specific, situational strategy, whether that is executing it yourself of playing against it. It is very important that you keep these threads specific. A general "How to FE against Zerg?" is not acceptable. This is the most important distinction from the [H] threads. As with [H] thread you must post one or several replays.
Post some analysis of the problem, and what you have tried so far. This not only avoids redundant advice but also shows people you have put some effort into this yourself.
As with the [H] threads, it makes it a lot easier to help you if you ask a couple of specific questions regarding the strategy you are unsure about.
Feedback on [H] and [Q] threads
Be respectful and accept the advice you get
Be respectful of the opinions people give you – you came here looking for help. If you disagree with a reply, cite examples or give some sort of analysis supporting why you disagree.
Experienced players should be direct and give advice that is generally accepted as standard. Their advice should be as specific as possible, as open-ended advice (“play faster”) isn’t very helpful.
Only reply to a help thread if you are an experienced SC2 player, and if you have watched the replay. Otherwise, these threads are simply no place for you to post.
[D] Discussion threads
Be clear about the topic and the feedback your are hoping for
This is the most open form of thread. Use a Discussion thread if you are not certain about some game mechanic and you want to get the feedback from other players. This can be about strategy and tactics, the role and viability of certain units, rock paper scissor counters, etc. The building blocks of what becomes sound SC2 strategy.
While the thread is less formal, please be clear and concise on the topic you want to discuss about, and open with your own opinion. Don’t make the topic too broad.
This is the perfect way to post a strategy you came up with that is not quite ready to be turned into a guide (See below). Post your strategy and point out the areas where you are not sure about it’s validity and ask for feedback.
Feedback on discussion threads
Be respectful and remember Rule No 1
You wanted to generate discussion, so please don’t brush off suggestions you don’t agree with. Post your counter argument and back it up (Rule No 1). The same goes for people replying to such threads.
Threads like these are a welcome place for people less experienced to ask for opinions, make suggestions and engage in discussion.
[G] Guides
Know what you are talking about
Guides are complete, detailed, and comprehensive advice for a specific strategy or tactic that can be generally executed and is not situational. Guides are held up against the highest standards of quality in this forum. They are the most valuable resource for the average player. Writing a good guide may yield you wide appreciation and e-fame, but comes with a lot of work and responsibility.
Naturally, do not write a guide about something you are not experienced with. If you have come up with a new build and you just won 6 games in a row with it, do not start writing a guide. Play your build more, tweak it, find out it’s weaknesses and follow-ups and branches. A good rule of thumb is to play a strategy until you lose a couple of times with it against different counters, then modify it until you win most games again, then start to think about writing a guide.
A good guide does not necessarily have to be written about a build in a specific matchup, although that is most common. If you have found a new, incredibly effective way to micro Helions you can write a generic Helion micro guide.
Most of the time guides will introduce builds in specific matchups though. Look through our legacy Strategy forum to get an idea on how to write good matchup build guides. There is no perfect recipe, but a few things to take care of: State the goal of the build, strengths, weaknesses, possible follow-up, and adaptations to what the opponent does. Dedicate a chapter to scouting and how to react to what you see within your build.
To give you an idea of the quality we are eventually aiming for have a look at this incredible SC:BW guide:
http://www.teamliquid.net/forum/viewmessage.php?topic_id=89265
Feedback on Guides
Be respectful and remember Rule No 1
A guide is always evolving as the game is being more and more understood and as people find counter strategies. As the author it is your job to keep the guide up to date. If other players find weaknesses or suggest changes to the build, it is your job to alter it accordingly. If you disagree, fall back to Rule No 1: Post a replay or some other form of proof that the criticism isn’t valid.
If you think you found a hole in a posted guide, describe your findings and why you think the guide is weak there. It makes your point incredibly more believable if you post a replay along. Also don't be lazy: Make a suggestion on how to adapt the guide to address your criticism. This is how the best guides that stand the test of time are created.
Contribute
Contribute to this forum! Give good and meaningful advice when you can. Write good introductory OPs to spawn discussion. Even when your thread does not follow these rules here at all, if it's still a well written OP it will stay. We will always reward effort put into our forums.
This site has been the number one resource for Starcraft strategy for one reason: Because it's base of enthusiastic players put an indescribable amount of combined effort into it. Be a part of the best source for Starcraft2 Strategy from the beginning!
(I'm both a nobody, and I don't have beta))
