Inform yourself and your team, read the Global Rules here.

Rules for Medal of Honor Allied Assault - Objective 2s & 3s

1. Introduction

Every ladder has a set of rules, please take the time to read through these rules and learn them to avoid conflicts.


When playing official ladder matches with AlphaMAC as anti-cheat, you are required to have your AlphaMAC ID added as a guid on your profile. If you won the match without having this ID added to your guides the opponent can request a cancel match.

How to add a guide:

Edit your profile on ScrimBase and choose to edit guids (or click here). Select Medal of Honor Allied Assault in the list and type something like this: "AlphaMAC ID: 12345". You can find your AlphaMAC ID by going to your profile on the AlphaMAC website, the number in the url is your ID.

2. Match rules

A match is played over two maps, one picked by each team in the challenge form. On every map, both teams will play each side once.

Scoring systems

All rounds count: Teams play as each team, on each map, for a set amount of rounds. i.e. 4 times 7 rounds each round lastst 4 minutes. A draw round counts as a played round.

Total rounds are added up at the end of the war and the team with most rounds is the winner. Ties are allowed, there are no tie breaker maps.

The match will begin with a massbash (all players involved), or a 1on1 bash. The winning team decides which map & side to start with.

Between maps a break of max 5 minutes can be taken.

3. Optional rules

If someone challenges you with anything in the notes it will count as rules for that match. So if you accept the challenge you ARE accepting these match notes as rules. Pay attention when accepting! If you do not accept the match notes as rules of the challenge you are able to refuse the challenge or click the reschedule button to send it back with different match notes.

By default the shotgun and the rocketlauncher are not allowed. It is also allowed to have other weapon limitations. The challenger puts them into the challenge notes and they will be accepted by the opponent when he accepts the challenge.

For example:

  • 2 shotgun max
  • 2 snipers max

Friendly Fire is enabled by default (set g_teamdamage 1) in ranked matches. However you can choose to put it off in unranked matches.

4. Maplist

The maplist for MoH:AA Objective ranked matches is:

  • The Hunt
  • V2 Rocket Facility
  • The Bridge

5. Client settings

The "Force models" and "Smoothclients" commands are allowed.

All the standard skins are allowed. We do not allow any custom skins or modifications to the default interface.

Client settings

  • r_gamma 1 (if playing with 2 monitors plugged in)
  • r_ignorehwgamma 0
  • cg_shadows 0
  • r_intensity 1.00

Playing with 2 monitors plugged in?

When playing with 2 monitors you are forced to play with r_gamma 1, any other value caught on screenshots will be a violation. If you want to know what it looks like you can check examples here.

Not uploading all the screenshots and demo's taken by AlphaMAC is also a violation, if they won't upload to AlphaMAC you have to manually upload them if requested by the opponent or admins. Remember that demo's can be checked by admins to check for vision abuse.

If you find your screen too dark in game then unplug your 2nd monitor when playing mohaa or uncheck the second monitor in your control panel. When playing with 1 monitor any gamma value is allowed for now, but again ONLY if you play with 1 plugged in monitor.

6. Server settings

It is not allowed to change any server setting after the match has started, doing so will result in a forfeit loss.

Matches have to be played with the new default and realism mods made by pstN. For default use "User_sbdefault.pk3" and for realism use "User_realism.pk3". Other mods and mapfixes aren't necessary anymore, everything is grouped in these .pk3 files so anything else isn't allowed anymore.

Server settings

  • rcon roundlimit 4
  • rcon timelimit 0
  • rcon fraglimit 0
  • rcon g_inactivespectate 0
  • rcon g_allowjointime 2
  • rcon g_inactivekick 0

Cvar list AlphaMAC rules

Rule Name Rule Value Rule Actions Custom Value
r_ignorehwgamma !=0 Kick Yes
cg_shadows !=0 Deny Yes
r_intensity !=1.00 Kick Yes
cg_3rd_person !=0 Deny No
cg_acidtrip >0 Deny No
cg_cameraverticaldisplacement ==-18 Deny No
cg_showbullettrace !=0 Deny No
r_drawbushes ==0 Deny No
r_drawstaticmodels ==0 Deny No
r_farplane_nofog >0 Deny No
r_lightmap >0 Deny No
r_picmip >2 Deny No
r_fastsky >0 Deny No
r_fullbright >0 Deny No
r_light_nolight >0 Deny No
r_light_showgrid >0 Deny No
r_mapOverBrightBits !=1 Deny No
r_nobind >0 Deny No
r_novis >0 Deny No
r_overbrightbits >0 Deny No
r_showcull >0 Deny No
r_showsky >0 Deny No
r_showSmp >0 Deny No
r_singleshader >0 Deny No
r_vertexlight >0 Deny No
r_static_shadermultiplier3 ==0 Deny No
r_subdivisions <=0 Deny No
r_drawstaticmodelpoly ==0 Deny No

