Analyze Graphs - Revision history

Fizzer at 02:36, 18 April 2026

2026-04-18T02:36:08Z

← Older revision		Revision as of 02:36, 18 April 2026
Line 27:		Line 27:
	* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The probability graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.		* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The probability graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.
	* The Probability graph is generated by running the attack thousands of times for each number of attacking armies. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.		* The Probability graph is generated by running the attack thousands of times for each number of attacking armies. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.
	* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, ~~Warzone~~ simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2.		* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, War.app simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2.

	==See Also ==		==See Also ==

DanWL60 at 01:45, 13 November 2023

2023-11-13T01:45:52Z

← Older revision		Revision as of 01:45, 13 November 2023
Line 32:		Line 32:
	* [[Combat Basics]]		* [[Combat Basics]]
	* [[Luck Modifier]]		* [[Luck Modifier]]

			[[Category:Gameplay]]

Fizzer at 20:22, 12 April 2018

2018-04-12T20:22:18Z

← Older revision		Revision as of 20:22, 12 April 2018
Line 1:		Line 1:
	The Analyze Graphs window helps you figure out how many armies you should attack with. ~~It shows two of three graphs: the Probability Graph, Army Loss, and the No-Luck graph graph.~~ To find this window, ~~start to issue an attack and click~~ the ~~Analyze button~~, or ~~select Analyze from~~ a game~~'s menu~~.		The Analyze Graphs window helps you figure out how many armies you should attack or defend with. To find this window, select Analyze Attack from the game menu, or in a luck game you can click Analyze when making an attack.

	If the game you're viewing these graphs from uses no-luck combat settings, you'll see the no-luck graph, otherwise you'll see the probability graph~~. The Army Loss graph is always shown~~.		If the game you're viewing these graphs from uses no-luck combat settings, you'll see the no-luck graph, otherwise you'll see the probability graph.

	To understand these graphs, you should first understand the [[combat basics]].		To understand these graphs, you should first understand the [[combat basics]].

	The first thing you should do after opening the Analyze Attack window is to set the number of armies you expect the defender to have in the text box at the top. ~~This number defaults to the number of defenders you opened the dialog from~~, ~~but remember that~~ the defender gets a chance to add armies before the attack takes place, so you may wish to predict how many your opponent will add. When attacking [[neutral]], you can be assured the numbers here will be accurate. After changing this number, click the Recalculate button.		The first thing you should do after opening the Analyze Attack window is to set the number of armies you expect the defender to have in the text box at the top. Remember, the defender gets a chance to add armies before the attack takes place, so you may wish to predict how many your opponent will add. When attacking [[neutral]], you can be assured the numbers here will be accurate. After changing this number, click the Recalculate button.

	==No-Luck Graph==		==No-Luck Graph==

	https://d32kaghj56y4ei.cloudfront.net/static/img/~~NoLuckGraph~~.png		https://d32kaghj56y4ei.cloudfront.net/static/img/NoLuckGraph2.png

	The no-luck graph only appears in games that have no combat luck (i.e. the [[luck modifier]] is set to 0% and the [[rounding mode]] is set to straight round). This graph shows you exactly how many armies you need to attack with to capture the territory for several different defending amounts.		The no-luck graph only appears in games that have no combat luck (i.e. the [[luck modifier]] is set to 0% and the [[rounding mode]] is set to straight round). This graph shows you exactly how many armies you need to attack with to capture the territory for several different defending amounts.

	You can ~~hover your mouse cursor over each circle~~ on ~~this graph~~ to ~~clarify what that point in the graph means~~.		You can also switch to the Defending tab at the top to see how many armies are killed on defense. This is useful if you're trying to ensure you hold a territory, to see how many armies attackers will lose when attacking you.

	==Probability Graph==		==Probability Graph==

	https://~~d2wcw7vp66n8b3~~.cloudfront.net/~~Images~~/ProbabilityGraph.png		https://d32kaghj56y4ei.cloudfront.net/static/img/ProbabilityGraph.png

	The probability graph shows you percent chance you have to capture a territory based on how many armies you attack with. In this example, we have entered that the defender has 50 armies. To be 80% sure that we capture a territory that has 50 armies, we look at the graph where the vertical axis reads 80. This corresponds to about 87 armies.		The probability graph shows you percent chance you have to capture a territory based on how many armies you attack with. In this example, we have entered that the defender has 40 armies. To be 98% sure that we capture a territory that has 40 armies, we look at the graph where the vertical axis reads 98. This corresponds to about 68 armies.

	You can hover your mouse cursor over each circle on this graph to clarify what that point in the graph means.		You can hover your mouse cursor over each circle on this graph to clarify what that point in the graph means.

	~~==Army Loss Graph==~~

	~~https://d2wcw7vp66n8b3.cloudfront.net/Images/ArmyLossGraph.png~~

	~~The army loss graph shows you how many armies each player will lose based on how many armies you attack with. In this example, we have entered that the defender has 50 armies.~~

	Take note of point A where the lines cross. This is the point where the defender loses the same number of armies as the attacker. In other words, an attack with this number of armies won't favor either player. Everything to the right (more attacking armies) is beneficial to the attacker, and everything to the left (fewer attacking armies) is beneficial to the defender.

	~~Point B is the point that is most beneficial to the defender. At this point, the defender kills all of the attacking armies while losing far fewer.~~

	Point C is the point that is most beneficial to the attacker. At this point, all of the defending armies are killed and the territory is captured. Adding more armies beyond this won't impact the result.

	==Notes==		==Notes==

	* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The probability graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.		* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The probability graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.
	* The data presented is not affected by which territories were selected when it was opened, other than to default the defending armies text box at the top.
	* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may vary based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.
	* The Probability graph is generated by running the attack thousands of times for each number of attacking armies. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.		* The Probability graph is generated by running the attack thousands of times for each number of attacking armies. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.
	* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, Warzone simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2.		* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, Warzone simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2.

			==See Also ==
			* [[Combat Basics]]
			* [[Luck Modifier]]

