Military strategies - Revision history

86.133.187.205: /* When is a fleet catch possible? */

2006-03-07T22:04:24Z

When is a fleet catch possible?

← Older revision		Revision as of 22:04, 7 March 2006
Line 53:		Line 53:
	* You launch on their landing tick with Frigates/Destroyer fleet.		* You launch on their landing tick with Frigates/Destroyer fleet.

	*Catching a fleet with Battleships/Cruiser works similar to catching a Frigates/Destroyer fleet, only here you have the hostile fleet eta +2 so you have some more possible options. Summarising, the best chance for a fleet catch is to attack with Fighter/Corvettes on the hostile planet, just make sure you land at the same tick when their fleet returns. We have given you some examples of how to find out that, to name all possible ways in ~~theocracy~~, its not the place for here.		*Catching a fleet with Battleships/Cruiser works similar to catching a Frigates/Destroyer fleet, only here you have the hostile fleet eta +2 so you have some more possible options. Summarising, the best chance for a fleet catch is to attack with Fighter/Corvettes on the hostile planet, just make sure you land at the same tick when their fleet returns. We have given you some examples of how to find out that, to name all possible ways in detail, its not the place for here.
	When you have enough members with enough fleet and ships available, order them to tell you their complete fleet. Calculate the battle. Make sure you will kill their entire fleet not only the returning fleet. Send massive overkill fleets to avoid defence or to kill hostile defence fleets. Order your scanners to make jumpgate probe scan when the target can not receive anymore defence in time and also unit scan the defenders. Calculate the worst case scenario that could happen. If in this calculation you still lose less then the enemy, order your members to land. Also ~~increase~~ the salvage donations to the defenders in your decision. Also make sure you still have enough defence at home to defend any counters.		When you have enough members with enough fleet and ships available, order them to tell you their complete fleet. Calculate the battle. Make sure you will kill their entire fleet not only the returning fleet. Send massive overkill fleets to avoid defence or to kill hostile defence fleets. Order your scanners to make jumpgate probe scan when the target can not receive anymore defence in time and also unit scan the defenders. Calculate the worst case scenario that could happen. If in this calculation you still lose less then the enemy, order your members to land. Also include the salvage donations to the defenders in your decision. Also make sure you still have enough defence at home to defend any counters.

	===Counter attacks===		===Counter attacks===

143.195.159.26: /* Make sure you notice all incomings */

2006-02-03T19:32:02Z

Make sure you notice all incomings

← Older revision		Revision as of 19:32, 3 February 2006
Line 106:		Line 106:
	===Make sure you notice all incomings===		===Make sure you notice all incomings===

	This round 3 people can make a so called buddy group. Means 3 people can join 1 galaxy together. Advise your members to make sure at least 1 of this 3 people / member is checking gal status regularly. Each buddy group should make plans as to who is checking for incomings and at what time. Advise to your members to do it, but even 3 people wont be able to check it each tick during a 3 month period. So it's necessary your members cooperate with their gals. They should tell their galaxies which alliances they are in, what your public channel is and how to report incomings to your alliances. Therefore your DC on duty will have to be in your public all the time. Advise people also in topic of your public channel how to report incomings of your members. DCs should have op, halfop or voice in your public channel so non-members also see that this officer relates to your alliance.		This round 5 people can make a so called buddy group. Means 5 people can join 1 galaxy together. Advise your members to make sure at least 1 of this 3 people / member is checking gal status regularly. Each buddy group should make plans as to who is checking for incomings and at what time. Advise to your members to do it, but even 5 people wont be able to check it each tick during a 3 month period. So it's necessary your members cooperate with their gals. They should tell their galaxies which alliances they are in, what your public channel is and how to report incomings to your alliances. Therefore your DC on duty will have to be in your public all the time. Advise people also in topic of your public channel how to report incomings of your members. DCs should have op, halfop or voice in your public channel so non-members also see that this officer relates to your alliance.

	With regards to the composition of those buddy packs, it might be best to create a "mixed" pack with people who you know are active but are NOT in the same alliance as you. This is because it is possible that two of your alliance's buddypacks can land in the same galaxy - and if you have six people in the same galaxy and that galaxy is attacked (particularly with multiple waves), it places a massive strain on your alliance's defence ability. On the other hand, if there is only one alliance member per pack, then it is unlikely that more than two people from your alliance are in the same galaxy - so when that galaxy is attacked your alliance isnt strained anywhere near as much. Good, active people from different alliances are typically hard to find - however the best source is from a previous galaxy of yours. For example, your GC and your MoC might have been active and made friends with you during the round - ask them whether they want to form a buddypack for the next round for the reasons above.		With regards to the composition of those buddy packs, it might be best to create a "mixed" pack with people who you know are active but are NOT in the same alliance as you. This is because it is possible that two of your alliance's buddypacks can land in the same galaxy - and if you have six people in the same galaxy and that galaxy is attacked (particularly with multiple waves), it places a massive strain on your alliance's defence ability. On the other hand, if there is only one alliance member per pack, then it is unlikely that more than two people from your alliance are in the same galaxy - so when that galaxy is attacked your alliance isnt strained anywhere near as much. Good, active people from different alliances are typically hard to find - however the best source is from a previous galaxy of yours. For example, your GC and your MoC might have been active and made friends with you during the round - ask them whether they want to form a buddypack for the next round for the reasons above.