7. Recording the match

At the end of every map side it is required to take a screenshot of the score and upload it if requested. Every player has to record a demo of the complete match, a team can also ask opposing players for path/dir screenshots during the match which they have to provide after the match (if path/dir is not asked during the match it cannot be requested after the match). When requested by the other team, players are obligated to add these demo's and screenshots to the match on ScrimBase. Failing to deliver requested files by the opposing team, may result in a forfeit loss.

8. Miscellaneous rules

Substitutions can only be made at half time. The only exception to this rule is when a player is having severe connection problems, and is unable to continue playing. Lag is not an example of this. In these cases you can change to a new player after the next round has started without pause.

Play will only stop if both teams agree, or if the end of a quarter is reached. Teams officially have 2 minutes between team changing (unless granted more by the other team) and an official 5 minute break between map changing.

It is NOT allowed to kick any player during play. The ONLY exception to this is when a player has timed out, and is waiting to re-enter the server. Permission must first be obtained from the opposing team, and wait for the opposing team to ask for a player to be kicked if it is one of their players.

9. Cheating and abuse

Matches may be edited to a cancellation, no-show, forfeit loss or a win for the opponent - depending on the ladder rules and severity of the problem. A forfeit loss is the standard punishment for all severe violations unless the punishment is otherwise stated in the rules.

It is not allowed to take advantage of or abuse bugs. Any kind of bug abuse is considered cheating and will lead to a forfeit loss, unless otherwise mentioned specifically in the game-related rules.

All programs or files, either changed game files or new files, that change the game or add to its functionality, or which interact with the game in any way, are strictly forbidden. Modified versions of the game's resource files are always forbidden, regardless of what they do.

The only exceptions to the rule above are clientside applications for anti-cheat and all the ScrimBase approved custom maps plus its accompanied maps folder.

Programs that do not interact with the game in any way are allowed, even if they can be used and operated simultaneously with the game. Voice communication programs are examples of such programs.

Any place on the map that you can reach by yourself, without altering server settings, is allowed. It is also allowed to stack players on top of each other to look and shoot over buildings and walls.

However, it is not allowed to:

  • Jump on rooftops or walls with help of other players, when you could not have reached that place on your own
  • Go out of the map
  • Abuse any map bugs
  • It is not allowed to respawn during a match
  • It is allowed to block doors and to bash through doors

Teams abusing the ladder system in any way in order to gain an advantage or just to be a nuisance will be deleted. Further punishment may include deletion of the accounts of the person responsible for the abuse, in extreme circumstances.

10. General

If the ladder rules for a specific ladder conflict with these global ladder rules, then the specific rules have precedence.

The proper functioning of the ladder system depends on the sportsmanship of the participating teams. We expect everybody to play by the rules, but also to be flexible when circumstances require it and to be reasonable when an opponent has problems beyond their control.

Not knowing the ladder rules is never a valid excuse for not following them.

11. Before the match

If you're more than 15 minutes late, you have to accept a no-show if your opponent insists. If you feel there's a good reason the result shouldn't be a no-show, you'll have to convince your opponent of that.

If one team is short of players or refuses to start the match with the rules agreed upon in the challenge form, the other team can demand a no-show to be filled in. Remember that challenge notes, the proposed server and agreements made elsewhere are not considered to be binding rules.

12. During the match

Once a match has started, its result counts, unless both sides agree it shouldn't. Ping, lag issues or incorrect server settings are no excuse for leaving; you should have checked the server before you started playing.

13. After the match

When a match is played the score can be entered on ScrimBase, select all players that played the match, upload screenshots and/or demo's if requested and complete the match.

If one team walks away from the match, the score at the time when their last player quit can be considered to be the result of the match if the team that stayed was leading. If the leaving team was winning but the losing team could have still won the match, ScrimBase can change it to the advantage of the team that stayed.

These rules are last revised on 6 July 2020