You need to more specific than "What do you guys think?"
Stuff like:
"What do you think of the build?"
"Is the guide well written?"
And the like.
Stuff like:
"What do you think of the build?"
"Is the guide well written?"
And the like.
Well let me explain you how it works.
Comments under the guide are a place for casual "let me know what do you think of it" type of comments. Forums are more strict.
You cant advert the guide plainly, You have to SPECIFY a questions.
"what do you think or how do you feel about it" are not valid backups for linking a guide.
If the guide is small you can only paste the issue that you are concerned about (for example itemisation) if the guide is too big to be included in the topic itself you might be able to provide the link if it is realy nessesary.
A specific questions is a specific question. Rule of common sense is needed here. You are unsure about which runes to use or is that or that item better, or this tactic work bla bla bla, srsly even those questions shouldnt be asked by a person that just wrote a "guide". But i would let it go...
Imho a person that write a guide does not need all that info or doesnt need to ask anyone about anything, it should be him/her that answers those questions. But it seems i am alone in that statement.
For me the only rule for posting a link should be an issue with the guide (bug, glitch and so on)
We let some pass but we try to keep it as strict as possible. Imagine YohahN if any user of MOBAFire would be free to create a topic and spam it on the forums... imagine the spam.
You need views? you need votes? well if you are not getting them, it might be a sign that your guide is not good enaugh.
Usualy the good guides pop up pretty fast. Be active, be active on the forums as well. Comment on other ppl builds and stuff.
Comments under the guide are a place for casual "let me know what do you think of it" type of comments. Forums are more strict.
You cant advert the guide plainly, You have to SPECIFY a questions.
"what do you think or how do you feel about it" are not valid backups for linking a guide.
If the guide is small you can only paste the issue that you are concerned about (for example itemisation) if the guide is too big to be included in the topic itself you might be able to provide the link if it is realy nessesary.
A specific questions is a specific question. Rule of common sense is needed here. You are unsure about which runes to use or is that or that item better, or this tactic work bla bla bla, srsly even those questions shouldnt be asked by a person that just wrote a "guide". But i would let it go...
Imho a person that write a guide does not need all that info or doesnt need to ask anyone about anything, it should be him/her that answers those questions. But it seems i am alone in that statement.
For me the only rule for posting a link should be an issue with the guide (bug, glitch and so on)
We let some pass but we try to keep it as strict as possible. Imagine YohahN if any user of MOBAFire would be free to create a topic and spam it on the forums... imagine the spam.
You need views? you need votes? well if you are not getting them, it might be a sign that your guide is not good enaugh.
Usualy the good guides pop up pretty fast. Be active, be active on the forums as well. Comment on other ppl builds and stuff.
Also a great way to get some publicity without creating advert threads is to include a link in your signature. When people see you post (hopefully helpful or funny things), they can choose to check out your guide.
If you have a specific question about your guide, you shouldn't need to post the link. If you just want more feedback in general, then put the link in your signature and make yourself known on the forums. There's really no other way to go.
If you have a specific question about your guide, you shouldn't need to post the link. If you just want more feedback in general, then put the link in your signature and make yourself known on the forums. There's really no other way to go.
Thanks to The_Nameless_Bard for the sig!
You need to log in before commenting.
<Member>