Good Map Guidelines
2012-07-08, 12:16 PM (This post was last modified: 2013-10-30, 02:55 PM by Victor.)
#1
Good Map Guidelines
There are many maps, but not all of them are that good to play on. It degrades users' experience to play bad maps.

What constitutes bad maps may change as the game is modified. For example, a map might force players underwater for 5 seconds. This might not have any effect yet, but if the game is modified, the players might drown in that time.

No official ACR map may fail to follow these guidelines:
  1. No extremely large maps! These maps take a long time to flood waypoints. *Some exceptions may apply.
  2. The waypoint flood must not take too long to complete.
  3. Player spawns! Player spawns should be created for every team (RED, BLUE, FFA) and they should not face the walls. This can be fixed by editing the entity while facing the right direction.
  4. No more than 3 bodies of water are allowed, and the largest body of water may not be too large (20x16 and 10 cubes deep)
  5. No large areas with a large height (e.g. twintowers). No large open areas either (e.g. longhorn).
  6. No traps that players cannot exit. These are annoying, and are for some non-official gema maps only.
  7. It should not take too long to get to the enemy (i.e. no gema maps where both teams try to get to the other side)
  8. No areas that force players to drown (e.g. KrizzlysFunhouse)
  9. Gameplay must be balanced. One team must not have an advantage over the other. If there is an equal advantage to both sides, it is acceptable.
  10. Instead of using map models, consider using solids (e.g. doors), as those are computed faster.
  11. Don't create inaccessible areas, as those waste computing resources (since no-one can get in, except from editmode).
  12. Hidden doorways are not noob-friendly, and should be avoided.
  13. Proper lighting! It should not use full-bright, and should not be over-lit (same as full-bright) or under-lit (too dark to see).

In addition, allowing derivation must be allowed.

This list can change anytime. Suggest improvements by replying to this thread.

Best regards,
Victor
//victorz.ca
Code:
Your antithesis compares favorably with any high magnitude of pwnage. (-you > |p|, you < -|p|)
My antithesis compares favorably with _that of_ any high magnitude of pwnage. (|-me| > |-p|, |me| > |p|)
Post Reply Quote this message in a reply


Messages In This Thread
Good Map Guidelines - by Victor - 2012-07-08, 12:16 PM
RE: Good Map Guidelines - by Nightmare - 2012-07-08, 12:43 PM
RE: Good Map Guidelines - by Victor - 2012-07-08, 06:39 PM
RE: Good Map Guidelines - by forumlurker007 - 2013-10-29, 01:19 AM
RE: Good Map Guidelines - by dm.mossberg590a1 - 2013-10-29, 02:34 AM
RE: Good Map Guidelines - by Victor - 2013-10-29, 02:56 PM
RE: Good Map Guidelines - by forumlurker007 - 2013-10-30, 07:43 AM

Forum Jump:


This forum uses Lukasz Tkacz MyBB addons.