Fizzer at 03:39, 13 November 2017

2017-11-13T03:39:11Z

← Older revision		Revision as of 03:39, 13 November 2017
Line 41:		Line 41:
	* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may vary based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.		* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may vary based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.
	* The Probability graph is generated by running the attack thousands of times for each number of attacking armies. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.		* The Probability graph is generated by running the attack thousands of times for each number of attacking armies. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.
	* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, ~~WarLight~~ simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2.		* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, Warzone simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2.

Fizzer at 23:38, 18 December 2014

2014-12-18T23:38:41Z

← Older revision		Revision as of 23:38, 18 December 2014
Line 9:		Line 9:
	==No-Luck Graph==		==No-Luck Graph==

	~~http~~://~~s3cdn~~.~~warlight~~.net/static/img/NoLuckGraph.png		https://d32kaghj56y4ei.cloudfront.net/static/img/NoLuckGraph.png

	The no-luck graph only appears in games that have no combat luck (i.e. the [[luck modifier]] is set to 0% and the [[rounding mode]] is set to straight round). This graph shows you exactly how many armies you need to attack with to capture the territory for several different defending amounts.		The no-luck graph only appears in games that have no combat luck (i.e. the [[luck modifier]] is set to 0% and the [[rounding mode]] is set to straight round). This graph shows you exactly how many armies you need to attack with to capture the territory for several different defending amounts.
Line 17:		Line 17:
	==Probability Graph==		==Probability Graph==

	~~http~~://~~cdn~~.~~warlight~~.net/Images/ProbabilityGraph.png		https://d2wcw7vp66n8b3.cloudfront.net/Images/ProbabilityGraph.png

	The probability graph shows you percent chance you have to capture a territory based on how many armies you attack with. In this example, we have entered that the defender has 50 armies. To be 80% sure that we capture a territory that has 50 armies, we look at the graph where the vertical axis reads 80. This corresponds to about 87 armies.		The probability graph shows you percent chance you have to capture a territory based on how many armies you attack with. In this example, we have entered that the defender has 50 armies. To be 80% sure that we capture a territory that has 50 armies, we look at the graph where the vertical axis reads 80. This corresponds to about 87 armies.
