Beta map rules for ~[FGS]0-Augs Server~
Posted: 16 Jun 2012, 20:22
The three rules will apply to beta maps thus;
1. "Any beta map that has not been updated for 1 month will be taken off the map rotation and placed into the bi-monthly map vote"
2. "Each mapper is allowed to have a limit of no more then 2 maps in beta stage at any one time involved in the 0-augs hosting or bi-monthly vote, those with 3 or more beta maps will have their oldest beta removed from hosting/bi-monthly map vote"
3. Beta maps should be named with the extension _beta1, _beta2, _beta3 etc, tiny updates and fixes can be named _beta1_1, _beta1_2, _beta1_3 etc.
It means that mappers will need to update their maps within 1 month in order for the map to have a 100% chance of hosting for beta feedback and testing. Having said that I don't want to be hosting a map that's still not finished 10 months after the first beta! These rules have been made to keep the ~[FGS]0-Augs Server~ map rotation as fresh as possible, it also gives incentive for those to update and then finish their maps.
1. "Any beta map that has not been updated for 1 month will be taken off the map rotation and placed into the bi-monthly map vote"
2. "Each mapper is allowed to have a limit of no more then 2 maps in beta stage at any one time involved in the 0-augs hosting or bi-monthly vote, those with 3 or more beta maps will have their oldest beta removed from hosting/bi-monthly map vote"
3. Beta maps should be named with the extension _beta1, _beta2, _beta3 etc, tiny updates and fixes can be named _beta1_1, _beta1_2, _beta1_3 etc.
It means that mappers will need to update their maps within 1 month in order for the map to have a 100% chance of hosting for beta feedback and testing. Having said that I don't want to be hosting a map that's still not finished 10 months after the first beta! These rules have been made to keep the ~[FGS]0-Augs Server~ map rotation as fresh as possible, it also gives incentive for those to update and then finish their maps.