Problem version: 2.0.0, build230 (in fact, this issue has been present since version 2.0.0, but not in version 1.4.1) Problem description: I created a replica on the server with an event set up that utilizes MythicMobs' signaling feature. This signal event is used to control the behavior of the boss in the replica. When this signal event is triggered, if the boss listens to this signal, he will commit suicide. In version 1.4.1, if there are two identical worlds operating simultaneously, we refer to them as World A and World B. If World A triggers this signal event, the boss of World A will die normally, while the boss of World B will not be affected. In versions 2.0.0 and above, if the signal event is triggered in World A, not only will the boss in World A die, but the boss in World B will also receive the signal, causing it to die abnormally. I think you modified the signal sending event of MythicMobs during the 2.0.0 update, because the problem still occurs when I roll back the version of MythicMobs plugin. I hope you can investigate, otherwise I won't be able to update versions after 1.4.1
For entities generated within the replica, some events will confuse entities in the world
#5902 opened by Unknown 1 year ago
Hey there! This sounds like it's more likely a Mythic Mobs issue if you're using Mythic Mobs signals... what targetter are you using when sending the signal?
Also, how exactly are you sending the signal? Is there a mob that does it, or are you using the Mythic Dungeons "Mythic Skill" function?
I am sure it is an issue with MythicDungeons, because when I discovered this bug, I tried rolling back the plugin version and eventually found that simply rolling back the MythicDungeons plugin to 1.4.1 could solve the problem. In addition, the problematic function is FunctionalMythSignal, which is a feature of the dungeon plugin that directly sends signals to a specified target.
The problem function is as follows：
- ==: net.playavalon.mythicdungeons.dungeons.functions.FunctionMythicSignal targetsString: 顶级-sheep056 targetType: &id003 ==: net.playavalon.mythicdungeons.api.parents.FunctionTargetType value: NONE location: ==: org.bukkit.Location x: -18.0 y: -60.0 z: 0.0 pitch: 0.0 yaw: 0.0 trigger: ==: net.playavalon.mythicdungeons.dungeons.triggers.TriggerLeaveDungeon preventLeaving: false allowRetrigger: false conditions: [] mythicSignal: Suicide radius: 999`
Hey there. I recently fixed an issue where multiple dungeons of the same type running simultaneously would break each other. Can you try the latest dev build and see if the issue persists?
I tried your latest version, but it still doesn't work properly. After retesting, I found that the problem is not with MythicMobs, and the events in the dungeon itself can read player behavior abnormally. In other words, there is a problem with the 'leave' trigger, as it reads all eligible behaviors in the same world and causes subsequent events to execute.
A simple testing method is as follows:
Firstly, you need two accounts and build a dungeon.
Then, when editing an event in the dungeon, I suggest using the message event because it is simple and easy to understand.
Next, configure the trigger for this event to leave and save the world.
Afterwards, use your two accounts to enter the dungeon you just created separately.
Finally, if any account is logged out of the dungeon, you will find that the information you just edited will be repeated twice for the account that logged out of the dungeon. Meanwhile, depending on the editing status of the message event, accounts that have not exited the dungeon may exhibit different abnormal behaviors depending on the targetType. I only tested the setting as party, in which case the message message will not be triggered when the account exits the dungeon.
I hope you can solve this problem, otherwise I won't be able to update the plugin version. Thank you
My server core is: purpur-1.21.1-2298