Guide to finding your current CraftBukkit build

Discussion in 'Bukkit Help' started by Pezmantbh, Jan 31, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    Pezmantbh

    UPDATE: As of build #204, you can use /version to get your build. If it doesn't work, use the methods below.

    It seems people don't know how to get their current CraftBukkit build, and I knew of a quick and (relatively) easy way to find it.

    Download a compression program
    7zip - This is the one I use, it works well, and therefore I recommend it. http://www.7-zip.org/

    After downloading and installing a compression program, use it to open your CraftBukkit .jar file
    Once it is open, you should see 5 folders:

    com​
    joptsimple​
    META-INF​
    net​
    org​

    and two files:
    font.txt​
    null​

    You need to open the META-INF folder and then drag/extract the MANIFEST.MF file to a location on your computer (It is probably easiest for you to use the desktop).
    Open MANIFEST.MF in a text editor, and you should see something similar to this:
    Code:
    Manifest-Version: 1.0
    Build-Jdk: 1.6.0_22
    Built-By: bamboo
    Build-Version: git-Bukkit-something-188
    Created-By: Apache Maven
    Main-Class: org.bukkit.craftbukkit.Main
    Archiver-Version: Plexus Archiver
    
    The line you are looking for is
    Build-Version: git-Bukkit-something-188

    The 188 contains your build number.

    Newer builds of Bukkit will contain the build version in this format:
    Implementation-Version: git-Bukkit-0.0.0-323-g29e96e1-b241
    Where b241 is Build 241.

    Linux
    To find the build on a linux server, there is a much easier way - Just use this command:
    Code:
    zgrep -i version craftbukkit.jar
    This is confirmed to be working on Ubuntu, but should work on other distro's too.
     
  2. Offline

    mughi

    Found this in another thread: thanks @MonsieurApple
    Listed as Ubuntu, may or may not work on other flavors
    zgrep -i version craftbukkit.jar
    and you should get something like

    Code:
    Manifest-Version: 1.0 Build-Version: git-Bukkit-something-164 Archiver-Version: Plexus Archiver
    In this case, I have craftbukkit build #164.
     
  3. Offline

    Pezmantbh

    This was generally for windows :)

    Edited main post to include it for linux
     
  4. Offline

    TnT Retired Staff

    I have a terrible memory. I still find it easier to remember the build number than to open up the jar file with 7zip and do what is listed here.

    Well, except for the Linux version. That shit is the bees knees man.
     
  5. Offline

    Pezmantbh

    There are a few commands that do similar things to zgrep, but they just don't decompress the file and therefore don't work. I could code a utility to do it myself, but I see no need...


    EDIT: Would you like a .exe file whereby you simply execute it and it puts your build in build.txt ? I could whip this up tomorrow, if it would be useful for anyone.
     
  6. Offline

    mughi

    can we sticky this or something? there are like 3-4 topics on the first page asking the same thing
     
  7. Offline

    Valrix

    I'm running OS X and it doesn't give a version number in the manifest. It just says "unknown"
     
  8. Offline

    Pezmantbh

    Can you post the manifest file?

    Thanks :)
     
  9. Offline

    lukegb Retired Staff

    If you use a build not done by me, then it'll say 'unknown' unless the smartypants has figured out how to do it themselves ;)

    Note to self: fix /version to report the build.
     
  10. Offline

    Pezmantbh

    Cheers for that info LukeGB :)

    Just so you know, I looked at the last builds by several authors, and all showed the version - I guess that the build Valrix tried was by an Author I didn't try or before they started putting in the build info :)
     
  11. Offline

    MonsieurApple

    Huzzah zgrep!
     
  12. Offline

    TnT Retired Staff

    Thank you sir!
     
  13. Offline

    lukegb Retired Staff

    ...they better be putting the version in the right format, or I'll throw a hissy fit.

    Note: I do not currently use the correct format, due to some outstanding technical difficulties.

    Correct format:
    git-Bukkit-GITSHORTTAG(-RESERVED)

    Where GITSHORTTAG is the git shorttag, and RESERVED is reserved. For me, and whatever use I see fit. Basically, the bracketed bit shouldn't be there.

    Thanks :p (I currently put something in instead of the shorttag, but I'm looking into resolving this soon and the build number in the reserved slot, which I'm not planning to change)

    Authors who need to use the reserved field for something shouldn't, and should instead add a new field to the manifest.
     
  14. Offline

    TnT Retired Staff

    I've linked it in my "...we need this information..." post that is stickied.
     
  15. Offline

    Pezmantbh

    Added some nice bold text at the top of the OP :)

    I think this thread served its purpose for a good 24 hours, and helped a few people out along the way :D
     
  16. Offline

    TnT Retired Staff

    EASIEST WAY TO FIND THE BUILD #:

    In the client, type: /version
     
  17. Offline

    Pezmantbh

    *cough* hence the big bold text at the top of op *cough*

    [​IMG]
     
  18. Offline

    TnT Retired Staff

    I beat you to it. ;)
     
  19. Offline

    Pezmantbh

    Lies... I did it before you posted.

    That was before your post :p
     
  20. Offline

    TnT Retired Staff

    Bah, I was distracted identifying a bug with using /version on ScrapBukkit. I hit reply too late.

    Either way, I deserve all the credit for it. :p
     
  21. Offline

    Pezmantbh

    Lets share the credit :D We can join forces and buy cake though

    Because I see no cake icon, have some raw meat instead [​IMG]

    Enjoy it! :D
     
  22. Offline

    TnT Retired Staff

    ALL. THE. CREDIT. IS. MINE!

    Just kidding. :p Glad we have that feature now instead of jumping through all these hoops. Can you imagine how much simpler our lives will be now? All hookers and blow from here on out!
     
  23. Offline

    Pezmantbh

    Now I have to find something else to make a guide on that will be useful :p Any suggestions? x)
     
  24. Offline

    TnT Retired Staff

    I've wrote all the ones I can think of that fill in any large gaps.

    But a tutorial on how to set up and troubleshoot the permissions plugin would be good - seems most people have trouble with that.
     
  25. Offline

    Pezmantbh

    Thats what I was thinking, but I wasn't too sure when permissions will be integrated into Bukkit by default... Do you have any info on that?
     
  26. Offline

    TnT Retired Staff

    No more than anyone else. I forgot to add the caveat that built in permissions will probably be released by the time you've wrote the troubleshooter document. :p
     
  27. Offline

    Jobsti

    Hehehe nice.... /version
    #207 shows me the version, client freezes, crash
    #210 client freezes directly, crash

    Code:
    java.lang.StringIndexOutOfBoundsException: String index out of range: 89
        at java.lang.String.charAt(Unknown Source)
        at nh.a(SourceFile:152)
        at nh.a(SourceFile:119)
        at pe.a(SourceFile:238)
        at ll.b(SourceFile:346)
        at net.minecraft.client.Minecraft.run(SourceFile:668)
        at java.lang.Thread.run(Unknown Source)
    --- END ERROR REPORT 8b8ea052 ----------
    Yep, fresh mc without mods, no console-message.
     
  28. Offline

    TnT Retired Staff

    http://forums.bukkit.org/threads/version-crashes-client.3131/
     
  29. Offline

    Visagalis

    Manifest-Version: 1.0
    Implementation-Vendor: Bukkit Team
    Implementation-Title: CraftBukkit
    Implementation-Version: unknown
    Specification-Vendor: Bukkit Team
    Build-Jdk: 1.6.0_22
    Built-By: bamboo
    Specification-Title: Bukkit
    Created-By: Apache Maven
    Specification-Version: unknown
    Main-Class: org.bukkit.craftbukkit.Main
    Archiver-Version: Plexus Archiver


    what to do then? :D
     
  30. Offline

    Pezmantbh

    If you think your build is before build 166, then update to 166... If you think it was after 168, update to the latest :)
     
Thread Status:
Not open for further replies.

Share This Page