Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue during explosion near a mob. #501

Open
Plgrrrr opened this issue Feb 1, 2025 · 0 comments
Open

Issue during explosion near a mob. #501

Plgrrrr opened this issue Feb 1, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@Plgrrrr
Copy link

Plgrrrr commented Feb 1, 2025

Current/Expected Behavior

I'm getting an error when a grenade explodes near a mob. When this error occurs there is no explosion.
The error:

[WeaponMechanics] Global task for WeaponMechanics v4.0.6-BETA1 generated an exception
java.lang.IllegalArgumentException: Invalid slot: BODY
        at WeaponMechanics-4.0.6-BETA1.jar/me.deecaad.weaponmechanics.weapon.damage.DamageUtil.damage(DamageUtil.java:262) ~[WeaponMechanics-4.0.6-BETA1.jar:?]
        at WeaponMechanics-4.0.6-BETA1.jar/me.deecaad.weaponmechanics.weapon.damage.DamageUtil.damageArmor(DamageUtil.java:251) ~[WeaponMechanics-4.0.6-BETA1.jar:?]
        at WeaponMechanics-4.0.6-BETA1.jar/me.deecaad.weaponmechanics.weapon.damage.DamageHandler.tryUse(DamageHandler.java:111) ~[WeaponMechanics-4.0.6-BETA1.jar:?]
        at WeaponMechanics-4.0.6-BETA1.jar/me.deecaad.weaponmechanics.weapon.damage.DamageHandler.lambda$tryUseExplosion$2(DamageHandler.java:271) ~[WeaponMechanics-4.0.6-BETA1.jar:?]
        at it.unimi.dsi.fastutil.objects.Object2DoubleMap.lambda$forEach$0(Object2DoubleMap.java:245) ~[fastutil-8.5.15.jar:?]
        at it.unimi.dsi.fastutil.objects.Object2DoubleOpenHashMap$MapEntrySet.fastForEach(Object2DoubleOpenHashMap.java:1082) ~[fastutil-8.5.15.jar:?]
        at it.unimi.dsi.fastutil.objects.Object2DoubleMap.forEach(Object2DoubleMap.java:247) ~[fastutil-8.5.15.jar:?]
        at WeaponMechanics-4.0.6-BETA1.jar/me.deecaad.weaponmechanics.weapon.damage.DamageHandler.tryUseExplosion(DamageHandler.java:270) ~[WeaponMechanics-4.0.6-BETA1.jar:?]
        at WeaponMechanics-4.0.6-BETA1.jar/me.deecaad.weaponmechanics.weapon.explode.Explosion.explode(Explosion.java:293) ~[WeaponMechanics-4.0.6-BETA1.jar:?]
        at WeaponMechanics-4.0.6-BETA1.jar/me.deecaad.weaponmechanics.weapon.explode.Explosion.lambda$handleExplosion$0(Explosion.java:191) ~[WeaponMechanics-4.0.6-BETA1.jar:?]
        at MechanicsCore-4.0.4.jar/me.deecaad.core.lib.scheduler.RegionSchedulerImplementation.lambda$runDelayed$3(RegionSchedulerImplementation.java:99) ~[MechanicsCore-4.0.4.jar:?]
        at MechanicsCore-4.0.4.jar/me.deecaad.core.lib.scheduler.folia.FoliaRegionScheduler.lambda$buildFoliaConsumer$0(FoliaRegionScheduler.java:36) ~[MechanicsCore-4.0.4.jar:?]
        at io.papermc.paper.threadedregions.scheduler.FoliaGlobalRegionScheduler$GlobalScheduledTask.run(FoliaGlobalRegionScheduler.java:179) ~[paper-1.21.4.jar:?]
        at io.papermc.paper.threadedregions.scheduler.FoliaGlobalRegionScheduler.tick(FoliaGlobalRegionScheduler.java:37) ~[paper-1.21.4.jar:?]
        at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1661) ~[paper-1.21.4.jar:1.21.4-114-cd9d6d6]
        at net.minecraft.server.MinecraftServer.tickServer(MinecraftServer.java:1529) ~[paper-1.21.4.jar:1.21.4-114-cd9d6d6]
        at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1251) ~[paper-1.21.4.jar:1.21.4-114-cd9d6d6]
        at net.minecraft.server.MinecraftServer.lambda$spin$2(MinecraftServer.java:310) ~[paper-1.21.4.jar:1.21.4-114-cd9d6d6]
        at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]

Steps To Reproduce

  1. Use any default explosive config
  2. Use WeaponMechanics-4.0.6-BETA1
  3. Use explosives to collide with the mob.

Log File

latest.log

Anything else?

No response

@Plgrrrr Plgrrrr added the bug Something isn't working label Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant