more bugs in 4.0.5 (?)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Tibarius
    Swordsman
    • Jun 2011
    • 429

    more bugs in 4.0.5 (?)

    Hi,
    so i played 4.0.5 to have the latest data for my players guide. Unfortunately there are a more things "odd" which i would mark as bugs:

    1. Rod of Probing does not reveal the breath attacks anymore. I hope that's a bug and not a feature.

    2. In the monster recal information window the electricity element is shown in yellow color even with permanent and temporary resistance active. It was for major multi-hued dragon and another monster so i assume this is valid for all monsters.

    3. Monster Name: dwar, dog lord of waR (not of waw)

    4. Game Turn count is sometimes obviously wrong, just started the game and did maybe a couple of dozens turns and the count is already close to 3000. No further (more accurate) information about this bug available tho.
    Last edited by Tibarius; June 27, 2016, 09:52.
    Blondes are more fun!
  • AnonymousHero
    Veteran
    • Jun 2007
    • 1393

    #2
    Originally posted by Tibarius
    3. Monster Name: dwar, dog lord of waR (not of waw)
    It's actually not a typo. Waw is a place, though this is obviously non canon.

    Comment

    • Pete Mack
      Prophet
      • Apr 2007
      • 6883

      #3
      Appears to be a memory corruption bug in REMOVE_RANDOM_STAT handler, for !Toughness. when the randomly selected stat is CON, the pointer will go out of bounds, and decrement who knows what.

      Edit:
      I noticed that once you get to stat 18-18/75 stat swap is actually a net gain, since the gain is usually greater than 1, but the loss is always exactly 1. (Above 18/75 or so, the stat swap is a net loss.)

      Comment

      • shadow
        Rookie
        • Oct 2014
        • 13

        #4
        Originally posted by Tibarius
        Hi,


        1. Rod of Probing does not reveal the breath attacks anymore. I hope that's a bug and not a feature.
        Doesn't seem to reveal summons either? Those are the two things I'd want to know.

        Comment

        • Bogatyr
          Knight
          • Feb 2014
          • 525

          #5
          Originally posted by shadow
          Doesn't seem to reveal summons either? Those are the two things I'd want to know.
          Also doesn't reveal previously unknown resistances. The only thing it seems to reveal is physical attacks. The rod of probing is weaker in 4.x than in 3.x because of this. In 3.x it did not reveal magical or breath attacks either until you've seen one (or more) of them.

          Comment

          • Pete Mack
            Prophet
            • Apr 2007
            • 6883

            #6
            Bug in mon-lore for chance to hit.
            The chance should be .12 + .83*chance, where
            chance, where chance = (adj_skill-2/3AC)/adj_skill
            The reported hit chance is significantly higher (by 7%, fully buffed, for my current mage vs Sauron)

            Comment

            • Nick
              Vanilla maintainer
              • Apr 2007
              • 9637

              #7
              Originally posted by Pete Mack
              Appears to be a memory corruption bug in REMOVE_RANDOM_STAT handler, for !Toughness. when the randomly selected stat is CON, the pointer will go out of bounds, and decrement who knows what.
              Thanks, that code was garbage - fixed in development.
              One for the Dark Lord on his dark throne
              In the Land of Mordor where the Shadows lie.

              Comment

              • luneya
                Swordsman
                • Aug 2015
                • 279

                #8
                I just downloaded the latest nightly (15 Oct 2016 at 22:34 UTC, revision 76734a1, OSX precompiled version), started up a new character, and got hit with an annoying bug right away. I chose not to take a starting kit, and when I looked in the weapon shops, everything had its damage dice marked as 0D0, and a corresponding 0 average damage upon inspection. I bought something at random, and proceeded to whack a defenseless townsman with it. Said townsman did take damage and die, but the weapon in my inventory still showed 0D0 and 0 average damage. My character screen did show the correct damage for the equipped weapon (1D8 for a cutlass, as opposed to 1D1 when I took it off), so I suppose it's not technically unplayable, but I'm not going to bother.

                I can post a save if you want, but it's literally a new game just off of character gen, so I doubt it'll help.

                Comment

                • Nick
                  Vanilla maintainer
                  • Apr 2007
                  • 9637

                  #9
                  Originally posted by luneya
                  I just downloaded the latest nightly (15 Oct 2016 at 22:34 UTC, revision 76734a1, OSX precompiled version), started up a new character, and got hit with an annoying bug right away. I chose not to take a starting kit, and when I looked in the weapon shops, everything had its damage dice marked as 0D0, and a corresponding 0 average damage upon inspection. I bought something at random, and proceeded to whack a defenseless townsman with it. Said townsman did take damage and die, but the weapon in my inventory still showed 0D0 and 0 average damage. My character screen did show the correct damage for the equipped weapon (1D8 for a cutlass, as opposed to 1D1 when I took it off), so I suppose it's not technically unplayable, but I'm not going to bother.

                  I can post a save if you want, but it's literally a new game just off of character gen, so I doubt it'll help.
                  This one's been reported before - it should right itself once you hit something.
                  One for the Dark Lord on his dark throne
                  In the Land of Mordor where the Shadows lie.

                  Comment

                  • luneya
                    Swordsman
                    • Aug 2015
                    • 279

                    #10
                    As I said in my post, I did indeed hit something with the weapon. Specifically, I killed some of the beggars in town. The sword was still reading 0D0 after doing so.

                    Comment

                    • Nick
                      Vanilla maintainer
                      • Apr 2007
                      • 9637

                      #11
                      Originally posted by luneya
                      As I said in my post, I did indeed hit something with the weapon. Specifically, I killed some of the beggars in town. The sword was still reading 0D0 after doing so.
                      OK, thanks.
                      One for the Dark Lord on his dark throne
                      In the Land of Mordor where the Shadows lie.

                      Comment

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