Spigot & BungeeCord 1.16.2-1.16.5

Discussion in 'News and Announcements' started by md_5, Aug 11, 2020.

  1. The time has just been increased from 7 to 28 days.
     
    • Funny Funny x 1
  2. I couldn't run 1.16.4 :(
     
  3. SlimeDog

    Moderator Patron

    Without more information, how could we possibly guess why?
     
  4. Start code old I have a trying make a new optimized start code for now
     
  5. Is this a new world or upgrading from an older version? Depending on what version world was first rendered, the generation process changes slightly - I have several places in my world (which was first built in 1.8 and upgraded through all versions since) where chunk borders are visible due to rendering changes - they look very much like what you show above. When I see them, if they bother me enough I fix them (drop a few blocks or break a few blocks to smooth out the transition). It's not an error, per se. Just a difference. You'll see this most often at the edges of a map when the new chunk was not explored until after some major version updates (e.g. 1.12 to 1.13).
     
  6. Nope, it all generated by the one version. (Built on 12/12/2020)
     
  7. SlimeDog

    Moderator Patron

    Please share the seed and location of the illustrated discontinuity, or some other sample discontinuity.
     
  8. The seed is
    Code (Text):
    level-seed=-2788421449335418328
    And the details of the Location is in the image.
    [​IMG]
    The problem generation is a fairly rare occurance.
    I have seen a few other questionable areas, but nothing as clear as this one.
     
    #230 Goldentoenail, Dec 17, 2020
    Last edited: Dec 17, 2020
  9. SlimeDog

    Moderator Patron

    This discontinuity occurs in vanilla Minecraft 1.16.4 (tested in single-player). Suggestion: file a Mojang issue.
     
    #231 SlimeDog, Dec 17, 2020
    Last edited: Dec 17, 2020
    • Like Like x 1
    • Agree Agree x 1
  10. It's a feature, not a bug ;)
     
    • Creative Creative x 1
  11. I'm just seeing this now, with the "input does not contain a key" error message and improperly-generated villages. I guess this is a vanilla bug, but is there anything we can do about it? Also, does it affect all villages? Because some of my villages look OK.
    https://bugs.mojang.com/browse/MC-197883
     
  12. Hello,

    Not sure if I'm allowed to mention this in this thread, but to get Spigot 1.16.4 to run natively on an arm64 (M1) Mac using native Java (I used zulu8.50.0.1017) and support plug-ins that use sqlite (e.g. CoreProtect) you have to repack the spigot.jar using a version of sqlite that has arm64 native code (I used sqlite-jdbc-3.32.3.3). Otherwise the following Java exeption will be thrown:
    "java.lang.Exception: No native library is found for os.name=Mac and os.arch=aarch64. path=/org/sqlite/native/Mac/aarch64"

    Ernst Mulder
     
  13. The same thing recently happened with BungeeCord. md_5 seems to just reupload the same version to fix this, because it doesn't show any changes in the changelog.
     
  14. Thanks for updating ...Spigot & BungeeCord 1.16.2 & 1.16.3 & 1.16.4
     
  15. Hi,
    anyone else having issues with nether portals?

    I have a world with a linked nether (using multiverse).
    When ever i travel to the nether: all is ok. I spawn at the portal in the nether.
    When i steped into the portal in nether the first time i got an error and lost connection.
    Code (Text):

    net.minecraft.server.v1_16_R3.ReportedException: Ticking player
       at net.minecraft.server.v1_16_R3.EntityPlayer.playerTick(EntityPlayer.java:528) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.PlayerConnection.tick(PlayerConnection.java:154) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.NetworkManager.a(NetworkManager.java:223) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.ServerConnection.c(ServerConnection.java:130) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.MinecraftServer.b(MinecraftServer.java:1127) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.DedicatedServer.b(DedicatedServer.java:355) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.MinecraftServer.a(MinecraftServer.java:1008) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.MinecraftServer.w(MinecraftServer.java:847) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.MinecraftServer.lambda$0(MinecraftServer.java:164) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at java.lang.Thread.run(Unknown Source) [?:1.8.0_271]
    Caused by: java.lang.IllegalArgumentException: Cannot get property BlockStateEnum{name=axis, clazz=class net.minecraft.server.v1_16_R3.EnumDirection$EnumAxis, values=[x, z]} as it does not exist in Block{minecraft:air}
       at net.minecraft.server.v1_16_R3.IBlockDataHolder.get(SourceFile:95) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.BlockPortalShape.a(BlockPortalShape.java:227) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.Entity.lambda$4(Entity.java:2489) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at java.util.Optional.map(Unknown Source) ~[?:1.8.0_271]
       at net.minecraft.server.v1_16_R3.Entity.a(Entity.java:2471) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.EntityPlayer.a(EntityPlayer.java:737) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.EntityPlayer.b(EntityPlayer.java:789) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.Entity.doPortalTick(Entity.java:2003) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.Entity.entityBaseTick(Entity.java:389) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.EntityLiving.entityBaseTick(EntityLiving.java:262) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.Entity.tick(Entity.java:364) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.EntityLiving.tick(EntityLiving.java:2361) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.EntityHuman.tick(EntityHuman.java:153) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       at net.minecraft.server.v1_16_R3.EntityPlayer.playerTick(EntityPlayer.java:446) ~[spigot-1.16.4_Build09-01-21_BT119.jar:git-Spigot-a56d446-7029c0a]
       ... 9 more

    When i reconnected, i found a portal in the air some blocks away from my first portal.
    After trying to find a reason by removing one plugin after the other... i only found spigot itself... ;(
    (btw: with paper it works...)

    Now i tried to move the portal in nether a few blocks and always ended with another new portal in overworld.
    Sometimes it creates a new portal in overworld without moving the portal in nether.
    Now i have 3 portals in my 'house' just a few blocks from each other...

    What could be the reason?

    Strange: In another world on the same server it seems to work...


    PS: i'm using multiverse with Multiverse-Portals and Multiverse-NetherPortals. (4.2.3 dev builds)
     
  16. Post the output of /version
     
  17. Same as in the error-spoiler:
    Code (Text):

    [00:43:24] [Server thread/INFO]: This server is running CraftBukkit version git-Spigot-a56d446-7029c0a (MC: 1.16.4) (Implementing API version 1.16.4-R0.1-SNAPSHOT)
    [00:43:24] [Server thread/INFO]: You are running the latest version
     
    PS: it seems that it only happens on this one world.. (it's an old one that started on MC1.4...)