Map Testing


With the recent addition of Vscript to TF2, the potential for security exploits exists.
Any exploits should be reported directly to Valve.

TF2Maps has a zero tolerance policy for any user uploading maps to our servers containing VScript exploits.
Any user found engaging in this will be immediately banned permanently and with no course for reinstatement.

How to Submit Your Map

Here at TF2Maps, we run regular map tests on our servers. All playable maps* are accepted! If you'd like to test your map with us, follow these steps:
  1. Join the TF2Maps Discord and navigate to the #bot channel.
  2. Type /add <download url> <notes> to add your map to the queue. Notes can request certain features and are optional.
  3. Example notes:
    • Use hlxce scramble modes!
    • Disable alltalk. Don't play without me.
    • Please ask for feedback about fps.
    • I only need 2 rounds then you can skip.
    • Enable mannpower please.
    • You can also submit anything else that is acceptable within our rules. It gets broadcasted at the beginning of every round.
  4. That's it! Feel free to hang out in chat until a map test is announced. Depending on the length of the queue, it may take a day or two to get to yours.

Regarding Notes

  • If a map has been on the list for more than a week and the notes are time/region restrictive, they will be ignored. An example of this is as follows: "Play with me." and/or "Play with me on EU only".
  • Notes such as "enable random crits" will still be honored even if the map has been on the list for more than a week as those types of notes are not time restrictive.

*Submitted maps must meet the following criteria

Not following any of these rules may result in the Map Test Host skipping your map and entering the feedback round immediately. You may always resubmit your map for testing after fixing any issues, of course.

General Rules

  1. Your map must have a gamemode prefix and a version suffix! Examples: koth_coolmap_a1, cp_testmap_b1, further information.
  2. Your filename must be all lowercase and have no special characters! This has technical reasons and is the convention for all TF2 maps anywhere.
  3. The map you are uploading to the list needs to be yours! Exception: You have explicit permission from the map creator or the map is intended for an approved gameday.
  4. Your map needs to be lit properly! This means a correctly configured light_environment entity if the map is set outside and fully lit rooms inside (ghost lights are perfectly acceptable!). If you are using HDR, the map needs to be compiled with both LDR and HDR and use a correctly configured tonemap entity. Imp hosts may skip your map if the lighting inhibits gameplay or makes players uncomfortable.
  5. Your map needs to work! At a minimum the map needs to feature spawn rooms, respawn room visualizers, and resupply cabinets (unless it’s arena), as well as healthkits, ammopacks, and a functional objective corresponding to your gamemode. Custom logic and gamemodes are always allowed, of course, as long as they are winnable.
  6. Your map needs to be sealed! Leaking maps have worse performance and poor lighting quality, as well as other possible issues.
  7. Your map must not intentionally crash the server or clients. No one will bat an eye if this happens on accident (as long as it doesn’t happen every time), but doing it on purpose is funny exactly never.
  8. Your map must not require custom server plugins to function. We only test maps that would work on any normal TF2 server. Your logic may interact with our custom feedback round plugin however, using a logic_relay named TF2M_FeedbackRoundRelay, which will get triggered automatically.
  9. Maps that are considered jokes or are intended for events such as April Fools need to be clearly labeled as such in the upload notes!

Custom Content rules

  1. If your map uses custom assets such as models or textures, they need to be packed! This is necessary for other players to be able to see the assets. These days this is most easily done using CompilePal. You can check whether your assets are actually packed into the map by temporarily renaming your tf/custom folder and running through your map in-game.
  2. If your map uses custom assets, it needs to be repacked! Repacking (not to be confused with packing) compresses the map, reducing filesize and download times. This can also be done with CompilePal, check the checkmark! or use this.
  3. No custom content that breaks TF2Maps rules. This includes obscene, NSFW, insulting, or copyrighted content (exceptions can be made on a case-by-case basis).

VScript Rules

  1. Your map must not contain any malicious VScript code. If discovered, it is grounds for an immediate ban from all TF2Maps services. User safety is our highest priority.
  2. Vscript must not run any SourceMod commands.
  3. Vscript must not impersonate anyone with chat commands.

Game Servers

* The MVM servers are kept offline sometimes. If you try to connect and are unable to please contact staff so we can fire it up for you.


We run a custom feedback plugin that allows players to leave comments with optional coordinates as they play. Once your map has been tested, you can find the recorded feedback and demos here.

Leaving feedback in-game.

Feedback can be left while playing the game. !fb is used for location based feedback, this leaves the coordinates of where you are standing and where you are looking. !gf is used for general feedback and will not have coordinates attached. Here are some examples:

  • !fb this spot is broken
  • !gf this map is fun