Thursday, February 11, 2021

Adding Hull Integrity Feature

Currently working on adding the new Hull Integrity feature.  How combat currently works is when a cannonball hits your ship, a comparison is made between the ammo's penetration value and your hull resistance.  When penetration is higher than hull resistance, chance to penetrate is also higher, and when penetration is lower than hull resistance then chance to penetrate is again lower.  This mechanic is explained in more detail in previous posts.  

What matters here, is you can get into a situation where you beat on an enemy seemingly forever with low chance to penetrate.  The Hull Integrity feature helps this.  Whenever you are hit, this hit will reduce your hull integrity value, whether penetrated or not.  So every hit now causes some damage.  Hull integrity is then taken as a percentage, on a scale of 0 to 1, and multiplied against hull resistance for penetration calculations.  

This means ships which have high hull resistance can eventually get beaten down by weaker opponents given enough damage to hull integrity.  Larger ammunition will generally deal more damage to hull integrity than smaller ammunition.  So in fleet battles a large ship can open fire on an enemy first, reducing its hull integrity, then smaller ships can join in with higher effectiveness, even if the first large ship didn't cause any leaks.  

As far as repairing hull integrity, whenever your repair crew aren't repairing leaks, or in the future sails and masts, they will apply their repair effort to hull integrity.  

Another cause of hull integrity damage is large fires.  Currently they can cause leaks, but now they will also damage hull integrity.  

Explosive ammunition, while not yet in the game, now are redesigned.  They now will be a low penetration but high hull integrity damage focused ammunition type.  The planned Ironclad ship has also been refocused, making it a high hull resistance and high hull integrity ship.  Explosive ammunition will be all but required to take it down.  

No comments:

Post a Comment