Difference between revisions of "Level Designing Etiquette"

From Elma Wiki
Jump to navigation Jump to search
m
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
When you are designing a level, there are several important guidelines to remember:
+
[[File:Tootight.png|313px|thumb|Wheel in a tight gap. These are not allowed in battle.]]
* Be careful with gravity.
+
When you are designing a level, there are several guidelines to remember:
* Speedloops, levels with very fast parts and big loops are generally considered to be boring and unwanted.
+
* Avoid placing two polygons too close to each other if the wheels are supposed to fit between them. Wheels getting stuck between too tight gaps results in [[bugs]], such as speeding up unrealistically fast. The result depends highly on the [[tuning|FPS]] and thus is most unfair and undesirable. Battles that include or depend on such spots will usually be aborted.
* Make sure your levels are suitable for the battle mode you choose, and not too hard (or easy, depending on the battle type).
+
* Do not make invisible polygons.
* If you are going to put the level up as a [[battle]], choose the battle time with care, usually too much time is better than too little time.
+
* Make sure your levels are suitable for the [[Battle types|battle type]] you choose.
* Avoid placing two polygons too close to each other if the wheels are supposed to fit between them. If the spcae is too tight, the result will be unexpected behaviour such as speeding up the bike or completely stopping it. The result is [[tuning|fps]]-dependable and thus most unfair and undesirable.
+
** Survivor battles should obviously not have spots where it's easy to stop completely.
 +
** Slowness battles should also not have spots where it's easy to stop, unless that loss of momentum makes finishing the level harder.
 +
** Flagtag battles need to allow players to move freely in many directions. Dead ends that are hard to escape will get the flag stuck. Gravity apples are an easy way to allow mobility.
 +
* Place arrows next to gravity apples to indicate the direction of gravity.
 +
* Many players have strong preferences regarding battle time, but there are no strict rules. Sometimes moderators will stop e.g. a ridiculously long battle on a short level.
 +
* Speedloops, levels with very fast parts and big loops, are generally considered boring and unwanted.

Latest revision as of 07:32, 8 May 2015

Wheel in a tight gap. These are not allowed in battle.

When you are designing a level, there are several guidelines to remember:

  • Avoid placing two polygons too close to each other if the wheels are supposed to fit between them. Wheels getting stuck between too tight gaps results in bugs, such as speeding up unrealistically fast. The result depends highly on the FPS and thus is most unfair and undesirable. Battles that include or depend on such spots will usually be aborted.
  • Do not make invisible polygons.
  • Make sure your levels are suitable for the battle type you choose.
    • Survivor battles should obviously not have spots where it's easy to stop completely.
    • Slowness battles should also not have spots where it's easy to stop, unless that loss of momentum makes finishing the level harder.
    • Flagtag battles need to allow players to move freely in many directions. Dead ends that are hard to escape will get the flag stuck. Gravity apples are an easy way to allow mobility.
  • Place arrows next to gravity apples to indicate the direction of gravity.
  • Many players have strong preferences regarding battle time, but there are no strict rules. Sometimes moderators will stop e.g. a ridiculously long battle on a short level.
  • Speedloops, levels with very fast parts and big loops, are generally considered boring and unwanted.