Redoing of* the Gameday Rules
Alright, so as I'm sure many other people have noticed and have heard/voiced their opinion about, the same maps seem to get into the gamedays before anyone else can. I have been talked to about this already a couple times (and it's only my first time hosting a gameday) and I believe the arguement does have some merit. I figured I'd post this now seeing as we have new people running gamedays currently, so why not a new, updated, shiney set of rules that make everyone happy.
Here are the current rules:
With the current rules, they are there more-or-less as rules of gameplay, along with the "No reserveing spots" rule.
I'm not going to suggest anything because I'm not sure what the best way to go about doing this is, but I would like a discussion on if they rules need changeing and if they do, what should be changed. I will say that I think that there should be some consideration toward low alpha maps a1/a2 and possibly b1 maps, that would allow them to have more push into getting into a gameday because they are "new"
Sorry for the wall of text, and if you did, thanks for reading. I'm hoping to keep this to a non-flame-war and to something that is actually productive.
Alright, so as I'm sure many other people have noticed and have heard/voiced their opinion about, the same maps seem to get into the gamedays before anyone else can. I have been talked to about this already a couple times (and it's only my first time hosting a gameday) and I believe the arguement does have some merit. I figured I'd post this now seeing as we have new people running gamedays currently, so why not a new, updated, shiney set of rules that make everyone happy.
Here are the current rules:
Rules
• The map must be playable. This means fully functional objective system, proper spawns, not fullbright, etc.
__The purpose of this testing is to help authors refine their designs, not catch newbie bugs.
• Filename MUST be versioned. (ctf_example_a1.bsp, NOT ctf_example.bsp)
__Do not rename a bsp after compile. The vmf must be renamed before compile.
• Filename must be all lowercase. (ctf_example_a1.bsp, NOT CTF_Example_A1.bsp)
__Our Linux servers don't work with uppercase names.
• Map must be IN DEVELOPMENT, finished maps do not require testing.
• Map may NOT use a point_servercommand to alter any variables.
• Map must be designed for normal play.
__This means no melee, class restricted, too small for 24 players, or otherwise gimmicky maps.
• You may NOT reserve a submission without a download.
• Non-compliance with rules will result in rejection of the submission.
• If an author has more than one map they want tested, they must be submitted to separate days.
With the current rules, they are there more-or-less as rules of gameplay, along with the "No reserveing spots" rule.
I'm not going to suggest anything because I'm not sure what the best way to go about doing this is, but I would like a discussion on if they rules need changeing and if they do, what should be changed. I will say that I think that there should be some consideration toward low alpha maps a1/a2 and possibly b1 maps, that would allow them to have more push into getting into a gameday because they are "new"
Sorry for the wall of text, and if you did, thanks for reading. I'm hoping to keep this to a non-flame-war and to something that is actually productive.
Last edited by a moderator: