senseiwells

Code Analysis (Mojang Mappings, 1.20.6):

For minecraft.custom:minecraft.damage_dealt_absorbed:
This happens because the Player class overrides the *actuallyHurt* with similar behaviour but doesn't include the code for awarding the minecraft.custom:minecraft.damage_dealt_absorbed stat.
Suggested fix:

public abstract class Player extends LivingEntity {
    // ...
    @Override
    protected void actuallyHurt(DamageSource source, float totalDamageAmount) {
        // ...
        float damageAmount = Math.max(damageAmount - this.getAbsorptionAmount(), 0.0F);
        // ...
        float damageAbsorbed = totalDamageAmount - damageAmount;
        if (damageAbsorbed > 0.0F && damageAbsorbed < 3.4028235E37F) {
            this.awardStat(Stats.DAMAGE_ABSORBED, Math.round(damageAbsorbed * 10.0F));
            
            // Fix start
            if (source.getEntity() instanceof ServerPlayer sourcePlayer) {
                sourcePlayer.awardStat(Stats.DAMAGE_DEALT_ABSORBED, Math.round(damageAbsorbed * 10.0F));
            }
            // Fix end
        }
        // ...
    }
}

For minecraft.custom:minecraft.damage_dealt_resisted the stat is only not awarded when attacking player entities, because of an incorrect use of an *else if* in *LivingEntity#getDamageAfterMagicAbsorb*.

Suggested fix:

public abstract class LivingEntity extends Entity implements Attackable {
    protected float getDamageAfterMagicAbsorb(DamageSource source, float damageAmount) {
        // ...
        if (this.hasEffect(MobEffects.DAMAGE_RESISTANCE) && !source.is(DamageTypeTags.BYPASSES_RESISTANCE)) {
            int reducedDamageScale = 25 - (this.getEffect(MobEffects.DAMAGE_RESISTANCE).getAmplifier() + 1) * 5;
            float reducedDamage = damageAmount * reducedDamageScale;
            float originalDamageAmount = damageAmount;
            damageAmount = Math.max(reducedDamage / 25.0F, 0.0F);
            float damageResisted = originalDamageAmount - damageAmount;
            if (damageResisted > 0.0F && damageResisted < 3.4028235E37F) {
                if (this instanceof ServerPlayer) {
                    ((ServerPlayer) this).awardStat(Stats.DAMAGE_RESISTED, Math.round(damageResisted * 10.0F));
                }  
                // Suggested fix: removed the 'else if' and converted into 'if':
                if (source.getEntity() instanceof ServerPlayer) {
                    ((ServerPlayer) source.getEntity()).awardStat(Stats.DAMAGE_DEALT_RESISTED, Math.round(damageResisted * 10.0F));
                }
            }
        }
    }
}

Yes but every other command that has a time parameter uses units in relation to ticks. I see no reason for the world border to be the exception and to be inconsistent with all other commands, the world border ** is ** a game mechanic that should be tied to ticking, in fact the game does indeed tick the world border, but it updates it in realtime (ms).

I understand that by default it takes seconds as an argument, and changing it to be consistent with the other commands would change behaviours, but I think that just making seconds the default unit and allowing the user to specify ticks, days, etc. would still be preferable. Also the fact that the argument states that it is in seconds doesn't necessarily mean it will be, with the current time arguments you can specify seconds by appending a 's', however this does not mean it will actually take that amount of seconds instead that amount of seconds in ticks.