Line 25:		Line 25:
	==Army Loss Graph==		==Army Loss Graph==

	~~http~~://~~cdn~~.~~warlight~~.net/Images/ArmyLossGraph.png		https://d2wcw7vp66n8b3.cloudfront.net/Images/ArmyLossGraph.png

	The army loss graph shows you how many armies each player will lose based on how many armies you attack with. In this example, we have entered that the defender has 50 armies.		The army loss graph shows you how many armies each player will lose based on how many armies you attack with. In this example, we have entered that the defender has 50 armies.

Fizzer at 05:56, 11 November 2014

2014-11-11T05:56:08Z

← Older revision		Revision as of 05:56, 11 November 2014
Line 1:		Line 1:
	The Analyze Graphs window helps you figure out how many armies you should attack with. It ~~is divided into~~ two graphs: the Probability Graph and the ~~Army Loss~~ graph. To find this window, start to issue an attack and click the Analyze button.		The Analyze Graphs window helps you figure out how many armies you should attack with. It shows two of three graphs: the Probability Graph, Army Loss, and the No-Luck graph graph. To find this window, start to issue an attack and click the Analyze button, or select Analyze from a game's menu.

			If the game you're viewing these graphs from uses no-luck combat settings, you'll see the no-luck graph, otherwise you'll see the probability graph. The Army Loss graph is always shown.

	To understand these graphs, you should first understand the [[combat basics]].		To understand these graphs, you should first understand the [[combat basics]].

	The first thing you should do after opening the Analyze Attack window is to set the number of armies you expect the defender to have in the text box at the top. This number defaults to the number of defenders you opened the dialog from, but remember that the defender gets a chance to add armies before the attack takes place, so you may wish to predict how many your opponent will add. When attacking [[neutral]], you can be assured the numbers here will be accurate. After changing this number, click the Recalculate button.		The first thing you should do after opening the Analyze Attack window is to set the number of armies you expect the defender to have in the text box at the top. This number defaults to the number of defenders you opened the dialog from, but remember that the defender gets a chance to add armies before the attack takes place, so you may wish to predict how many your opponent will add. When attacking [[neutral]], you can be assured the numbers here will be accurate. After changing this number, click the Recalculate button.

			==No-Luck Graph==

			http://s3cdn.warlight.net/static/img/NoLuckGraph.png

			The no-luck graph only appears in games that have no combat luck (i.e. the [[luck modifier]] is set to 0% and the [[rounding mode]] is set to straight round). This graph shows you exactly how many armies you need to attack with to capture the territory for several different defending amounts.

			You can hover your mouse cursor over each circle on this graph to clarify what that point in the graph means.

	==Probability Graph==		==Probability Graph==

	http://warlight.net/Images/ProbabilityGraph.png		http://cdn.warlight.net/Images/ProbabilityGraph.png

	The probability graph shows you percent chance you have to capture a territory based on how many armies you attack with. In this example, we have entered that the defender has 50 armies. To be 80% sure that we capture a territory that has 50 armies, we look at the graph where the vertical axis reads 80. This corresponds to about 87 armies.		The probability graph shows you percent chance you have to capture a territory based on how many armies you attack with. In this example, we have entered that the defender has 50 armies. To be 80% sure that we capture a territory that has 50 armies, we look at the graph where the vertical axis reads 80. This corresponds to about 87 armies.

	You can hover over each circle on this graph to clarify what that point in the graph means.		You can hover your mouse cursor over each circle on this graph to clarify what that point in the graph means.

	==Army Loss Graph==		==Army Loss Graph==

	http://warlight.net/Images/ArmyLossGraph.png		http://cdn.warlight.net/Images/ArmyLossGraph.png

	The army loss graph shows you how many armies each player will lose based on how many armies you attack with. In this example, we have entered that the defender has 50 armies.		The army loss graph shows you how many armies each player will lose based on how many armies you attack with. In this example, we have entered that the defender has 50 armies.

Fizzer at 21:42, 24 March 2013

2013-03-24T21:42:23Z

