Package megamek.common.weapons.handlers

Class CapitalLaserBayOrbitalBombardmentHandler

java.lang.Object

megamek.common.weapons.handlers.WeaponHandler

megamek.common.weapons.handlers.BayWeaponHandler

megamek.common.weapons.handlers.CapitalLaserBayOrbitalBombardmentHandler

All Implemented Interfaces:

Serializable, AttackHandler

public class CapitalLaserBayOrbitalBombardmentHandler
extends BayWeaponHandler

See Also:

• Serialized Form

Field Summary

Fields inherited from class megamek.common.weapons.handlers.BayWeaponHandler

ammo

Fields inherited from class megamek.common.weapons.handlers.WeaponHandler

advancedPD, ammoType, amsBayEngaged, amsBayEngagedCap, amsBayEngagedMissile, amsEngaged, announcedEntityFiring, apdsEngaged, attackingEntity, attackValue, bDirect, bGlancing, bLowProfileGlancing, bMissed, bSalvo, calcDmgPerHitReport, CapMissileAMSMod, CapMissileArmor, CapMissileMissed, CounterAV, damageType, firstHit, game, gameManager, generalDamageType, hit, insertedAttacks, isJammed, isStrafing, isStrafingFirstShot, missed, nDamPerHit, nRange, nSalvoBonus, nukeS2S, numRapidFireHits, numWeapons, numWeaponsHit, originalAV, parentBayHandler, pdBayEngaged, pdBayEngagedCap, pdBayEngagedMissile, pdOverheated, roll, secondShot, sSalvoType, subjectId, target, throughFront, toHit, typeName, underWater, weapon, weaponAttackAction, weaponEntity, weaponType

Constructor Summary

Constructors

Constructor	Description
CapitalLaserBayOrbitalBombardmentHandler(ToHitData t, WeaponAttackAction w, Game g, TWGameManager m)

Method Summary

Modifier and Type	Method	Description
boolean	cares(GamePhase phase)	Do we care about the specified phase?
boolean	handle(GamePhase phase, Vector<Report> reports)	Sigh, according to the ruling linked below, when weapon bays are fired at ground targets, they should make one to-hit roll, but the AV of each weapon should be applied separately as damage - that needs a special handler

Methods inherited from class megamek.common.weapons.handlers.BayWeaponHandler

addHeat, calcAttackValue, handleAeroSanity, initializeCapMissileArmor

Methods inherited from class megamek.common.weapons.handlers.WeaponHandler

absorbBuildingDamage, addGlancingBlowReports, allShotsHit, announcedEntityFiring, applyGlancingBlowModifier, applyGlancingBlowModifier, calcAeroDamage, calcCapMissileAMSMod, calcCounterAV, calcDamagePerHit, calcHits, calculateNumCluster, calculateNumClusterAero, canEngageCapitalMissile, checkLI, checkPDConditions, checkTerrain, doAmmoFeedProblemCheck, doChecks, getAttacker, getAttackerId, getBracketingMultiplier, getCapMisMod, getCapMissileAMSMod, getClusterModifiers, getCounterAV, getFireTNRoll, getLargeCraftHeat, getNumberWeapons, getParentBayHandler, getSalvoBonus, getTotalGlancingBlowFactor, getWeaponAttackAction, handleArtilleryDriftMarker, handleBuildingDamage, handleClearDamage, handleClearDamage, handleEntityDamage, handleIgnitionDamage, handlePartialCoverHit, handleSpecialMiss, initHit, insertAttacks, isLowProfileGlancingBlow, isStrafing, isStrafingFirstShot, isThunderBolt, reportMiss, reportMiss, restore, setAMSBayReportingFlag, setAnnouncedEntityFiring, setDone, setGlancingBlowFlags, setParentBayHandler, setPDBayReportingFlag, setStrafing, setStrafingFirstShot, specialResolution, unitGainsPartialCoverFromWater, unitStickingOutOfBuilding, useAmmo, usesClusterTable

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface megamek.common.weapons.handlers.AttackHandler

getBuildingDamageAdjustment, producesReportThisPhase

Constructor Details

CapitalLaserBayOrbitalBombardmentHandler

public CapitalLaserBayOrbitalBombardmentHandler(ToHitData t,
 WeaponAttackAction w,
 Game g,
 TWGameManager m)
                                         throws EntityLoadingException

Throws:

EntityLoadingException

Method Details

cares

public boolean cares(GamePhase phase)

Description copied from class: WeaponHandler

Do we care about the specified phase?

Specified by:

cares in interface AttackHandler

Overrides:

cares in class WeaponHandler

Parameters:

phase - The current game phase

Returns:

True when this handler acts or might act in this phase. The handle() method of this handler is only called when this method returns true for the present phase.

handle

public boolean handle(GamePhase phase,
 Vector<Report> reports)

Description copied from class: BayWeaponHandler

Sigh, according to the ruling linked below, when weapon bays are fired at ground targets, they should make one to-hit roll, but the AV of each weapon should be applied separately as damage - that needs a special handler

Specified by:

handle in interface AttackHandler

Overrides:

handle in class BayWeaponHandler

Parameters:

phase - The present game phase

reports - The reports list to add new reports to

Returns:

a boolean value indicating whether this should be kept or not