Bukkit, CraftBukkit, Spigot & BungeeCord 1.13.1 Development Builds

Discussion in 'News and Announcements' started by md_5, Aug 26, 2018.

Thread Status:
Not open for further replies.
  1. So after applying '--rev 1.13.1' to BuildTools, the program is throwing heaps of errors... not expecting this!
     
  2. Ah, well my bad then. Thank you for an insanely quick answer, lol.

    Sent from my E6653 using Tapatalk
     
  3. Many builds on our world date back to 1.8 days and I vaguely remember the combat update (1.9) causing similar issues. Ppl recommended I boot the new server and let it spawn a new world but then to shut down and overwrite with your existing world. Preventing data loss upon reboot and that worked perfectly for us

    Does this method no longer work with 1.13.1?
     
  4. md_5

    Administrator Developer

    I don't see what that method would achieve...
     
  5. Can I run 1.13.1 on a world that was generated on 1.13, or would I still need to --forceUpgrade?

    (Obviously taking backups beforehand, etc.)
     
  6. md_5

    Administrator Developer

    As always it'll be upgraded only the fly. You may get better performance with a forceupgrade but probably not as significant as from 1.12
     
    • Like Like x 1
  7. md_5

    Administrator Developer

    Guess what, apparently chests being emptied on chunk borders isn't fully fixed.

    Guess we're staying red.
     
    • Informative Informative x 9
  8. Thank you for letting us know. I just copied over 40gb from remote servers to do local convert tests, guess I will just do some tests to build experience
     
    #108 mrfloris, Aug 28, 2018
    Last edited: Aug 28, 2018
    • Agree Agree x 1
  9. Would you mind telling me what the errors are? Because I had errors too when running BuildTools which I had not had before
     
  10. Will there be a 1.13.2 update? And will broke the 1.13.1 worlds?
     
  11. Mojang decides whether there will be a 1.13.2 update, but seeing how unstable 1.13.1 currently is, I'd be surprised if there won't be a 1.13.2 update.
     
  12. It's my morning routine. /version followed by buildtools.
    I really appreciate all the hard work you guys do.
     
    • Agree Agree x 1
  13. Well for starts, I am running on Windows 7, here is the batch file I use to start BuildTools

    @Echo off
    set startdir=%~dp0
    set bashdir="C:\Program Files\Git\bin\bash.exe"
    %bashdir% --login -i -c "java -jar BuildTools.jar --rev 1.13.1"
    pause

    The errors are then:


    Exception in thread "main" org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of reset command. Cannot lock C:\Users\Tim\Desktop\Buildtools\Bukkit\.git\index
    at org.eclipse.jgit.api.ResetCommand.call(ResetCommand.java:234)
    at org.spigotmc.builder.Builder.pull(Builder.java:570)
    at org.spigotmc.builder.Builder.main(Builder.java:287)
    at org.spigotmc.builder.Bootstrap.main(Bootstrap.java:29)
    Caused by: org.eclipse.jgit.errors.LockFailedException: Cannot lock C:\Users\Tim\Desktop\Buildtools\Bukkit\.git\index
    at org.eclipse.jgit.dircache.DirCache.lock(DirCache.java:250)
    at org.eclipse.jgit.dircache.DirCache.lock(DirCache.java:327)
    at org.eclipse.jgit.dircache.DirCache.lock(DirCache.java:293)
    at org.eclipse.jgit.lib.Repository.lockDirCache(Repository.java:1183)
    at org.eclipse.jgit.api.ResetCommand.checkoutIndex(ResetCommand.java:404)
    at org.eclipse.jgit.api.ResetCommand.call(ResetCommand.java:207)
    ... 3 more


    Also I think it may be trying to pull the same version as without the --rev, which resulted in a 1.12.2 version...
     
  14. Choco

    Moderator

    Still as present as it's always been. Both in lang 2.6 (Bukkit) and lang 3 (NMS)

    [​IMG]
     
  15. Change to the working dir, don't just define it.
     
  16. MiniDigger

    Supporter

    Should prolly consider to sync bukkit and nms versions
     
  17. Choco

    Moderator

    It will break any plugin using Lang 2.6. Not an option.
     
  18. You mean like moving Gson a few versions ago broke any plugin using Gson?
     
    • Like Like x 1
  19. Choco

    Moderator

    Correct. That was a tough decision from md_5 in and of itself. The only reason Bukkit made the jump in 1.12 is because Mojang also made a massive jump in library updates for the majority of their libraries. It was best for the API to move alongside its implementation.
     
  20. MiniDigger

    Supporter

    Wasn't it always set that bukkit libs are in sync with vanilla? So a jump by mojang should be mirrored by bukkit. Else we will end up with ancient libs and we all know how that worked out for ebean
     
    • Agree Agree x 2
Thread Status:
Not open for further replies.