Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicMobs MythicMobs
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 165
    • Issues 165
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicMobsMythicMobs
  • Issues
  • #675

Closed
Open
Created Jan 14, 2022 by Zackary Blair@Paintsplatters

java.lang.UnsupportedOperationException: Calling Entity#remove on players produces undefined (bad) behavior

Summary

Describe the bug encountered in detail.

Steps to reproduce

Provide a full set of steps used to reproduce the bug, including links to SEPARATE Pastebin pastes for each relevant configuration file.

Current behavior

Upon logging into the server, walking to some other location, then logging off. this error is thrown in console.

when using 4.14.1

[20:05:21 ERROR]: [MythicMobs] [SCHEDULER] Exception thrown whilst executing task [20:05:21 WARN]: java.lang.UnsupportedOperationException: Calling Entity#remove on players produces undefined (bad) behavior [20:05:21 WARN]: at org.bukkit.craftbukkit.v1_17_R1.entity.CraftPlayer.remove(CraftPlayer.java:2459) [20:05:21 WARN]: at MythicMobs-4.14.1.jar//io.lumine.xikage.mythicmobs.adapters.bukkit.BukkitEntity.lambda$remove$0(BukkitEntity.java:159) [20:05:21 WARN]: at MythicMobs-4.14.1.jar//io.lumine.xikage.mythicmobs.utils.Delegates$RunnableToSupplier.get(Delegates.java:121) [20:05:21 WARN]: at MythicMobs-4.14.1.jar//io.lumine.xikage.mythicmobs.utils.promise.LuminePromise$SupplyRunnable.run(LuminePromise.java:654) [20:05:21 WARN]: at MythicMobs-4.14.1.jar//io.lumine.xikage.mythicmobs.utils.tasks.LumineExecutors$SchedulerWrappedRunnable.run(LumineExecutors.java:70) [20:05:21 WARN]: at org.bukkit.craftbukkit.v1_17_R1.scheduler.CraftTask.run(CraftTask.java:101) [20:05:21 WARN]: at org.bukkit.craftbukkit.v1_17_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:483) [20:05:21 WARN]: at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:1567) [20:05:21 WARN]: at net.minecraft.server.dedicated.DedicatedServer.b(DedicatedServer.java:490) [20:05:21 WARN]: at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:1483) [20:05:21 WARN]: at net.minecraft.server.MinecraftServer.x(MinecraftServer.java:1282) [20:05:21 WARN]: at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:319) [20:05:21 WARN]: at java.base/java.lang.Thread.run(Thread.java:831)

Then, i log back on, and my player location and advancements were not saved. Describe what happens currently, while the bug is affecting your server.

although this error does not seem to appear in dev 3976, the player location issue persists.

Intended correct behavior

This error should not occur and player data should save and function as normal

Server log file

Log file from mm 3976 https://pastebin.com/Bth2EmaG

log file from 4.14.1

https://pastebin.com/Vc2Gx1up

this issue was not present in build 17dae5d0 5.0.0 premium (unsure the build #)

It is present in 3976 5.0.0 dev - and stable premium 4.14.1

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking