Bug: Entities In the World and high range targeters doesn't work

Discussion in 'Bug Reports' started by Hisho, Jan 20, 2020.

  1. Hisho

    Hisho New Member

    Joined:
    Apr 19, 2017
    Messages:
    6
    Likes Received:
    0
    Enter a brief description of what is broken Entities In the World and high range targeters doesn't work

    What version of Minecraft are you using? 1.14

    What server jar are you using? Spigot

    What is this a bug report for? MythicMobs

    What version of the plugin are you using? 4.7.2

    Describe the bug. Be as specific as possible, images or short gifs/videos are welcome but save configuration files for later sections. Write a whole paragraph if needed, help us bug testers replicate your issue!
    When I try to use mechanics that affects mobs in radius ~4000 or all mobs in the world I always get this on my console:
    [17:34:33] [Craft Scheduler Thread - 46/WARN]: [MythicMobs] Plugin MythicMobs v4.7.2-FREE generated an exception while executing task 83
    java.lang.NullPointerException: null
    at io.lumine.xikage.mythicmobs.skills.SkillManager.runTimerSkills(SkillManager.java:330) ~[?:?]
    at io.lumine.xikage.mythicmobs.clock.MythicMobsAsyncClock.run(MythicMobsAsyncClock.java:21) ~[?:?]
    at org.bukkit.craftbukkit.v1_14_R1.scheduler.CraftTask.run(CraftTask.java:84) ~[patched_1.14.4.jar:git-Paper-233]
    at org.bukkit.craftbukkit.v1_14_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:54) ~[patched_1.14.4.jar:git-Paper-233]
    at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[patched_1.14.4.jar:git-Paper-233]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_201]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_201]
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_201]

    It stops when i restart the server but it's really annoying because when I do any change in mob it's start again. Please help me with this and also repair bug with mob despawning (this bug brought me to have mobs that are suiciding another mobs when they should peacefuly despawn :c).

    Example Configurations
    TestingStand:
    Type: ARMOR_STAND
    Options:
    Despawn: false
    Skills:
    - signal{s=ARTEM} @EntitiesInRadius{r=4000} ~onTimer:100
    SQUID:
    Type: SQUID
    Skills:
    - suicide @self ~onSignal:ARTEM
     
    #1
  2. jaylawl

    jaylawl Developer
    Developer Community Manager Premium Supporter Supporter Quality Assurance

    Joined:
    Sep 16, 2015
    Messages:
    1,840
    Likes Received:
    175
    sweet jesus what the fuck 4000 radius
     
    #2
  3. jaylawl

    jaylawl Developer
    Developer Community Manager Premium Supporter Supporter Quality Assurance

    Joined:
    Sep 16, 2015
    Messages:
    1,840
    Likes Received:
    175
    while i dont wanna say that using that high a radius isn't supported (because i dont know), this is definitly not a good method of doing what youre trying to achieve. if you just want the squids to die then do

    Code:
    Skills:
    - suicide @self ~onSpawn
     
    #3
  4. Hisho

    Hisho New Member

    Joined:
    Apr 19, 2017
    Messages:
    6
    Likes Received:
    0
    Ok I don't mean exatly that. What I want is to bypass bug with despawning and I created this:


    TestingStand:
    Type: ARMOR_STAND
    Options:
    Despawn: false
    Skills:
    - signal{s=ARTEM} @EntitiesInRadius{r=4000} ~onTimer:100

    SQUID:
    Type: SQUID
    Options:
    Depawn: false
    Drops:
    - SquidDrops
    Skills:
    - skill{s=ConsoleFrendlyDespawnig} ~onSignal:ARTEM

    ConsoleFrendlyDespawnig:
    Conditions:
    - playerwithin{d=80} false
    Skills:
    - setstance{stance=CFDespawn} @self
    - suicide @self

    SquidDrops:
    Conditions:
    - stance{s=CFDespawn} false
    Drops:
    - ink_sac 1 1
    - ink_sac 1 0.4
    - ink_sac 1 0.1
     
    #4
    Last edited: Jan 20, 2020
  5. jaylawl

    jaylawl Developer
    Developer Community Manager Premium Supporter Supporter Quality Assurance

    Joined:
    Sep 16, 2015
    Messages:
    1,840
    Likes Received:
    175
    #5
  6. Hisho

    Hisho New Member

    Joined:
    Apr 19, 2017
    Messages:
    6
    Likes Received:
    0
    Yes, but every time when mob despawns or get removed I get this bug on console:

    [21:44:12 WARN]: [MythicMobs] Plugin MythicMobs v4.7.2-FREE generated an exception while executing task 83
    java.lang.IllegalStateException: MythicMobDespawnEvent may only be triggered synchronously.
    at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:533) ~[patched_1.14.4.jar:git-Paper-233]
    at io.lumine.xikage.mythicmobs.adapters.bukkit.BukkitWorldManager.handleMobDespawnEvent(BukkitWorldManager.java:108) ~[?:?]
    at io.lumine.xikage.mythicmobs.mobs.ActiveMob.setUnloaded(ActiveMob.java:436) ~[?:?]
    at io.lumine.xikage.mythicmobs.mobs.ActiveMob.tick(ActiveMob.java:156) ~[?:?]
    at io.lumine.xikage.mythicmobs.skills.SkillManager.runTimerSkills(SkillManager.java:328) ~[?:?]
    at io.lumine.xikage.mythicmobs.clock.MythicMobsAsyncClock.run(MythicMobsAsyncClock.java:21) ~[?:?]
    at org.bukkit.craftbukkit.v1_14_R1.scheduler.CraftTask.run(CraftTask.java:84) ~[patched_1.14.4.jar:git-Paper-233]
    at org.bukkit.craftbukkit.v1_14_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:54) ~[patched_1.14.4.jar:git-Paper-233]
    at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[patched_1.14.4.jar:git-Paper-233]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_201]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_201]
    at java.lang.Thread.run(Unknown Source) [?:1.8.0_201]

    When they are killed by suicide mechanic or minecraft command they don't spam on my console.
     
    #6

Share This Page