Ultimate Newbie: Added "See Also"

2006-01-07T06:02:56Z

Added "See Also"

← Older revision		Revision as of 06:02, 7 January 2006
Line 123:		Line 123:
	__FORCETOC__		__FORCETOC__

			== See Also ==
			*[[Fleet_Strategy]]
			*[[New_Player_Manual]]
			*[[New_Player_Manual:Combat]]
			*[[Battle_calculator]]

	[[Category:Strategy]]		[[Category:Strategy]]

83.160.18.126: /* What to do with not attacking members? */

2005-11-18T11:09:51Z

What to do with not attacking members?

← Older revision		Revision as of 11:09, 18 November 2005
Line 74:		Line 74:
	==What to do with not attacking members?==		==What to do with not attacking members?==

	If anyone doesn't attack with their alliance or doesn't launch on their claimed target regularly, contact the member and find out the reasons for their behaviour. Give them a warning they have to attack with their alliance regularly and/or they have to launch at their claimed target. If this warning doesn't help, think about excluding such members from attacks or about kicking them from your alliance..		If anyone doesn't attack with their alliance or doesn't launch on their claimed target regularly, contact the member and find out the reasons for their behaviour. Give them a warning they have to attack with their alliance regularly and/or they have to launch at their claimed target. If this warning doesn't help, think about excluding such members from attacks or about kicking them from your alliance.

	==Getting additional fleet power==		==Getting additional fleet power==

83.160.18.126: /* What to do with not attacking members? */

2005-11-18T11:09:24Z

What to do with not attacking members?

← Older revision		Revision as of 11:09, 18 November 2005
Line 74:		Line 74:
	==What to do with not attacking members?==		==What to do with not attacking members?==

	If anyone doesn't attack with their alliance or doesn't launch on their claimed target regularly, contact the member and find out the reasons for their behaviour. Give them a warning they have to attack with their alliance regularly and/or they have to launch at their claimed target. If this warning doesn't help, think about excluding such members from attacks or about kicking them from your alliance.		If anyone doesn't attack with their alliance or doesn't launch on their claimed target regularly, contact the member and find out the reasons for their behaviour. Give them a warning they have to attack with their alliance regularly and/or they have to launch at their claimed target. If this warning doesn't help, think about excluding such members from attacks or about kicking them from your alliance..

	==Getting additional fleet power==		==Getting additional fleet power==

Ultimate Newbie: /* Synopsis */

2005-11-07T16:57:12Z

Synopsis

← Older revision		Revision as of 16:57, 7 November 2005
Line 1:		Line 1:
	==Synopsis==		==Synopsis==

	We will introduce you to a lot of basic and advanced military tactics. For new allies it is almost always better to keep their attack and defence system simple, so it is easier to get it running.		We will introduce you to a lot of basic and advanced military tactics. For new allies it is almost always better to keep their attack and defence system simple, so it is easier to get it running.

			This thread deals with similar concepts to the [[Fleet Strategy]] thread, however this is meant to be more of a guide, whereas the other is more focused on definition and examples for [[Terminology]].

	==Basic attack strategy==		==Basic attack strategy==

220.235.18.31: /* Make sure you notice all incomings */

2005-07-19T11:21:50Z

Make sure you notice all incomings

← Older revision		Revision as of 11:21, 19 July 2005
Line 104:		Line 104:
	===Make sure you notice all incomings===		===Make sure you notice all incomings===

	This round 3 people can make a so called buddy group. Means 3 people can join 1 galaxy together. Advise your members to make sure at least 1 of this 3 people / member is checking gal status regularly. Each buddy group should make plans as to who is checking for incomings and at what time. Advise to your members to do it, but even 3 people wont be able to check it each tick during a 3 month period. So it's necessary your members cooperate with their gals. They should tell their galaxies which alliances they are in, what your public channel is and how to report incomings to your alliances. Therefore your DC on duty will have to be in your public all the time. Advise people also in topic of your public channel how to report incomings of your members. DCs should have op, halfop or voice in your public channel so non-members also see that this officer relates to your alliance.		This round 3 people can make a so called buddy group. Means 3 people can join 1 galaxy together. Advise your members to make sure at least 1 of this 3 people / member is checking gal status regularly. Each buddy group should make plans as to who is checking for incomings and at what time. Advise to your members to do it, but even 3 people wont be able to check it each tick during a 3 month period. So it's necessary your members cooperate with their gals. They should tell their galaxies which alliances they are in, what your public channel is and how to report incomings to your alliances. Therefore your DC on duty will have to be in your public all the time. Advise people also in topic of your public channel how to report incomings of your members. DCs should have op, halfop or voice in your public channel so non-members also see that this officer relates to your alliance.

			With regards to the composition of those buddy packs, it might be best to create a "mixed" pack with people who you know are active but are NOT in the same alliance as you. This is because it is possible that two of your alliance's buddypacks can land in the same galaxy - and if you have six people in the same galaxy and that galaxy is attacked (particularly with multiple waves), it places a massive strain on your alliance's defence ability. On the other hand, if there is only one alliance member per pack, then it is unlikely that more than two people from your alliance are in the same galaxy - so when that galaxy is attacked your alliance isnt strained anywhere near as much. Good, active people from different alliances are typically hard to find - however the best source is from a previous galaxy of yours. For example, your GC and your MoC might have been active and made friends with you during the round - ask them whether they want to form a buddypack for the next round for the reasons above.

	===Make sure you have always enough defence available===		===Make sure you have always enough defence available===

Cheerios at 09:39, 19 July 2005

2005-07-19T09:39:48Z

← Older revision		Revision as of 09:39, 19 July 2005
Line 102:		Line 102:
	This part will show you how to protect yourself from incomings especially at times when the member with incomings isn't online and what to do against not defending members.		This part will show you how to protect yourself from incomings especially at times when the member with incomings isn't online and what to do against not defending members.

	Make sure you notice all incomings		===Make sure you notice all incomings===

	This round 3 people can make a so called buddy group. Means 3 people can join 1 galaxy together. Advise your members to make sure at least 1 of this 3 people / member is checking gal status regularly. Each buddy group should make plans as to who is checking for incomings and at what time. Advise to your members to do it, but even 3 people wont be able to check it each tick during a 3 month period. So it's necessary your members cooperate with their gals. They should tell their galaxies which alliances they are in, what your public channel is and how to report incomings to your alliances. Therefore your DC on duty will have to be in your public all the time. Advise people also in topic of your public channel how to report incomings of your members. DCs should have op, halfop or voice in your public channel so non-members also see that this officer relates to your alliance.		This round 3 people can make a so called buddy group. Means 3 people can join 1 galaxy together. Advise your members to make sure at least 1 of this 3 people / member is checking gal status regularly. Each buddy group should make plans as to who is checking for incomings and at what time. Advise to your members to do it, but even 3 people wont be able to check it each tick during a 3 month period. So it's necessary your members cooperate with their gals. They should tell their galaxies which alliances they are in, what your public channel is and how to report incomings to your alliances. Therefore your DC on duty will have to be in your public all the time. Advise people also in topic of your public channel how to report incomings of your members. DCs should have op, halfop or voice in your public channel so non-members also see that this officer relates to your alliance.

