Template:Stub - Revision history

Smithy at 15:35, 6 August 2021

2021-08-06T15:35:14Z

← Older revision		Revision as of 15:35, 6 August 2021
Line 1:		Line 1:
	{\|		<onlyinclude>{\|
	\|-		\|-
	\| [[Image:stub.jpg\|40px]]		\| [[Image:stub.jpg\|40px]]
	\|		\|
	<div class="boilerplate metadata" id="stub">''This article is a [[stub]]. You can contribute by [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}\|action=edit}} editing it]''.</div>		<div class="boilerplate metadata" id="stub">''This article is a [[stub]]. You can contribute by [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}\|action=edit}} editing it]''.</div>
	\|}		\|}</onlyinclude>

	~~<noinclude>~~
	[[Category:Templates]]		[[Category:Templates]]
	~~</noinclude>~~

Smithy at 12:51, 6 August 2021

2021-08-06T12:51:31Z

← Older revision		Revision as of 12:51, 6 August 2021
Line 5:		Line 5:
	<div class="boilerplate metadata" id="stub">''This article is a [[stub]]. You can contribute by [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}\|action=edit}} editing it]''.</div>		<div class="boilerplate metadata" id="stub">''This article is a [[stub]]. You can contribute by [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}\|action=edit}} editing it]''.</div>
	\|}		\|}

			<noinclude>
			[[Category:Templates]]
			</noinclude>

Solokiller at 20:29, 29 March 2006

2006-03-29T20:29:10Z

← Older revision	Revision as of 20:29, 29 March 2006
Line 1:	Line 1:
		{\|
		\|-
		\| [[Image:stub.jpg\|40px]]
		\|
		<div class="boilerplate metadata" id="stub">''This article is a [[stub]]. You can contribute by [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}\|action=edit}} editing it]''.</div>
		\|}

Solokiller at 20:21, 29 March 2006

2006-03-29T20:21:36Z

← Older revision		Revision as of 20:21, 29 March 2006
Line 1:		Line 1:
	~~== General Empires Mod Mapping Guidelines ==~~

	~~== Less Detail, More Space ==~~

	Empires is designed to be played over very large areas. Merely the simple requirement of space for both teams base areas and sufficient resource nodes to support them, dictates a map on a larger scale than most HL mods.

	~~This means that fine detail is close to pointless, as maintaining that level of detail through out the map will result in massive amounts of lag.~~

	~~Empires players are looking for a very large space to do strategic battle in, they do not want to stand and admire your waterfall effect on a small drainage pipe that very few people will ever see.~~

	~~However that is not to say every map should be a wide open space, just large and varied enough to allow strategic options.~~

	~~== Chokepoints should be placed very carefully ==~~

	Chokepoints are what make some maps fun, and they are also what makes some maps terrible. In general, chokepoints should be of roughly equal benefit to each side. When designing a choke point, imagine yourself attacking and defending it from the viewpoint of both sides. If you can envisage one team finding it particularly easy to defend/attack, then you need to think very carefully about whether the map is truely balanced.

	~~== It doesn't have to be a 'real' place ==~~

	Take emp_money for example. I bet very few people have ever considered just why such an odd structure exists. That is because it provides an interesting and balanced battlefield purely through its geography. It has nothing to do with the feeling of 'realism' that most singleplayer maps will find essential to immersive and fun play.

	~~== Resource nodes should also be placed carefully ==~~

	~~Resources should be at roughly equal distances from the starting positions or one team will consistently have the upper hand over the other.~~

Solokiller at 20:19, 29 March 2006

2006-03-29T20:19:22Z

← Older revision	Revision as of 20:19, 29 March 2006
Line 1:	Line 1:
		== General Empires Mod Mapping Guidelines ==

		== Less Detail, More Space ==

		Empires is designed to be played over very large areas. Merely the simple requirement of space for both teams base areas and sufficient resource nodes to support them, dictates a map on a larger scale than most HL mods.

		This means that fine detail is close to pointless, as maintaining that level of detail through out the map will result in massive amounts of lag.

		Empires players are looking for a very large space to do strategic battle in, they do not want to stand and admire your waterfall effect on a small drainage pipe that very few people will ever see.

		However that is not to say every map should be a wide open space, just large and varied enough to allow strategic options.

		== Chokepoints should be placed very carefully ==

		Chokepoints are what make some maps fun, and they are also what makes some maps terrible. In general, chokepoints should be of roughly equal benefit to each side. When designing a choke point, imagine yourself attacking and defending it from the viewpoint of both sides. If you can envisage one team finding it particularly easy to defend/attack, then you need to think very carefully about whether the map is truely balanced.

		== It doesn't have to be a 'real' place ==

		Take emp_money for example. I bet very few people have ever considered just why such an odd structure exists. That is because it provides an interesting and balanced battlefield purely through its geography. It has nothing to do with the feeling of 'realism' that most singleplayer maps will find essential to immersive and fun play.

		== Resource nodes should also be placed carefully ==

		Resources should be at roughly equal distances from the starting positions or one team will consistently have the upper hand over the other.

Solokiller at 20:18, 29 March 2006

2006-03-29T20:18:04Z

← Older revision		Revision as of 20:18, 29 March 2006
Line 1:		Line 1:
	~~== General Empires Mod Mapping Guidelines ==~~

	~~== Less Detail, More Space ==~~

	Empires is designed to be played over very large areas. Merely the simple requirement of space for both teams base areas and sufficient resource nodes to support them, dictates a map on a larger scale than most HL mods.

	~~This means that fine detail is close to pointless, as maintaining that level of detail through out the map will result in massive amounts of lag.~~

	~~Empires players are looking for a very large space to do strategic battle in, they do not want to stand and admire your waterfall effect on a small drainage pipe that very few people will ever see.~~

	~~However that is not to say every map should be a wide open space, just large and varied enough to allow strategic options.~~

	~~== Chokepoints should be placed very carefully ==~~

	Chokepoints are what make some maps fun, and they are also what makes some maps terrible. In general, chokepoints should be of roughly equal benefit to each side. When designing a choke point, imagine yourself attacking and defending it from the viewpoint of both sides. If you can envisage one team finding it particularly easy to defend/attack, then you need to think very carefully about whether the map is truely balanced.

	~~== It doesn't have to be a 'real' place ==~~

	Take emp_money for example. I bet very few people have ever considered just why such an odd structure exists. That is because it provides an interesting and balanced battlefield purely through its geography. It has nothing to do with the feeling of 'realism' that most singleplayer maps will find essential to immersive and fun play.

	~~== Resource nodes should also be placed carefully ==~~

	~~Resources should be at roughly equal distances from the starting positions or one team will consistently have the upper hand over the other.~~

Solokiller: General Mapping Tips

2006-03-29T20:17:36Z

General Mapping Tips

← Older revision	Revision as of 20:17, 29 March 2006
Line 1:	Line 1:
		== General Empires Mod Mapping Guidelines ==

		== Less Detail, More Space ==

		Empires is designed to be played over very large areas. Merely the simple requirement of space for both teams base areas and sufficient resource nodes to support them, dictates a map on a larger scale than most HL mods.

		This means that fine detail is close to pointless, as maintaining that level of detail through out the map will result in massive amounts of lag.

		Empires players are looking for a very large space to do strategic battle in, they do not want to stand and admire your waterfall effect on a small drainage pipe that very few people will ever see.

		However that is not to say every map should be a wide open space, just large and varied enough to allow strategic options.

		== Chokepoints should be placed very carefully ==

		Chokepoints are what make some maps fun, and they are also what makes some maps terrible. In general, chokepoints should be of roughly equal benefit to each side. When designing a choke point, imagine yourself attacking and defending it from the viewpoint of both sides. If you can envisage one team finding it particularly easy to defend/attack, then you need to think very carefully about whether the map is truely balanced.

		== It doesn't have to be a 'real' place ==

		Take emp_money for example. I bet very few people have ever considered just why such an odd structure exists. That is because it provides an interesting and balanced battlefield purely through its geography. It has nothing to do with the feeling of 'realism' that most singleplayer maps will find essential to immersive and fun play.

		== Resource nodes should also be placed carefully ==

		Resources should be at roughly equal distances from the starting positions or one team will consistently have the upper hand over the other.

Solokiller at 20:11, 29 March 2006

2006-03-29T20:11:06Z

← Older revision		Revision as of 20:11, 29 March 2006
Line 1:		Line 1:
	~~== General Empires Mod Mapping Guidelines ==~~

	~~== Less Detail, More Space ==~~

	Empires is designed to be played over very large areas. Merely the simple requirement of space for both teams base areas and sufficient resource nodes to support them, dictates a map on a larger scale than most HL mods.

	~~This means that fine detail is close to pointless, as maintaining that level of detail through out the map will result in massive amounts of lag.~~

	~~Empires players are looking for a very large space to do strategic battle in, they do not want to stand and admire your waterfall effect on a small drainage pipe that very few people will ever see.~~

	~~However that is not to say every map should be a wide open space, just large and varied enough to allow strategic options.~~

	~~== Chokepoints should be placed very carefully ==~~

	Chokepoints are what make some maps fun, and they are also what makes some maps terrible. In general, chokepoints should be of roughly equal benefit to each side. When designing a choke point, imagine yourself attacking and defending it from the viewpoint of both sides. If you can envisage one team finding it particularly easy to defend/attack, then you need to think very carefully about whether the map is truely balanced.

	~~== It doesn't have to be a 'real' place ==~~

	Take emp_money for example. I bet very few people have ever considered just why such an odd structure exists. That is because it provides an interesting and balanced battlefield purely through its geography. It has nothing to do with the feeling of 'realism' that most singleplayer maps will find essential to immersive and fun play.

	~~== Resource nodes should also be placed carefully ==~~

	~~Resources should be at roughly equal distances from the starting positions or one team will consistently have the upper hand over the other.~~

Solokiller at 20:08, 29 March 2006

2006-03-29T20:08:18Z

@@ Line 1: / Line 1: @@
-{|
+== General Empires Mod Mapping Guidelines ==
-|-
-| [[Image:stub.jpg|40px]]
+== Less Detail, More Space ==
-<div class="boilerplate metadata" id="stub">''This article is a [[stub]]. You can contribute by [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing it]''.</div>
+Empires is designed to be played over very large areas. Merely the simple requirement of space for both teams base areas and sufficient resource nodes to support them, dictates a map on a larger scale than most HL mods.
-|}

Administrator at 02:10, 10 March 2006

2006-03-10T02:10:31Z

New page

{|
|-
| [[Image:stub.jpg|40px]]
|
<div class="boilerplate metadata" id="stub">''This article is a [[stub]]. You can contribute by [{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} editing it]''.</div>
|}