Edit 2:Thanks for the suggestions guys. Our email is officially sent! In the subject line I put; 'from the mapping community'. Now we just have to wait Edit 1: Does anyone actually know the TF2 devs email? At long last, I think we're ready to be done w/ this thing Frankly, the reason this has taken so long is b/c I've been a lazy sob lately, busy w/ geek party stuff like every day for summer vacation, lol. Anyways, I've done my best to incorporate and otherwise revise all the suggestions in the previous thread; http://forums.tf2maps.net/showthread.php?t=1442 Credit for the revised template of my original letter goes to DrHapazard. Dear TF2 Design Team, I am writing this letter on behalf of the mapping community at TF2Maps.net. As the site name implies, the community is geared towards mapping for Team Fortress 2 and making other custom content for the game. Most of the discussions on the forum center on the usual optimization, layout and entity questions. However, there is also a recurring theme of posts trying to get around some of the limitations that seem to be built in to the TF2 mapping system. This letter and the list attached mentions some of the more common roadblocks that the TF2 mapping community runs into. We are all hoping that some of these restrictions could be looked into by Valve's TF2 team. Our overarching request is to introduce more flexibility into the Team Fortress 2 custom mapping process. Several of our members have been mapping since the days of Team Fortress Classic, and they have praised the TFC system in which an infinite number of game play variations could be created. We would love some of that same flexibility to be present in the current mapping system so that we can more easily create custom objectives and game play styles beyond those that are included in the game. Some overall examples of our requests include the addition of more working filter entities, both by class and by weapon damage type, which would allow for custom, class based objectives. Another example would be the ability to customize the item_teamflag so that variables such as carrier run speed and return timer could be tweaked to better fit into different game play styles. The most important request of all, however, deals with ability to create custom scoring structures so that the TF2 mapping community is not tied down to the current standard CTF and CP styles of play. We are aware that making changes like these can be very time consuming. We also know, however, that Valve has an excellent record when it comes to supporting its products and helping the modding community that works with its games. Your continued work in creating new maps, class tweaks and game play styles for Team Fortress 2 confirms that reputation. Finally, while this letter might appear to be one big gripe, none of us over at TF2maps.net would be mapping at all if we did not enjoy the challenges and the rewards of the mapping process. Keep making great games and keep giving us new stuff to work with! Thanks for your time, Your fans at TF2Maps.net List of requests follows. Because these suggestions were contributed by multiple mappers they are not unified in wording. We have, however, tried to group them by general categories to make things clearer. Thanks again! CTF – While the “game type” variable for the item_teamflag is an interesting concept, it is also often buggy. We feel that the inclusion of more variables for the flag entity would eliminate the need for the game type variable and would allow greater flexibility. 1. Create a speed penalty variable so carriers can be slowed/sped up, preferably a percentage of normal speed. 2. Currently a flag carrier can pick up an infinite number of his team’s/neutral flags, but in the process the pickup disables any previously grabbed flags. This makes multiple flag games (more than one per side) a very buggy situation and hinders the recreation of some classic TFC scenarios, such as CZ2. 3. Allow for CTF maps to have a Setup Time and allow each team to place the intel at a certain point in the map before the match begins FILTERS – Adding these filters would allow for more custom objective based upon class or flag possession, making for unique game scenarios. 4. Allow a way to filter player classes 5. Allow a way to filter weapon damage 6. Allow a way to filter out flag carriers 7. filter_activator_name appears to be broken for TF2 8. Add a way to filter by uber status 9. Add a way to filter by cloak status SCORING – This is a major category. Scoring gets to the heart of how a level plays. More variety in the scoring system might allow for flag captures to count for different amounts depending on where the flag is returned. A point system based on time of possession for Capture Point games would help branch out from the current all-or-nothing winning system. These are just examples of how more variables when it comes to scoring in TF2 allows for new and interesting game play options. 10. The game_score entity currently does not alter individual player scores, only team scores, making it difficult to correctly reward players completing custom objectives. 11. A more direct way to manipulate team score. Having to tie a game_score entity to a trigger_multiple with a filter_activator_tfteam is awkward and leads to some unavoidable bugs. 12. Allow for other scoring systems than CP/CTF, such as a gradual scoring system, that can be displayed in the HUD HUD – In combination with the Scoring system, more variables in how the HUD is set up would allow mappers to better direct players to objectives and more easily display custom scoring systems. 13. The option for turning OFF any auto-HUD stuff that the mapper doesn’t need for his map 14. Allow both CP HUD icons and CTF HUD icons on at the same time 15. Custom HUD element entity. The entity lets you define where on the screen they go, and what is linked to them (state of an entity, compass position of an entity, etc) how many elements MODELS 16. Scalable models. (We know this is a major request, but this ability would truly be a godsend for any game that uses the Hammer editor.) 17. Add the ability to automatically embed custom models and textures into your map from Hammer (during the compile process, if possible) 18. Incorporate the custom model compiler into either the XSI Mod Tool or Hammer. Having it as a separate step between the two is inconvenient and confusing for many people ENTITIES 19. Ability to use fire as part of the environment, and have it react w/ the Pyro. 20. Make func_rotating work 21. Make func_nogrenades work (to avoid stickies in the wrong places) MISC – Despite being stuck in the miscellaneous category, these would also be useful additions. The class limit request is especially important since it would again allow for the mapper to better tweak his map to favor the completion of custom objectives. 22. Ability to limit classes (or disable) and ability to change the limits as objectives are met 23. Ability to control max spawn time, not just min spawn time. Even if min spawn time is set to 5 seconds, in game it still gets as large as 15 - 20 seconds randomly. 24. Ability to implement a territory control overview map/window for non-TC game types. 25. Fix for the TeamNum property of func_nobuild.