Cheerios: toc tweaking

2005-07-19T09:14:26Z

toc tweaking

← Older revision		Revision as of 09:14, 19 July 2005
Line 3:		Line 3:
	We will introduce you to a lot of basic and advanced military tactics. For new allies it is almost always better to keep their attack and defence system simple, so it is easier to get it running.		We will introduce you to a lot of basic and advanced military tactics. For new allies it is almost always better to keep their attack and defence system simple, so it is easier to get it running.

	==Basic attack ~~strategies:~~==		==Basic attack strategy==

	At round start a new alliance should start with attacking only to get roids and grow. Order your members to build up the speed tree as fast as possible and order them to have their first ships ready at the end of protection.		At round start a new alliance should start with attacking only to get roids and grow. Order your members to build up the speed tree as fast as possible and order them to have their first ships ready at the end of protection.
Line 34:		Line 34:
	These strategies are mostly used in times of war with certain alliance(s). Try to keep these attacks as secret as possible. Involve only trusted members. If you control any gals which are doing consistent gal attacks, check which allies they have in the gal and if they can be trusted to join the attacks. This attack strategy SHOULD NOT be used before jumpgate scans are available.		These strategies are mostly used in times of war with certain alliance(s). Try to keep these attacks as secret as possible. Involve only trusted members. If you control any gals which are doing consistent gal attacks, check which allies they have in the gal and if they can be trusted to join the attacks. This attack strategy SHOULD NOT be used before jumpgate scans are available.

	==Multi Wave Attacks==		===Multi Wave Attacks===

	The most used attack strategy to take out a single planet or galaxy is the Multi Wave Attack. You attack the same planet / galaxy in waves again and again until that planet/gal's alliance is out of defence then you can raid and bash the planet / galaxy. If you plan this attack in a longer time, make sure all planets are covered in all waves. Advise your members to attack/fake attack planets that are not covered. If you setup a multi wave attack as counter or spontaneous attack, check before if you have enough members with free fleet available.		The most used attack strategy to take out a single planet or galaxy is the Multi Wave Attack. You attack the same planet / galaxy in waves again and again until that planet/gal's alliance is out of defence then you can raid and bash the planet / galaxy. If you plan this attack in a longer time, make sure all planets are covered in all waves. Advise your members to attack/fake attack planets that are not covered. If you setup a multi wave attack as counter or spontaneous attack, check before if you have enough members with free fleet available.

	==Fleet Catching==		===Fleet Catching===

	Through the changes during the last round one of the most challenging kinds of attacking was the Fleet Catching. This kind of attack means, you attack a planet at a certain time so your attacking fleets and the enemy's returning fleet are landing in the same tick at the enemy's planet. So they do not have any chance to send their fleet away (short: he can't run his fleet). This kind of attack can be planned ahead but is based on when you see a hostile planet landing on one of your members or you get info from your Intel that they landed on a planet. For fleet catches Fighter/Corvette fleets should be used because its hard to defend it, due to short travel time or ETA.		Through the changes during the last round one of the most challenging kinds of attacking was the Fleet Catching. This kind of attack means, you attack a planet at a certain time so your attacking fleets and the enemy's returning fleet are landing in the same tick at the enemy's planet. So they do not have any chance to send their fleet away (short: he can't run his fleet). This kind of attack can be planned ahead but is based on when you see a hostile planet landing on one of your members or you get info from your Intel that they landed on a planet. For fleet catches Fighter/Corvette fleets should be used because its hard to defend it, due to short travel time or ETA.

	==When is a fleet catch possible?==		===When is a fleet catch possible?===

	*Catching a hostile Fighter/Corvette fleet is only possible when you launch at them exactly in the tick they landed, countering with an attack fleet of Fighter/Corvette.		*Catching a hostile Fighter/Corvette fleet is only possible when you launch at them exactly in the tick they landed, countering with an attack fleet of Fighter/Corvette.
