Microsoft Visual Studio Solution File, Format Version 12.00
# XCOM ModBuddy Solution File, Format Version 11.00
VisualStudioVersion = 12.0.21005.1
MinimumVisualStudioVersion = 10.0.40219.1
Project("{5DAE07AF-E217-45C1-8DE7-FF99D6011E8A}") = "RWRealisticAimingAnglesHL", "RWRealisticAimingAnglesHL\RWRealisticAimingAnglesHL.x2proj", "{9D0C7CAC-0EC7-4756-B4F7-A2B3B57C675B}"
EndProject
Global
	GlobalSection(SolutionConfigurationPlatforms) = preSolution
		Debug|XCOM 2 = Debug|XCOM 2
		Default|XCOM 2 = Default|XCOM 2
	EndGlobalSection
	GlobalSection(ProjectConfigurationPlatforms) = postSolution
		{9D0C7CAC-0EC7-4756-B4F7-A2B3B57C675B}.Debug|XCOM 2.ActiveCfg = Debug|XCOM 2
		{9D0C7CAC-0EC7-4756-B4F7-A2B3B57C675B}.Debug|XCOM 2.Build.0 = Debug|XCOM 2
		{9D0C7CAC-0EC7-4756-B4F7-A2B3B57C675B}.Default|XCOM 2.ActiveCfg = Default|XCOM 2
		{9D0C7CAC-0EC7-4756-B4F7-A2B3B57C675B}.Default|XCOM 2.Build.0 = Default|XCOM 2
	EndGlobalSection
	GlobalSection(SolutionProperties) = preSolution
		HideSolutionNode = FALSE
	EndGlobalSection
EndGlobal


Microsoft Visual Studio Solution File, Format Version 12.00
# XCOM ModBuddy Solution File, Format Version 11.00
VisualStudioVersion = 12.0.21005.1
MinimumVisualStudioVersion = 10.0.40219.1
Project("{5DAE07AF-E217-45C1-8DE7-FF99D6011E8A}") = "RWRealisticAimingAnglesHL", "RWRealisticAimingAnglesHL\RWRealisticAimingAnglesHL.x2proj", "{FBE22F50-CBA1-4451-B6ED-E4AFCD956C90}"
EndProject
Global
	GlobalSection(SolutionConfigurationPlatforms) = preSolution
		Debug|XCOM 2 = Debug|XCOM 2
		Default|XCOM 2 = Default|XCOM 2
	EndGlobalSection
	GlobalSection(ProjectConfigurationPlatforms) = postSolution
		{FBE22F50-CBA1-4451-B6ED-E4AFCD956C90}.Debug|XCOM 2.ActiveCfg = Debug|XCOM 2
		{FBE22F50-CBA1-4451-B6ED-E4AFCD956C90}.Debug|XCOM 2.Build.0 = Debug|XCOM 2
		{FBE22F50-CBA1-4451-B6ED-E4AFCD956C90}.Default|XCOM 2.ActiveCfg = Default|XCOM 2
		{FBE22F50-CBA1-4451-B6ED-E4AFCD956C90}.Default|XCOM 2.Build.0 = Default|XCOM 2
	EndGlobalSection
	GlobalSection(SolutionProperties) = preSolution
		HideSolutionNode = FALSE
	EndGlobalSection
EndGlobal

class Override_X2AbilityToHitCalc_StandardAim extends X2AbilityToHitCalc_StandardAim config (RWRealisticAimingAngles);

class Override_X2AbilityToHitCalc_StandardAim extends X2AbilityToHitCalc_StandardAim config (RWRealisticAimingAnglesHL);

						if (VisInfo.TargetCover != CT_MidLevel) {
							for (i=1;i==20;++i){

						if (VisInfo.TargetCover != CT_MidLevel)
						{
							for (i=1;i==20;++i)
							{

						}}

							}
                                                }

[RWRealisticAimingAngles.Override_X2AbilityToHitCalc_StandardAim]
;My "Good Angle" Bonus against Cover is not absurdly applied ONLY by my troops, not ONLY within a distance of 11 Tiles, not ONLY to Horizontal Angles but also to Vertical Angles (instead of the absurdly constant +20 Height Advantage) not ONLY as a proportional Bonus against lower targets but also as a proportional Malus against higher targets and my higher targets can now FINALLY realistically use as Cover the "buildings' ceilings" they're standing on (depending on how much of the border "hides them" from the shooter's view) and my Low Covers now FINALLY count as "Far Cover" when not immediately in front of the target but still partially hiding him from the shooter's view, yours?
;RESTRICTIONS MY ASS ;)
ApplyGoodAngleBonusEvenFartherThan11TilesAway = true
ApplyGoodAngleBonusNotOnlyForXComSoldiersButAlsoForAnyoneShooting = true
;Donations: paypal.me/krumiro
;GOOD ANGLE (HORIZONTAL ANGLE BONUS)
;You can change at which angle the Good Angle Bonus "starts and ends", either within a "full range" (from Perfectly Frontal to Fully Flanking) or within a shorter range.
;Personally, from 45 degrees (Half Flanking) to 5 degrees (almost Fully Flanking) seems appropriate BECAUSE when people use a tree (for example) to take High Cover, they don't just place themselves just North, East, South or West especially when the shooter is aiming from South-West but instead they realistically "conveniently adjust" their position "slightly" rotating around the tree (or slightly shifting behind the wall) as much as they can.
MinimumGoodAngleBonusCoverReductionPercentage = 0   ;(  0% means Cover unchanged)
MaximumGoodAngleBonusCoverReductionPercentage = 100 ;(100% means Cover completely ignored)
MinimumGoodAngleBonusStartsAtThisHorizontalAngleBetweenLineOfFireAndCoverSurface = 45 ;(90 means Fully Frontal  )
MaximumGoodAngleBonusEndsAtThisHorizontalAngleBetweenLineOfFireAndCoverSurface   =  5 ;( 0 means Fully Flanaking)
;HEIGHT ADVANTAGE (VERTICAL ANGLE BONUS AGAINST LOWER TARGETS IN COVER)
;Why just horizontal aiming angles had to affect cover protection?
;I always hated Default-XCom2 +20 Height Advantage not only for being absurdly constant independently from the vertical angle but also for being absurdly applied to anyone independently by their taking cover or not. Nonsense, had to stop. Now that target's Low/High Cover will be protective as intended only if at the same height of the shooter and gradually decreasing with increasing vertical aiming angle (from 0deg to 90deg).
;Collateral effect: "tall shooters" (such as Sparks or Sectopods) have a natural Height Advantage Aiming Bonus proportional to the height difference with the Target. ;)
;Change to your desired values but, personally, the Target's Cover should be completely ignored (100% Cover Reduction) not when the Shooter is completely above the target (0deg = Fully Vertical Line of Fire) but a little bit before (30deg).
ApplyVerticalGoodAngleAgainstLowerTargetAsProportionalHeightAdvantage    = true
MinimumHeightAdvantageBonusCoverReductionPercentage = 0   ;(  0% means Cover unchanged)
MaximumHeightAdvantageBonusCoverReductionPercentage = 100 ;(100% means Cover completely ignored)
MinimumHeightAdvantageBonusStartsAtThisVerticalAngleBetweenLineOfFireAndCoverSurface = 90 ;(90 means Fully Horizontal Line of Fire) 
MaximumHeightAdvantageBonusEndsAtThisVerticalAngleBetweenLineOfFireAndCoverSurface   = 30 ;( 0 means Fully Vertical   Line of Fire)
;HEIGHT DISADVANTAGE (VERTICAL ANGLE MALUS AGAINST HIGHER TARGETS)
ApplyVerticalBadAngleAgainstHigherTargetAsProportionalHeightDisadvantage = true
;The opposite is true for Targets in cover above the Shooter. This proportional Height Disadvantage Malus gives additional protection (negative value to the shooter) proportionally to how much the low cover on top of a building hides the target more than usual because of the vertical line of sight.
;YES! Finally a Building's or Mountain's Border now works as Cover! And the Cover Value it gives varies depending on how much the Border hides the target from the shooter's view, and therefore the more the target is away from the Border, the more he is hidden. ;)
;With the two effects combined if, for example, a target taking Low Cover on top of a building "takes a step back" (1 tile) he will receive much more that +20 Cover.
;HEIGHT ADVANTAGE/DISADVANTAGE DIFFICULTY BALANCE
;Therefore, although climbing on buildings/mountains doesn't give anymore a "constant" +20 Bonus against "anyone" below (but a realistically "proportional" one against lower enemies "in cover") it is compensated by receiving a lot of realistically proportional extra cover protection, thus elegantly preserving the difficulty balance originally intended by Firaxis and still making high positions as favourable as before (but in a realistic way). ;)
;HORIZONTAL AND VERTICAL ANGLE BONUSES COMBINED
;Automatic High Cover “Type Detection”!: “Simple”, “Tall”, “Long” High Cover or a combination of them. Determining whether to apply only Horizontal Aiming Good Angle Bonus, only Vertical Aiming Height Advantage Bonus or both simultaneously. For example: On a Target taking a “Simple” High Cover (such as a 1-Tile Rock) both Good Angle and Height Advantage Bonuses can as before be applied (BUT never cumulatively higher than the Cover Value they are reducing, for example: -40LowCover +28GoodAngle +12HeightAdvantage), on a Target taking instead a “Tall” High Cover (such as a tall Tree/Pillar) only Horizontal Aiming Angle Bonus can be applied (for as high as the Shooter climbs, the vertical Tree/Pillar still never offers a Vertical Angle Bonus), on a Target taking instead a “Long” High Cover (such as a long fence, standing the Target NOT at its edge) only Vertical Good Angle Bonus can with this update be applied (for as much as the Shooter on the building tries to “partially flank” the Target, the long fence still never offers an Horizontal Good Angle).
;FAR COVER
AllowFarCoverToGiveSomeCoverProtection = true
;Personal concept: Low Cover between shooter and target but not immediately near target. Who said that your soldier cannot use that trashcan as cover only because he is not immediately in front of it? Nonsense, in my book if something is partially hiding you from view then it's partially giving you cover (between +1 and +20, proportionally to how far/much that far Low Cover is hiding the target from the shooter's view). ;)
;Far Cover is applied obviously only to Targets NOT already taking cover (because the Far Cover would not cover them but their already existing Cover) EXCEPT if they are taking Cover AND a Good Angle is reducing that Cover Value: Only in that case Far Cover can help the Target BUT never with a value higher than the existing Good Angle Bonus (So that the Target will never have cumulative Cover Values above 40/20). Example: 40HighCover -14GoodAngle +14FarCoverPreventingGoodAngle (Instead of +19FarCover). ;)
;EXTENDED COVER
;Other personal concept: High Cover extended by Low Cover: When a Target taking High Cover “with a Low Cover next to it” is being partially flanked, then the Horizontal Good Angle reducing the High Cover will be only “half applied” since the the Shooter is only flanking the “upper half” of the Target while his “lower half” is still protected by the Extended Low Cover. (Example: -40HighCover +38GoodAngle -19ExtendedLowCoverPreventingGoodAngle). This way a Target using High/Low Covers on 2 sides, the more he is flanked, the more his cover will be reduced from 40 to 20 (realistically gradually switching from High to Low Cover). 
;CHECK TRUE LINE OF SIGHT
GiveHitChanceZeroWhenTargetableEnemiesAreInsteadNotTrulyInLineOfSight = true
;Personally designed check to prevent shooting aliens behind walls. Why give 0% Hit Chance instead of simply preventing to target? Because I like that it gives me the opportunity to shoot anyway which, sometimes as a result, does environmental damage sometimes destroying or punching a hole in "what was blocking my view" for, possibly, a second regular shot in the next turn or by a squad-mate.
;FAIRLY APPLIED
;The modifiers apply also to Enemies targeting your Squad-mates (oR it wouldn't be fair) and don't apply against units who refuse to or cannot take cover (Sparks, Faceless, Berserkers...) or who are unaware of your presence (therefore not "taking" cover because unaware of danger) unless altering this variable below: 
OnlyAlertedTargetsCanHaveTheExtraProtectionOfFarCoverAndHeightDisadvantage = true
;CLASS OVERRIDES: 
;+ModClassOverrides=(BaseGameClass="X2AbilityToHitCalc_StandardAim"

[RWRealisticAimingAnglesHL.Override_X2AbilityToHitCalc_StandardAim]
;My "Good Angle" Bonus against Cover is not absurdly applied ONLY by my troops, not ONLY within a distance of 11 Tiles, not ONLY to Horizontal Angles but also to Vertical Angles (instead of the absurdly constant +20 Height Advantage) not ONLY as a proportional Bonus against lower targets but also as a proportional Malus against higher targets and my higher targets can now FINALLY realistically use as Cover the "buildings' ceilings" they're standing on (depending on how much of the border "hides them" from the shooter's view) and my Low Covers now FINALLY count as "Far Cover" when not immediately in front of the target but still partially hiding him from the shooter's view, yours?

;EU ROLLS: XCOM 1 DICE-ROLL SYSTEM
UseIndividualConsecutiveRollsForHitChanceCriticalChanceDodgeChance = false ;"false" will ignore the other 2 variables
PrioritizeCriticalChanceOverDodgeChance = true ; Hit?Yes-->Critical?No-->Dodge? OR Hit?Yes-->Dodge?No-->Critical?
AlwaysRollForBothDodgeAndCriticalEvenWhenOneUnsuccesful = false ;If both successful then they cancel out becoming Normal Hit
;Example: 90% Hit Chance with 10% Critical Chance on a Chrissalyd with 20% Dodge Chance
;XCOM1 - 3Rolls: FirstRoll90%Hit --> SecondRoll(10%of90%=)9%CriticalHit --> ThirdRoll(20%of81%=)16%Dodge
;XCOM1 - 3Rolls: (10%of 90%=) 9%CriticalHit, (90%- 9%-16%=)65%NormalHit, (20%of 81%=)16%Dodge, (100%-90%=)10%Miss
;XCOM2 - 1Roll : (10%of100%=)10%CriticalHit, (90%-10%-20%=)60%NormalHit, (20%of100%=)20%Dodge, (100%-90%=)10%Miss
;Example: 30% Hit Chance with 10% Critical Chance on a Chrissalyd with 20% Dodge Chance
;XCOM1 - 3Rolls: FirstRoll30%Hit --> SecondRoll(10%of30%=)3%CriticalHit --> ThirdRoll(20%of27%=)5%Dodge
;XCOM1 - 3Rolls: (10%of 30%=) 3%CriticalHit, (30%- 3%- 5%=)22%NormalHit, (20%of 27%=) 5%Dodge, (100%-30%=)70%Miss
;XCOM2 - 1Roll : (10%of100%=)10%CriticalHit, (30%-10%-20%=) 0%NormalHit, (20%of100%=)20%Dodge, (100%-30%=)70%Miss
;In XCOM2 the %Hit is "eaten" from the "left" by %Critical and from the "right" by Dodge "cutting" the %Hit into 3 parts %CriticalHit+%NormalHit+%Dodge and if  %Dodge is large enough then it can "eat" all of the remaining %NormalHit or even some of the %CriticalHit
;EXTRA DICE-ROLL OPTIONS
GuaranteedHitsCannotDodge = false
IndirectFireGuaranteesHit = false 

;RESTRICTIONS MY ASS ;)
ApplyGoodAngleBonusEvenFartherThan11TilesAway = true
ApplyGoodAngleBonusNotOnlyForXComSoldiersButAlsoForAnyoneShooting = true
;Donations: paypal.me/krumiro
;GOOD ANGLE (HORIZONTAL ANGLE BONUS)
;You can change at which angle the Good Angle Bonus "starts and ends", either within a "full range" (from Perfectly Frontal to Fully Flanking) or within a shorter range.
;Personally, from 45 degrees (Half Flanking) to 5 degrees (almost Fully Flanking) seems appropriate BECAUSE when people use a tree (for example) to take High Cover, they don't just place themselves just North, East, South or West especially when the shooter is aiming from South-West but instead they realistically "conveniently adjust" their position "slightly" rotating around the tree (or slightly shifting behind the wall) as much as they can.
MinimumGoodAngleBonusCoverReductionPercentage = 0   ;(  0% means Cover unchanged)
MaximumGoodAngleBonusCoverReductionPercentage = 100 ;(100% means Cover completely ignored)
MinimumGoodAngleBonusStartsAtThisHorizontalAngleBetweenLineOfFireAndCoverSurface = 45 ;(90 means Fully Frontal  )
MaximumGoodAngleBonusEndsAtThisHorizontalAngleBetweenLineOfFireAndCoverSurface   =  5 ;( 0 means Fully Flanaking)
;HEIGHT ADVANTAGE (VERTICAL ANGLE BONUS AGAINST LOWER TARGETS IN COVER)
;Why just horizontal aiming angles had to affect cover protection?
;I always hated Default-XCom2 +20 Height Advantage not only for being absurdly constant independently from the vertical angle but also for being absurdly applied to anyone independently by their taking cover or not. Nonsense, had to stop. Now that target's Low/High Cover will be protective as intended only if at the same height of the shooter and gradually decreasing with increasing vertical aiming angle (from 0deg to 90deg).
;Collateral effect: "tall shooters" (such as Sparks or Sectopods) have a natural Height Advantage Aiming Bonus proportional to the height difference with the Target. ;)
;Change to your desired values but, personally, the Target's Cover should be completely ignored (100% Cover Reduction) not when the Shooter is completely above the target (0deg = Fully Vertical Line of Fire) but a little bit before (30deg).
ApplyVerticalGoodAngleAgainstLowerTargetAsProportionalHeightAdvantage    = true
MinimumHeightAdvantageBonusCoverReductionPercentage = 0   ;(  0% means Cover unchanged)
MaximumHeightAdvantageBonusCoverReductionPercentage = 100 ;(100% means Cover completely ignored)
MinimumHeightAdvantageBonusStartsAtThisVerticalAngleBetweenLineOfFireAndCoverSurface = 90 ;(90 means Fully Horizontal Line of Fire)
MaximumHeightAdvantageBonusEndsAtThisVerticalAngleBetweenLineOfFireAndCoverSurface   = 30 ;( 0 means Fully Vertical   Line of Fire)
;HEIGHT DISADVANTAGE (VERTICAL ANGLE MALUS AGAINST HIGHER TARGETS)
ApplyVerticalBadAngleAgainstHigherTargetAsProportionalHeightDisadvantage = true
;The opposite is true for Targets in cover above the Shooter. This proportional Height Disadvantage Malus gives additional protection (negative value to the shooter) proportionally to how much the low cover on top of a building hides the target more than usual because of the vertical line of sight.
;YES! Finally a Building's or Mountain's Border now works as Cover! And the Cover Value it gives varies depending on how much the Border hides the target from the shooter's view, and therefore the more the target is away from the Border, the more he is hidden. ;)
;With the two effects combined if, for example, a target taking Low Cover on top of a building "takes a step back" (1 tile) he will receive much more that +20 Cover.
;HEIGHT ADVANTAGE/DISADVANTAGE DIFFICULTY BALANCE
;Therefore, although climbing on buildings/mountains doesn't give anymore a "constant" +20 Bonus against "anyone" below (but a realistically "proportional" one against lower enemies "in cover") it is compensated by receiving a lot of realistically proportional extra cover protection, thus elegantly preserving the difficulty balance originally intended by Firaxis and still making high positions as favourable as before (but in a realistic way). ;)
;HORIZONTAL AND VERTICAL ANGLE BONUSES COMBINED
;Automatic High Cover “Type Detection”!: “Simple”, “Tall”, “Long” High Cover or a combination of them. Determining whether to apply only Horizontal Aiming Good Angle Bonus, only Vertical Aiming Height Advantage Bonus or both simultaneously. For example: On a Target taking a “Simple” High Cover (such as a 1-Tile Rock) both Good Angle and Height Advantage Bonuses can as before be applied (BUT never cumulatively higher than the Cover Value they are reducing, for example: -40LowCover +28GoodAngle +12HeightAdvantage), on a Target taking instead a “Tall” High Cover (such as a tall Tree/Pillar) only Horizontal Aiming Angle Bonus can be applied (for as high as the Shooter climbs, the vertical Tree/Pillar still never offers a Vertical Angle Bonus), on a Target taking instead a “Long” High Cover (such as a long fence, standing the Target NOT at its edge) only Vertical Good Angle Bonus can with this update be applied (for as much as the Shooter on the building tries to “partially flank” the Target, the long fence still never offers an Horizontal Good Angle).
;FAR COVER
AllowFarCoverToGiveSomeCoverProtection = true
;Personal concept: Low Cover between shooter and target but not immediately near target. Who said that your soldier cannot use that trashcan as cover only because he is not immediately in front of it? Nonsense, in my book if something is partially hiding you from view then it's partially giving you cover (between +1 and +20, proportionally to how far/much that far Low Cover is hiding the target from the shooter's view). ;)
;Far Cover is applied obviously only to Targets NOT already taking cover (because the Far Cover would not cover them but their already existing Cover) EXCEPT if they are taking Cover AND a Good Angle is reducing that Cover Value: Only in that case Far Cover can help the Target BUT never with a value higher than the existing Good Angle Bonus (So that the Target will never have cumulative Cover Values above 40/20). Example: 40HighCover -14GoodAngle +14FarCoverPreventingGoodAngle (Instead of +19FarCover). ;)
;EXTENDED COVER
;Other personal concept: High Cover extended by Low Cover: When a Target taking High Cover “with a Low Cover next to it” is being partially flanked, then the Horizontal Good Angle reducing the High Cover will be only “half applied” since the the Shooter is only flanking the “upper half” of the Target while his “lower half” is still protected by the Extended Low Cover. (Example: -40HighCover +38GoodAngle -19ExtendedLowCoverPreventingGoodAngle). This way a Target using High/Low Covers on 2 sides, the more he is flanked, the more his cover will be reduced from 40 to 20 (realistically gradually switching from High to Low Cover).
;CHECK TRUE LINE OF SIGHT
GiveHitChanceZeroWhenTargetableEnemiesAreInsteadNotTrulyInLineOfSight = true
;Personally designed check to prevent shooting aliens behind walls. Why give 0% Hit Chance instead of simply preventing to target? Because I like that it gives me the opportunity to shoot anyway which, sometimes as a result, does environmental damage sometimes destroying or punching a hole in "what was blocking my view" for, possibly, a second regular shot in the next turn or by a squad-mate.
;FAIRLY APPLIED
;The modifiers apply also to Enemies targeting your Squad-mates (oR it wouldn't be fair) and don't apply against units who refuse to or cannot take cover (Sparks, Faceless, Berserkers...) or who are unaware of your presence (therefore not "taking" cover because unaware of danger) unless altering this variable below:
OnlyAlertedTargetsCanHaveTheExtraProtectionOfFarCoverAndHeightDisadvantage = true
;CLASS OVERRIDES: 
;+ModClassOverrides=(BaseGameClass="X2AbilityToHitCalc_StandardAim"

;EU ROLLS: XCOM 1 DICE-ROLL SYSTEM
UseIndividualConsecutiveRollsForHitChanceCriticalChanceDodgeChance = false ;"false" will ignore the other 2 variables
PrioritizeCriticalChanceOverDodgeChance = true ; Hit?Yes-->Critical?No-->Dodge? OR Hit?Yes-->Dodge?No-->Critical?
AlwaysRollForBothDodgeAndCriticalEvenWhenOneUnsuccesful = false ;If both successful then they cancel out becoming Normal Hit
;Example: 90% Hit Chance with 10% Critical Chance on a Chrissalyd with 20% Dodge Chance
;XCOM1 - 3Rolls: FirstRoll90%Hit --> SecondRoll(10%of90%=)9%CriticalHit --> ThirdRoll(20%of81%=)16%Dodge
;XCOM1 - 3Rolls: (10%of 90%=) 9%CriticalHit, (90%- 9%-16%=)65%NormalHit, (20%of 81%=)16%Dodge, (100%-90%=)10%Miss
;XCOM2 - 1Roll : (10%of100%=)10%CriticalHit, (90%-10%-20%=)60%NormalHit, (20%of100%=)20%Dodge, (100%-90%=)10%Miss
;Example: 30% Hit Chance with 10% Critical Chance on a Chrissalyd with 20% Dodge Chance
;XCOM1 - 3Rolls: FirstRoll30%Hit --> SecondRoll(10%of30%=)3%CriticalHit --> ThirdRoll(20%of27%=)5%Dodge
;XCOM1 - 3Rolls: (10%of 30%=) 3%CriticalHit, (30%- 3%- 5%=)22%NormalHit, (20%of 27%=) 5%Dodge, (100%-30%=)70%Miss
;XCOM2 - 1Roll : (10%of100%=)10%CriticalHit, (30%-10%-20%=) 0%NormalHit, (20%of100%=)20%Dodge, (100%-30%=)70%Miss
;In XCOM2 the %Hit is "eaten" from the "left" by %Critical and from the "right" by Dodge "cutting" the %Hit into 3 parts %CriticalHit+%NormalHit+%Dodge and if  %Dodge is large enough then it can "eat" all of the remaining %NormalHit or even some of the %CriticalHit
;EXTRA DICE-ROLL OPTIONS
GuaranteedHitsCannotDodge = false
IndirectFireGuaranteesHit = false