Didn't resign, sorry

1.1.2
Entries in the JSON no longer check for inheritance. Previously, this could add EF_Component to items that were not supposed to have it, leading to conflicts.

1.1.1
Added protection from invalid json. if you see "EXPLOSION FRAGMENTS JSON IS INVALID, USING DEFAULT ONE. REGENERATE JSON" in logs, do what it says, because your current json is invalid.

1.1.0
REGENERATE JSON
Class ExplosionFragmentsServer has been renamed to EF_Component from the previous static implementation. It is no longer static, allowing for more code optimization.

Behavior of dynamicDamageCoef has been modified. If enabled, fragment damage now decreases with distance using a distance coefficient (ranging from 1 to 0). This is based on the distance and utilizes Quart easing, and the damage coefficient is calculated accordingly.

New fragmentation preset, OPTIMIZEDSPHERE, has been added. This preset optimizes the fragmentation behavior when the explosion is close to the surface.

Calculations for the fragmentation cone have been updated to improve accuracy and performance.

Various null pointer issues have been resolved to prevent crashes.

Dummy object used for projectiles has been optimized to reduce unnecessary calculations and improve overall performance.

Debug functionality has been added to assist with troubleshooting and provide more detailed feedback during development.

JSON Configuration Updates:
minDistanceToSpawnSounds added: A new configuration parameter has been added to the JSON for specifying the minimum distance at which sounds will spawn.
offset added: The offset from the item's zero point or the point of contact in the case of projectiles. It is recommended to leave this at the default value.
createParticles and createSounds settings are now independent in the JSON configuration, allowing for more granular control over their behavior.

1.0.1
RPC related issues should be resolved, now you can set up to 1000 fragments without client freeze.

1.0.0
Release