Line 54:		Line 54:
	When you have enough members with enough fleet and ships available, order them to tell you their complete fleet. Calculate the battle. Make sure you will kill their entire fleet not only the returning fleet. Send massive overkill fleets to avoid defence or to kill hostile defence fleets. Order your scanners to make jumpgate probe scan when the target can not receive anymore defence in time and also unit scan the defenders. Calculate the worst case scenario that could happen. If in this calculation you still lose less then the enemy, order your members to land. Also increase the salvage donations to the defenders in your decision. Also make sure you still have enough defence at home to defend any counters.		When you have enough members with enough fleet and ships available, order them to tell you their complete fleet. Calculate the battle. Make sure you will kill their entire fleet not only the returning fleet. Send massive overkill fleets to avoid defence or to kill hostile defence fleets. Order your scanners to make jumpgate probe scan when the target can not receive anymore defence in time and also unit scan the defenders. Calculate the worst case scenario that could happen. If in this calculation you still lose less then the enemy, order your members to land. Also increase the salvage donations to the defenders in your decision. Also make sure you still have enough defence at home to defend any counters.

	==Counter attacks==		===Counter attacks===

	This strategy to attempt to force defenders or attackers against your alliance to recall. If you have not completely covered your incomings , get a counter attacker. This might make the attacker recall when they can not receive enough defence. In the same way you can try this when anyone is defending against your attacks. Attack the defender also so they may recall their defence to prevent their own asteroid loses.		This strategy to attempt to force defenders or attackers against your alliance to recall. If you have not completely covered your incomings , get a counter attacker. This might make the attacker recall when they can not receive enough defence. In the same way you can try this when anyone is defending against your attacks. Attack the defender also so they may recall their defence to prevent their own asteroid loses.
Line 106:		Line 106:
	This round 3 people can make a so called buddy group. Means 3 people can join 1 galaxy together. Advise your members to make sure at least 1 of this 3 people / member is checking gal status regularly. Each buddy group should make plans as to who is checking for incomings and at what time. Advise to your members to do it, but even 3 people wont be able to check it each tick during a 3 month period. So it's necessary your members cooperate with their gals. They should tell their galaxies which alliances they are in, what your public channel is and how to report incomings to your alliances. Therefore your DC on duty will have to be in your public all the time. Advise people also in topic of your public channel how to report incomings of your members. DCs should have op, halfop or voice in your public channel so non-members also see that this officer relates to your alliance.		This round 3 people can make a so called buddy group. Means 3 people can join 1 galaxy together. Advise your members to make sure at least 1 of this 3 people / member is checking gal status regularly. Each buddy group should make plans as to who is checking for incomings and at what time. Advise to your members to do it, but even 3 people wont be able to check it each tick during a 3 month period. So it's necessary your members cooperate with their gals. They should tell their galaxies which alliances they are in, what your public channel is and how to report incomings to your alliances. Therefore your DC on duty will have to be in your public all the time. Advise people also in topic of your public channel how to report incomings of your members. DCs should have op, halfop or voice in your public channel so non-members also see that this officer relates to your alliance.

	==Make sure you have always enough defence available==		===Make sure you have always enough defence available===

	That's for sure the most difficult part. Therefore you need to give out some clear rules. First of all you should count the defence activity of each member. This can be done in web based tools, IRC bots and on normal text files, Excel files or in your Officer forums. Additionally, you should advise your members to have always a certain part of their fleet at home for defence, of course always a fleet slot open for defence. So your members shouldn't be allowed to attack with 3 fleets if you want to have a working defence. For offensive attacking alliances members should be ordered to have 10-25% of their fleet as defence fleet available, defensive and counter strategies should order their members to keep 25-50% of their whole fleet at home for defence and counters.		That's for sure the most difficult part. Therefore you need to give out some clear rules. First of all you should count the defence activity of each member. This can be done in web based tools, IRC bots and on normal text files, Excel files or in your Officer forums. Additionally, you should advise your members to have always a certain part of their fleet at home for defence, of course always a fleet slot open for defence. So your members shouldn't be allowed to attack with 3 fleets if you want to have a working defence. For offensive attacking alliances members should be ordered to have 10-25% of their fleet as defence fleet available, defensive and counter strategies should order their members to keep 25-50% of their whole fleet at home for defence and counters.

Cheerios: added toc, cleaning up, added to Strategy category etc.

2005-07-19T09:06:49Z

added toc, cleaning up, added to Strategy category etc.

Show changes