*

Account

Welcome, Guest. Please login or register.
Did you miss your activation email?
July 04, 2020, 03:30:05 am

Login with username, password and session length

Resources

Recent posts

[Today at 12:46:11 am]

[Yesterday at 10:16:51 pm]

[Yesterday at 10:52:21 am]

[June 29, 2020, 08:00:08 pm]

[June 29, 2020, 01:24:53 am]

[June 28, 2020, 03:03:14 am]

[June 24, 2020, 05:24:11 am]

[June 22, 2020, 07:38:26 pm]

[June 19, 2020, 05:54:49 pm]

[June 14, 2020, 12:14:37 pm]
Pages: [1]   Go Down
  Print  
Author Topic: How to avoid having your thread locked in the balance forum  (Read 2026 times)
0 Members and 1 Guest are viewing this topic.
Smokaz Offline
Honoured Member
*
Posts: 11452



« on: July 03, 2014, 08:15:22 pm »

What a monkey can understand given time and training:

- Don't flame other posters
- Don't derail the thread with offtopic
- Don't hate on coders/devs
- Don't post retarded pictures

Classic pathological EIRR balance forum flamebait that you shouldn't do:

- Don't discredit other posters because they are not "good enough" as a player, point out the flaw in their play, not the player. This leads to flaming and the plummeting of a thread.

- How much people play is not up for you or me to decide whether or not qualifies to having a opinion.

This is a small community and every man, woman and deformed hobgoblin counts.

- "You only play noobs/stacks", no no no no no.

If you disagree, then make the rules more lenient by applying the mod leadership for the evil nazi moderation to stop.  Don't smoke weed while you are working for legalization. Until somebody opposes these to me pretty constructive rules, respect them.

« Last Edit: July 03, 2014, 09:00:32 pm by Smokaz » Logged

SlippedHerTheBigOne: big penis puma
SlippedHerTheBigOne: and i have no repairkits
SlippedHerTheBigOne: ( ͡ ͜ʖ ͡)
Pages: [1]   Go Up
  Print  
 
Jump to:  

TinyPortal v1.0 beta 4 © Bloc
Powered by MySQL Powered by PHP Powered by SMF 1.1.9 | SMF © 2006-2009, Simple Machines LLC
Valid XHTML 1.0! Valid CSS!
Page created in 0.381 seconds with 35 queries.