Bug Closed · Resolved

damageamount Condition does not work for onDamaged trigger.

#4830 opened by Unknown 2 years ago

Upvote 0
Unknownreported this bug

Title, tested using a crucible item with:

  - message{m="more than 5 , <skill.var.damage-amount>";sync=true} @self ~onDamaged ?damageamount{amount=>5}

Even when taking damage greater than 5, ./damage @p 15 for instance, the message would not send. Also tested as a regular non-inline condition, neither approach worked.

Unknowncommented

It also returns this error, regardless of if >5 is in ""

[15:45:06 WARN]: [MythicMobs] ✗ Configuration Error in Condition DamageAmount
[15:45:06 WARN]: [MythicMobs] --| Mechanic: defender-guard:message | File: items-armor.yml
[15:45:06 WARN]: [MythicMobs] --| Error Message: An internal error occurred
[15:45:06 WARN]: [MythicMobs] --| Condition Line: damageamount{amount=">5"}
[15:45:06 WARN]: java.lang.ClassCastException: class java.lang.Float cannot be cast to class java.lang.String (java.lang.Float and java.lang.String are in module java.base of loader 'bootstrap')
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.core.skills.conditions.all.DamageAmountCondition.check(DamageAmountCondition.java:32)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.core.skills.SkillCondition.evaluateCaster(SkillCondition.java:213)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.core.skills.SkillMechanic.isUsableFromSkill(SkillMechanic.java:254)
[15:45:06 WARN]:        at MythicCrucible-2.0.0-SNAPSHOT.jar//io.lumine.mythiccrucible.items.EquippedItem.runSkills(EquippedItem.java:130)
[15:45:06 WARN]:        at MythicCrucible-2.0.0-SNAPSHOT.jar//io.lumine.mythiccrucible.profiles.Profile.runSkills(Profile.java:339)
[15:45:06 WARN]:        at MythicCrucible-2.0.0-SNAPSHOT.jar//io.lumine.mythiccrucible.skills.SkillEventListeners.onMythicTrigger(SkillEventListeners.java:255)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.bukkit.utils.Delegates$ConsumerToBiConsumerSecond.accept(Delegates.java:144)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.bukkit.utils.events.functional.single.EventListener.execute(EventListener.java:131)
[15:45:06 WARN]:        at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:81)
[15:45:06 WARN]:        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70)
[15:45:06 WARN]:        at io.papermc.paper.plugin.manager.PaperEventManager.callEvent(PaperEventManager.java:54)
[15:45:06 WARN]:        at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.callEvent(PaperPluginManagerImpl.java:126)
[15:45:06 WARN]:        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:615)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.bukkit.utils.Events.call(Events.java:103)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.core.skills.EventExecutor.processTriggerMechanics(EventExecutor.java:108)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.bukkit.listeners.triggers.DamageTriggerListeners.onDamagedTrigger(DamageTriggerListeners.java:576)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.bukkit.utils.Delegates$ConsumerToBiConsumerSecond.accept(Delegates.java:144)
[15:45:06 WARN]:        at MythicMobs-5.6.2-SNAPSHOT.jar//io.lumine.mythic.bukkit.utils.events.functional.single.EventListener.execute(EventListener.java:131)
[15:45:06 WARN]:        at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:81)
[15:45:06 WARN]:        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70)
[15:45:06 WARN]:        at io.papermc.paper.plugin.manager.PaperEventManager.callEvent(PaperEventManager.java:54)
[15:45:06 WARN]:        at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.callEvent(PaperPluginManagerImpl.java:126)
[15:45:06 WARN]:        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:615)
[15:45:06 WARN]:        at org.bukkit.craftbukkit.v1_20_R3.event.CraftEventFactory.callEvent(CraftEventFactory.java:265)
[15:45:06 WARN]:        at org.bukkit.craftbukkit.v1_20_R3.event.CraftEventFactory.callEntityDamageEvent(CraftEventFactory.java:1252)
[15:45:06 WARN]:        at org.bukkit.craftbukkit.v1_20_R3.event.CraftEventFactory.handleEntityDamageEvent(CraftEventFactory.java:1226)
[15:45:06 WARN]:        at org.bukkit.craftbukkit.v1_20_R3.event.CraftEventFactory.handleEntityDamageEvent(CraftEventFactory.java:1051)
[15:45:06 WARN]:        at org.bukkit.craftbukkit.v1_20_R3.event.CraftEventFactory.handleLivingEntityDamageEvent(CraftEventFactory.java:1286)
[15:45:06 WARN]:        at net.minecraft.world.entity.EntityLiving.damageEntity0(EntityLiving.java:2221)
[15:45:06 WARN]:        at net.minecraft.world.entity.player.EntityHuman.damageEntity0(EntityHuman.java:1059)
[15:45:06 WARN]:        at net.minecraft.world.entity.EntityLiving.a(EntityLiving.java:1471)
[15:45:06 WARN]:        at net.minecraft.world.entity.player.EntityHuman.a(EntityHuman.java:966)
[15:45:06 WARN]:        at net.minecraft.server.level.EntityPlayer.a(EntityPlayer.java:1135)
[15:45:06 WARN]:        at net.minecraft.server.commands.DamageCommand.a(DamageCommand.java:38)
[15:45:06 WARN]:        at net.minecraft.server.commands.DamageCommand.e(DamageCommand.java:24)
[15:45:06 WARN]:        at com.mojang.brigadier.context.ContextChain.runExecutable(ContextChain.java:73)
[15:45:06 WARN]:        at net.minecraft.commands.execution.tasks.ExecuteCommand.a(ExecuteCommand.java:32)
[15:45:06 WARN]:        at net.minecraft.commands.execution.tasks.ExecuteCommand.execute(ExecuteCommand.java:19)
[15:45:06 WARN]:        at net.minecraft.commands.execution.UnboundEntryAction.a(UnboundEntryAction.java:8)
[15:45:06 WARN]:        at net.minecraft.commands.execution.CommandQueueEntry.a(CommandQueueEntry.java:5)
[15:45:06 WARN]:        at net.minecraft.commands.execution.ExecutionContext.a(ExecutionContext.java:101)
[15:45:06 WARN]:        at net.minecraft.commands.CommandDispatcher.a(CommandDispatcher.java:434)
[15:45:06 WARN]:        at net.minecraft.commands.CommandDispatcher.performCommand(CommandDispatcher.java:336)
[15:45:06 WARN]:        at net.minecraft.commands.CommandDispatcher.a(CommandDispatcher.java:323)
[15:45:06 WARN]:        at net.minecraft.server.network.PlayerConnection.a(PlayerConnection.java:2216)
[15:45:06 WARN]:        at net.minecraft.server.network.PlayerConnection.lambda$handleChatCommand$16(PlayerConnection.java:2176)
[15:45:06 WARN]:        at net.minecraft.util.thread.IAsyncTaskHandler.b(IAsyncTaskHandler.java:59)
[15:45:06 WARN]:        at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
[15:45:06 WARN]:        at net.minecraft.server.TickTask.run(TickTask.java:18)
[15:45:06 WARN]:        at net.minecraft.util.thread.IAsyncTaskHandler.d(IAsyncTaskHandler.java:153)
[15:45:06 WARN]:        at net.minecraft.util.thread.IAsyncTaskHandlerReentrant.d(IAsyncTaskHandlerReentrant.java:24)
[15:45:06 WARN]:        at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:1454)
[15:45:06 WARN]:        at net.minecraft.server.MinecraftServer.d(MinecraftServer.java:194)
[15:45:06 WARN]:        at net.minecraft.util.thread.IAsyncTaskHandler.x(IAsyncTaskHandler.java:126)
[15:45:06 WARN]:        at net.minecraft.server.MinecraftServer.bl(MinecraftServer.java:1431)
[15:45:06 WARN]:        at net.minecraft.server.MinecraftServer.x(MinecraftServer.java:1354)
[15:45:06 WARN]:        at net.minecraft.util.thread.IAsyncTaskHandler.c(IAsyncTaskHandler.java:136)
[15:45:06 WARN]:        at net.minecraft.server.MinecraftServer.w_(MinecraftServer.java:1332)
[15:45:06 WARN]:        at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:1221)
[15:45:06 WARN]:        at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:319)
[15:45:06 WARN]:        at java.base/java.lang.Thread.run(Thread.java:840)
Unknowncommented

Closing due to inactivity and major version changes since posting. If this issue is still present, re-open this issue with a modern-version server log, configs used to test and steps to reproduce.
onDamaged seemed to have many issues during this version, such as #1450

Sign in to join the discussion.