Gameplay Strategy For The Mod Developer - Revision history

Neddiedrow: /* The Mod Developer's Role In Relation To Strategy */

2006-12-04T21:52:06Z

The Mod Developer's Role In Relation To Strategy

← Older revision		Revision as of 22:52, 4 December 2006
Line 5:		Line 5:
	===The Mod Developer's Role In Relation To Strategy===		===The Mod Developer's Role In Relation To Strategy===

	As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision~~, but on~~ the other hand must compensate for the actions of the player base.		As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision. On the other hand your game design must compensate for the actions and desires of the player base.

	In example, if an artillery unit is highly capable in direct combat, chances are you have let the role of the unit collapse and must ~~rectify~~ the ~~lack~~. In order to solve issues like this you must be aware of what the players are doing. These events are inevitable, as promoted by the interaction between your vision, the engine, different maps and of course the ever-present force of sheer human creativity.		In example, if an artillery unit is highly capable in direct combat, chances are you have let the role of the unit collapse and must correct the mistake. In order to solve issues like this you must be aware of what the players are doing. These events are inevitable, as promoted by the interaction between your vision, the engine, different maps and of course the ever-present force of sheer human creativity.

	===Conclusion===		===Conclusion===

Neddiedrow at 23:02, 17 November 2006

2006-11-17T23:02:41Z

← Older revision		Revision as of 00:02, 18 November 2006
Line 1:		Line 1:
	~~'''~~Overview~~'''<br><br>~~		===Overview===

	As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.		As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.

	~~'''~~The Mod Developer's Role In Relation To Strategy~~'''<br><br>~~		===The Mod Developer's Role In Relation To Strategy===

	As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base.		As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base.

	In example, if an artillery unit is highly capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this you must be aware of what the players are doing. These events are inevitable, as promoted by the interaction between your vision, the engine, different maps and of course the ever-present force of sheer human creativity.		In example, if an artillery unit is highly capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this you must be aware of what the players are doing. These events are inevitable, as promoted by the interaction between your vision, the engine, different maps and of course the ever-present force of sheer human creativity.

	~~'''~~Conclusion~~'''<br><br>~~		===Conclusion===

	In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.		In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.

Neddiedrow at 23:01, 17 November 2006

2006-11-17T23:01:30Z

← Older revision		Revision as of 00:01, 18 November 2006
Line 1:		Line 1:
	'''Overview'''<br>		'''Overview'''<br><br>
	As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.		As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.

	'''The Mod Developer's Role In Relation To Strategy'''<br>		'''The Mod Developer's Role In Relation To Strategy'''<br><br>
	As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base. If an artillery unit is capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this, inevitable, you must be aware of what the players are doing.		As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base.

	'''Conclusion'''<br>		In example, if an artillery unit is highly capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this you must be aware of what the players are doing. These events are inevitable, as promoted by the interaction between your vision, the engine, different maps and of course the ever-present force of sheer human creativity.

			'''Conclusion'''<br><br>
	In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.		In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.

Neddiedrow at 22:58, 17 November 2006

2006-11-17T22:58:51Z

← Older revision		Revision as of 23:58, 17 November 2006
Line 7:		Line 7:
	'''Conclusion'''<br>		'''Conclusion'''<br>
	In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.		In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.

			''' [[Strategy_and_Tactics\|<- Back to Strategy and Tactics page]]'''

			[[category:Strategy]]

Neddiedrow at 22:58, 17 November 2006

2006-11-17T22:58:17Z

← Older revision		Revision as of 23:58, 17 November 2006
Line 1:		Line 1:
	'''Overview'''<br>		'''Overview'''<br>
	As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.		As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.
	'''
	The Mod Developer's Role In Relation To Strategy'''<br>		'''The Mod Developer's Role In Relation To Strategy'''<br>
	As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base. If an artillery unit is capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this, inevitable, you must be aware of what the players are doing.		As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base. If an artillery unit is capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this, inevitable, you must be aware of what the players are doing.
	'''
	Conclusion'''<br>		'''Conclusion'''<br>
	In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.		In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.

Neddiedrow at 22:58, 17 November 2006

2006-11-17T22:58:03Z

← Older revision		Revision as of 23:58, 17 November 2006
Line 1:		Line 1:
	Overview<br>		'''Overview'''<br>
	As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.		As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.
			'''
	The Mod Developer's Role In Relation To Strategy<br>		The Mod Developer's Role In Relation To Strategy'''<br>
	As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base. If an artillery unit is capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this, inevitable, you must be aware of what the players are doing.		As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base. If an artillery unit is capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this, inevitable, you must be aware of what the players are doing.
			'''
	Conclusion<br>		Conclusion'''<br>
	In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.		In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.

Neddiedrow at 22:57, 17 November 2006

2006-11-17T22:57:50Z

New page

Overview<br>
As the developer of play content for the Spring engine, you are catering to an audience of players, many of them intelligent and creative. Through trial and error with the units you include, they will establish tactics and define overhead strategies which can be employed in your mod.

The Mod Developer's Role In Relation To Strategy<br>
As a developer you have two chief responsibilities outside of your personal vision of what your mod should be. You are supposed to present a dynamic enviroment with units that promote the sort of play originally intended by your vision, but on the other hand must compensate for the actions of the player base. If an artillery unit is capable in direct combat, chances are you have let the role of the unit collapse and must rectify the lack. In order to solve issues like this, inevitable, you must be aware of what the players are doing.

Conclusion<br>
In many ways, the developer of mod content for the Spring engine defines the limits of strategy and tactics within his or her own mod. It is thus your responsibility to rectify issues which undermine the gameplay strategy you seek to promote, and this takes precedence over cosmetics or the popular opinion. Your vision, your role.