Spigot & BungeeCord 1.16.1

Discussion in 'News and Announcements' started by md_5, Jun 25, 2020.

  1. I get it in a new 1.15 world (no old spawners).
     
  2. Got latest v0.5.5 from https://github.com/sekwah41/Advanced-Portals/releases/tag/0.5.5
    [​IMG]
    What is this error ?? had to change trigger block from PORTAL_BLOCK - now triggers but get above error

    portals.yml
    midgard:
    world: ZeSpawn
    triggerblock: AIR
    bungee: Midgard
    pos1:
    X: -1521
    Y: 114
    Z: 715

    IS THIS A BUNGEECORD ERROR

    Get same error if I use "/server midgard" on my hub - which i believe is a Bungeecord command??
     
  3. md_5

    Administrator Developer

    Plugin bypassing the Bungee API, not a Bungee issue
     
    • Winner Winner x 1
  4. Most Embarrassing - left a old plugin in Bungeecord plugins folder
    name: FastConnect
    version: 3.0
    main: me.blackfire.fastconnect.Core
    author: Blackfire62

    1.Was not allowing me to use bungeecord command "server myworld" when i was in myhub
    2.Was also stopping AdvancedPortals allowing me to teleport to myworld.
    3.Because i did not complete the teleport - caused error to show on myworld console with the NPC_Police plugin - which saw me long enough
    to "protest - it could not pass on player info to the plugin"
    Long morning - issue resolved - found fault - plugin removed - Error was the weak link "ME" - Thank You for your feedback.
     
  5. Hi, i used --forceUpgrade from 1.15.2 to 1.16.1 but 1 hour has passed and still says 0 chunks
    Code (Text):
    [05:24:04 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:05 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:06 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:07 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:08 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:09 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:10 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:11 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:12 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:13 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:14 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:15 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:16 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:17 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:18 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:19 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:20 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:21 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:22 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:23 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:24 INFO]: 0% completed (0 / 4211376 chunks)...
    [05:24:25 INFO]: 0% completed (0 / 4211376 chunks)...
     
     
  6. Hi everyone, I have rather a weird question, when having multiple worlds in one server folder, and I do --forceupgrade, it only takes the world that is mentioned in the server.properties...
    Was wondering if this is the problem that is currently being repaired or is it new?
    Because I think when naming every world seperately in a following order upgrade in 1.15.2 and then 1.16.1, after that take the next world, should this work... gonna try that...

    reply to myself: hmmm, does not work at all, It only takes the word World and nothing else.....
    Oh, and I was in a cave and it rained outside, well, in the cave it rained as hard too..... Must be something weird Mojang had to do with....
     
    #186 Ms_Killer01, Jun 29, 2020
    Last edited: Jun 29, 2020
  7. You started first with 1.15.2 --forceupgrade?
     
  8. Thank you!

    If i have a 1.12.2-Server i have to update to 1.15.2 first. And then update to 1.16.1? Otherwise my world will be ruinned?
     
  9. First, make a backup! I would go straight from 1.12.2 to 1.16.1 with --forceUpgrade. (md_5 may have a different suggestion.) I tried going version by version from 1.12 to 1.14 and something got corrupted. So I would just try it in one shot. If there's a problem, that's why you have the backup. :cool:
     
  10. Do you normally use Multiverse or some other world management plugin? Did you have the plugin loaded when doing --forceUpgrade? You need the plugin for Spigot to find the worlds to upgrade.
     
  11. I think, you can´t see many errors in the world. And if you see them month ago, you can´t use the backup. So i am looking for the savest way to update.

    I didn´t know the --forceUpdgrade-command. Is it new? I am used to the build-tools-update method.
     
  12. Hi, I have a problem with 1.16.1. I cant disable advancements. I disabled it in spigot.yml as always (in 1.14 and 1.15 it worked) but here it wont work. Advancements arent saving but they are still visible in player menu and they are still displaying in chat. I dont want them. And I dont want to just hide them by gamerule. It's only hide. I want to real disable them. Please fix it :(
     
  13. It's one of the startup parameter options for running spigot. Before you update your spigot file (after you backup your world files) add the --forceUpgrade parameter to the start script and run, and then update spigot and run the new version with --forceUpgrade again, then remove that parameter and you should be good to go.
    I think this was in the first post...
     
    #193 MrKylen, Jun 29, 2020
    Last edited: Jun 29, 2020
    • Like Like x 1
  14. --forceUpgrade (did I get it wrong before?) was added in 1.13. See https://twitter.com/Dinnerbone/status/1019633458635829254
    It upgrades the map files to the new version. So after you update your spigot jar file, the first time (and it's a one-time only thing), use --forceUpgrade at the end of the command to update your map files.
     
    • Like Like x 1
  15. I have same problem. Map was generated by 1.15.2 and now I downloaded 1.16.1 spigot and runned with `--forceUpgrade`... After 1 hour still no single upgraded chunk.
     
  16. Shaggy67

    Supporter

    This is what md5 says in the first post...

    Upgrading
    Although upgrades from between any two version pairs are technically possible, it is recommended that all upgrades are conducted from 1.15.2. This means that you should first upgrade your world completely on 1.15.2 using the --forceUpgrade server argument, and then do the same on 1.16.1.
     
  17. It will take forever. If the map is large, the count is enormously huge, my map is about 90gb and after 17 hours I'm at 19%.

    @md_5 what can happen if I run a 1.15.2 world in 1.16.1 without upgrading chunks? Or is there a way to speed up the process? I can see that the server isn't using so much cpu or ram, and it's on a nvme ssd so why is this process so slow?
     
  18. The chunks will be upgraded as players explore the world. Expect lag spikes in that case.

    It seems to be using only two cores on my PC. Too bad it can't use all 8 cores.

    My 7.8 GB worlds took 90 minutes to upgrade on my i7-9700K running at 4.6 GHz with an NVMe PCIe drive.
     
  19. Damn, I'll stop it immediately and I'll let it run!

    I have a Ryzen 3700X and it's converting 200 chunks/sec...
     
  20. That's great to hear! Thank you very much for your amazing work, and the ability to use Spigot!