Basing this off observations made about suggestions that have been denied in the past that were of particularly dreadful quality.
No. 1
Fill the format out (aka actually put in your steam ID you lazy schmuck)
Not filling out the format properly is an instant-denial regardless of content, so if you spent an hour or so pouring the most amount of critical thinking into a suggestion than you have anything else in your entire life, regardless if you don't fill the format out properly then Burn or whoever's judging the suggestion is just gonna insta-deny it.
No. 2
When suggesting the implentation of an addon, consider the file size.
If you're making, for example, a suggestion to add playermodels for a certain class, ensure that the file size justifies it's inclusion. In the past playermodel suggestions have been denied due to the large file size, especially if it only benefitted one class.
So avoid making such suggestions like adding a 160 mb playermodel pack just for the EOWs.
No. 3
Avoid trying to justify your suggestions with one of these reasons (god help you if you use all of them).
It's the lore
Because (INSERT CLASS HERE) keeps kicking our ass!
Because we voted on it
I'll attack these individually.
It's the lore
The main mistake people make when using this argument is that they more often than not confuse HL2 lore with HL2RP lore. To elaborate, the actual lore of Half Life is very open-ended and doesn't provide a great level of detail on the inner-workings of the world, almost everything in this server is based off lore created by the HL2RP community, this includes things like the rank structures, protocols, divisions and pulse weaponry outside of the AR2. Infact, even the lore created by the HL2RP community is different from server to server as there is no real consensus on all the details. This results in so many different headcanons that have never been confirmed by the HL2 writers/dev team.
While this lore does provide a good foundation for many RP aspects of the server, it doesn't act as gospel, nor does it override issues of higher priority such as balancing.
This reasoning has been commonly used in the past in an attempt to justify buffing Combine classes, typically in the form of "BECAUSE WE'RE SUPPOSED TO BE THIS STRONG", and has yet to be accepted as valid justification.
Because (INSERT CLASS HERE) keeps kicking our ass!
Before you finish typing this sentence out, consider the following:
Are you sure that it's some inherent flaw within your class, rather than the class you're calling out needing a nerf?
That's all that needs to be said really.
Because we voted on it
Popular opinion =/= correct.
Be very careful on where you get your votes from, if it's just within your division/sub-division then of course people are going to vote for a suggestion if it's asking for a buff.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Alright that's all i fucking got, if you got any more ideas feel free to add it, I'm not your dad/mum.
Before anyone asks why I made this, I was bored.
Basing this off observations made about suggestions that have been denied in the past that were of particularly dreadful quality.
No. 1
Fill the format out (aka actually put in your steam ID you lazy schmuck)
Not filling out the format properly is an instant-denial regardless of content, so if you spent an hour or so pouring the most amount of critical thinking into a suggestion than you have anything else in your entire life, regardless if you don't fill the format out properly then Burn or whoever's judging the suggestion is just gonna insta-deny it.
No. 2
When suggesting the implentation of an addon, consider the file size.
If you're making, for example, a suggestion to add playermodels for a certain class, ensure that the file size justifies it's inclusion. In the past playermodel suggestions have been denied due to the large file size, especially if it only benefitted one class.
So avoid making such suggestions like adding a 160 mb playermodel pack just for the EOWs.
No. 3
Avoid trying to justify your suggestions with one of these reasons (god help you if you use all of them).
- It's the lore
- Because (INSERT CLASS HERE) keeps kicking our ass!
- Because we voted on it
I'll attack these individually.It's the lore
The main mistake people make when using this argument is that they more often than not confuse HL2 lore with HL2RP lore. To elaborate, the actual lore of Half Life is very open-ended and doesn't provide a great level of detail on the inner-workings of the world, almost everything in this server is based off lore created by the HL2RP community, this includes things like the rank structures, protocols, divisions and pulse weaponry outside of the AR2. Infact, even the lore created by the HL2RP community is different from server to server as there is no real consensus on all the details. This results in so many different headcanons that have never been confirmed by the HL2 writers/dev team.
While this lore does provide a good foundation for many RP aspects of the server, it doesn't act as gospel, nor does it override issues of higher priority such as balancing.
This reasoning has been commonly used in the past in an attempt to justify buffing Combine classes, typically in the form of "BECAUSE WE'RE SUPPOSED TO BE THIS STRONG", and has yet to be accepted as valid justification.
Because (INSERT CLASS HERE) keeps kicking our ass!
Before you finish typing this sentence out, consider the following:
Are you sure that it's some inherent flaw within your class, rather than the class you're calling out needing a nerf?
That's all that needs to be said really.
Because we voted on it
Popular opinion =/= correct.
Be very careful on where you get your votes from, if it's just within your division/sub-division then of course people are going to vote for a suggestion if it's asking for a buff.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Alright that's all i fucking got, if you got any more ideas feel free to add it, I'm not your dad/mum.