← Older revision		Revision as of 21:42, 24 March 2013
Line 29:		Line 29:
	* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The probability graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.		* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The probability graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.
	* The data presented is not affected by which territories were selected when it was opened, other than to default the defending armies text box at the top.		* The data presented is not affected by which territories were selected when it was opened, other than to default the defending armies text box at the top.
	* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may ~~be off~~ based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.		* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may vary based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.
	* The Probability graph is generated by running the attack thousands of times for each ~~scenario~~. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.		* The Probability graph is generated by running the attack thousands of times for each number of attacking armies. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.
	* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, WarLight simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2~~, etc~~.		* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, WarLight simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2.

Fizzer at 21:40, 24 March 2013

2013-03-24T21:40:17Z

← Older revision		Revision as of 21:40, 24 March 2013
Line 27:		Line 27:
	==Notes==		==Notes==

	* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The ~~top~~ graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.		* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The probability graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.
	* The data presented is not affected by which territories were selected when it was opened, other than to default the defending armies text box at the top.		* The data presented is not affected by which territories were selected when it was opened, other than to default the defending armies text box at the top.
	* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may be off based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.		* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may be off based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.
	* The Probability graph is generated by running the attack thousands of times for each scenario. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.		* The Probability graph is generated by running the attack thousands of times for each scenario. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.
	* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, WarLight simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2, etc.		* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, WarLight simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2, etc.

Fizzer at 21:40, 24 March 2013

2013-03-24T21:40:04Z

← Older revision		Revision as of 21:40, 24 March 2013
Line 27:		Line 27:
	==Notes==		==Notes==

	* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The top graph is also affected by the [[luck modifier\|luck percentage]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.		* Both graphs are affected by the [[offense and defense kill rates]] set for the game you are looking at. The top graph is also affected by the [[luck modifier\|luck percentage]] and [[rounding mode]] set for the game. Therefore, you cannot assume that the numbers you see in one game will hold true for another game since the [[settings]] may be different.
	* The data presented is not affected by which territories were selected when it was opened, other than to default the defending armies text box at the top.		* The data presented is not affected by which territories were selected when it was opened, other than to default the defending armies text box at the top.
	* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may be off based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.		* The Army Loss graph presents the most likely outcome of the attack. The actual outcome may be off based on the random factor, but since that's impossible to predict it's logical to assume that the most likely outcome is what will happen when forming your plans.
	* The Probability graph is generated by running the attack thousands of times for each scenario. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.		* The Probability graph is generated by running the attack thousands of times for each scenario. Therefore, the numbers could change slightly from one run to the next. However, they are typically only off by one percent at most.
	* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, WarLight simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2, etc.		* Astute players will notice that the probability graph dips a bit where the number of attacking armies equals the number of defending armies. This is most easily seen when the number of defenders is 1 or 2. This is not a glitch and does indeed reflect the true probability. This is due to an edge case in the combat system. If equal numbers fight and both sides kill the maximum number of armies possible, and since every territory must have at least one army, there would be no armies left to control the captured territory. In this event, WarLight simply resurrects one defending army and allows it to retain control of the territory. For this reason, it's rarely a good idea to attack a 1 with 1 or to attack a 2 with 2, etc.

24.207.135.113: /* Probability Graph - spelling fix */

2012-09-15T15:49:12Z

Probability Graph - spelling fix

← Older revision		Revision as of 15:49, 15 September 2012
Line 9:		Line 9:
	http://warlight.net/Images/ProbabilityGraph.png		http://warlight.net/Images/ProbabilityGraph.png

	The probability graph shows you percent ~~change~~ you have to capture a territory based on how many armies you attack with. In this example, we have entered that the defender has 50 armies. To be 80% sure that we capture a territory that has 50 armies, we look at the graph where the vertical axis reads 80. This corresponds to about 87 armies.		The probability graph shows you percent chance you have to capture a territory based on how many armies you attack with. In this example, we have entered that the defender has 50 armies. To be 80% sure that we capture a territory that has 50 armies, we look at the graph where the vertical axis reads 80. This corresponds to about 87 armies.

	You can hover over each circle on this graph to clarify what that point in the graph means.		You can hover over each circle on this graph to clarify what that point in the graph means.