Angband 3.3.2 RC1

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Magnate
    Angband Devteam member
    • May 2007
    • 5110

    Angband 3.3.2 RC1

    Windows and Mac builds are both available here.

    This release candidate fixes the slow/haste monster bug, and possibly fixes the numpad issues on Windows - feedback from Windows users most welcome.
    "Been away so long I hardly knew the place, gee it's good to be back home" - The Beatles
  • david3x3x3
    Scout
    • Jun 2009
    • 28

    #2
    I pushed out the 3.3.1 update to the Android market yesterday before I saw the slow monster bug report. I quickly grabbed the fix for that one, so the current Android market version is 3.3.1 with the slow monster fix.

    Comment

    • Magnate
      Angband Devteam member
      • May 2007
      • 5110

      #3
      Originally posted by david3x3x3
      I pushed out the 3.3.1 update to the Android market yesterday before I saw the slow monster bug report. I quickly grabbed the fix for that one, so the current Android market version is 3.3.1 with the slow monster fix.
      It's not good to have different versions floating around with the same number - next time pls could you call it x.y.z-android1 or something. (Or did you name it with git describe?)
      "Been away so long I hardly knew the place, gee it's good to be back home" - The Beatles

      Comment

      • PowerWyrm
        Prophet
        • Apr 2008
        • 2987

        #4
        The link to the Windows version of yesterday's build (873f1fb) is missing. But I can confirm that the numpad bug is fixed in the c2a6c97 build.
        PWMAngband variant maintainer - check https://github.com/draconisPW/PWMAngband (or http://www.mangband.org/forum/viewforum.php?f=9) to learn more about this new variant!

        Comment

        • Magnate
          Angband Devteam member
          • May 2007
          • 5110

          #5
          Originally posted by PowerWyrm
          The link to the Windows version of yesterday's build (873f1fb) is missing. But I can confirm that the numpad bug is fixed in the c2a6c97 build.
          Excellent!

          Sorry about the non-appearance of the Windows builds. Apparently there is a little problem with the buildbot scripts that causes this (they build fine, but they don't get uploaded to that list properly).
          "Been away so long I hardly knew the place, gee it's good to be back home" - The Beatles

          Comment

          • BlueFish
            Swordsman
            • Aug 2011
            • 414

            #6
            Originally posted by Magnate
            Windows and Mac builds are both available here.

            This release candidate fixes the slow/haste monster bug, and possibly fixes the numpad issues on Windows - feedback from Windows users most welcome.
            in c2a6c97, when i try to inscribe something with @w0, it comes out as @w00. Ever time I hit a number, it appears twice.

            Comment

            • Magnate
              Angband Devteam member
              • May 2007
              • 5110

              #7
              Originally posted by BlueFish
              in c2a6c97, when i try to inscribe something with @w0, it comes out as @w00. Ever time I hit a number, it appears twice.
              Which OS and version are you using? Does this happen with keyboard numbers or only with numpad numbers?
              "Been away so long I hardly knew the place, gee it's good to be back home" - The Beatles

              Comment

              • d_m
                Angband Devteam member
                • Aug 2008
                • 1517

                #8
                Originally posted by BlueFish
                in c2a6c97, when i try to inscribe something with @w0, it comes out as @w00. Ever time I hit a number, it appears twice.
                Can you try d6f687e linked from http://buildbot.rephial.org/builds/3...e/builds.html?

                That should hopefully fix this.
                linux->xterm->screen->pmacs

                Comment

                • Magnate
                  Angband Devteam member
                  • May 2007
                  • 5110

                  #9
                  Originally posted by d_m
                  Can you try d6f687e linked from http://buildbot.rephial.org/builds/3...e/builds.html?

                  That should hopefully fix this.
                  We'll call that 3.3.2RC2 ... thanks to Blubaron and d_m for (possibly) fixing it ...
                  "Been away so long I hardly knew the place, gee it's good to be back home" - The Beatles

                  Comment

                  • BlueFish
                    Swordsman
                    • Aug 2011
                    • 414

                    #10
                    Originally posted by d_m
                    Can you try d6f687e linked from http://buildbot.rephial.org/builds/3...e/builds.html?

                    That should hopefully fix this.
                    Yes, that fixed it! Thanks!

                    Comment

                    • david3x3x3
                      Scout
                      • Jun 2009
                      • 28

                      #11
                      Originally posted by Magnate
                      It's not good to have different versions floating around with the same number - next time pls could you call it x.y.z-android1 or something. (Or did you name it with git describe?)
                      The android app actually has its own version number. In this case it is 3.3.1.2. I think the splash screen still shows 3.3.1. I'll try to follow your suggestion for that number in the future.

                      Comment

                      Working...
                      😀
                      😂
                      🥰
                      😘
                      🤢
                      😎
                      😞
                      😡
                      👍
                      👎