Where to report bugs

Collapse
This is a sticky topic.
X
X
 
  • Time
  • Show
Clear All
new posts

  • backwardsEric
    replied
    Originally posted by eschiss1
    Edit: really, I'd as soon find out how to do a nice clean uninstall, and then I can reinstall this port which should fix things.
    What's needed for a clean uninstall will depend on what front end you're using. With the Mac front end, you would remove the installed application, remove ~/Documents/Angband which has the save files and other user-generated data, and run

    Code:
    defaults delete org.rephial.angband
    from a terminal to clear the saved settings for the front end. For the curses/X11/SDL/SDL2 front ends, what's needed will depend on how it was configured and built. For a no install build with private user files, remove the directory where Angband was built and ~/.angband/Angband . For the Windows front end, I believe you can get a clean uninstall by removing the directory that was created by unpacking the .zip file for the Windows release (i.e. Angband-4.2.5 for Angband 4.2.5).

    Leave a comment:


  • eschiss1
    replied
    Originally posted by Nick
    I believe I've now set it up so you can submit an issue without having a github account. Could you please try?
    Not anymore, apparently. (Weird bugs, too, monster memory is no longer working for the borg, and every save in-game is creating a new copy rather than overwriting, though these may be partially my fault as this was working before I fiddled with something I oughtn't have...)
    Edit: really, I'd as soon find out how to do a nice clean uninstall, and then I can reinstall this port which should fix things.

    Leave a comment:


  • Pete Mack
    replied
    Why are "Onyx rings" red colored? I had to look at the detailed item list and count squares to figure it out.

    Edit: never mind. I see it can be either color, though the red is usually called "Sardonyx."

    Leave a comment:


  • kineahora
    replied
    RandArts issue

    So I have a RandArt called the Ring of Estel.

    Description for activation says it "Restores 4d8 hitpoints and cures poison"

    I havent tested it while poisoned, but when injured it says simply "You activate it" and 0 hitpoints are restored. Seems like a bug to me.

    Leave a comment:


  • Julian
    replied
    Stun resistance protects you against mystics.

    Leave a comment:


  • PowerWyrm
    replied
    Originally posted by BrianGiles
    I have come across being knocked out on three separate occasions by Grand Master Mystics when I clearly have multiple equipped items that give "Free Action". How can that happen?
    Free Action doesn't prevent KO from physical or magical attacks. For magical attacks you need "resistance to stunning". For physical attacks there is no resistance, only a high AC will prevent getting stunned by attacks that have xd1 or xd2 dice by simply "dodging" such attacks. A common practice is to avoid master mystics because there's nothing to gain fighting them.

    Leave a comment:


  • BrianGiles
    replied
    How Can you be "Knocked Out" if you have "Free Action"

    I have come across being knocked out on three separate occasions by Grand Master Mystics when I clearly have multiple equipped items that give "Free Action". How can that happen?

    Leave a comment:


  • Aloise Harvey
    replied
    Originally posted by Derakon
    Then you'd have each bug in the same thread, which can make reports harder to track down.
    I support you on this. It would take ages for a person to find out a solution to a bug they are facing

    Leave a comment:


  • DavidMedley
    replied
    I just anonymously reported "sho bobs" but I haven't received any bobs yet

    Leave a comment:


  • Nick
    replied
    Originally posted by Sparrow the Dunadan
    Problem is you have to have acct with github, or sign up. This requires answering some very personal questions that have nothing to do with the issue being reported.
    I believe I've now set it up so you can submit an issue without having a github account. Could you please try?

    Leave a comment:


  • Sparrow the Dunadan
    replied
    Originally posted by Nick
    New preferred method of reporting bugs is to create a new issue here.

    Here are step-by-step instructions for reporting a bug. Depending on the nature of the bug, it may be worth some preliminary enquiries to see whether it is actually a bug or simply a wonderful, surprising piece of game design.
    1. Go to the issues page on Github.
    2. Click the green "New Issue" button near the top right.
    3. Give a short descriptive title to your bug; if it's not a report for the current official release, please include what version it it in your title.
    4. In the "Write" pane below the title, give sufficient details to fully describe the problem; this can include links.
    5. Add any relevant files (a savefile is sometimes helpful).
    6. Click "Labels" on the right and add a type label from the list (they start with "T:") - usually you will want T: bug.
    7. Click "Milestone" on the right and choose the "Triage" milestone.
    8. Click the green "Submit new issue" button at the bottom and you are done.
    Problem is you have to have acct with github, or sign up. This requires answering some very personal questions that have nothing to do with the issue being reported.

    Leave a comment:


  • Pete Mack
    replied
    Not a bug. HP are alotted to CON in 1/10 HP increments. You are seeing two 1/2 HP increments adding up to 1.

    Leave a comment:


  • gtrudeau88
    replied
    Interesting bug

    Here's the deal. I started a new game from a previous character so I have Aragorn II, duedain warrior. But I didn't keep the stats from the original character because I wanted to change some things. The original had a starting CON of 17, giving him a hit die of 20. The new char had a CON of 15 giving him a hit die of 19. I started with 19 hp as expected but when I progressed to character level 2 I jumped to 39 hp, an increase of 20. I like the bug, but it is a bug nevertheless.

    Leave a comment:


  • Nick
    replied
    New! Improved!

    New preferred method of reporting bugs is to create a new issue here.

    Here are step-by-step instructions for reporting a bug. Depending on the nature of the bug, it may be worth some preliminary enquiries to see whether it is actually a bug or simply a wonderful, surprising piece of game design.
    1. Go to the issues page on Github.
    2. Click the green "New Issue" button near the top right.
    3. Give a short descriptive title to your bug; if it's not a report for the current official release, please include what version it it in your title.
    4. In the "Write" pane below the title, give sufficient details to fully describe the problem; this can include links.
    5. Add any relevant files (a savefile is sometimes helpful).
    6. Click "Labels" on the right and add a type label from the list (they start with "T:") - usually you will want T: bug.
    7. Click "Milestone" on the right and choose the "Triage" milestone.
    8. Click the green "Submit new issue" button at the bottom and you are done.
    Last edited by Nick; February 4, 2020, 21:10. Reason: Edit: Cross out things most people can't do

    Leave a comment:


  • mattmiller057
    replied
    Do we have a sticky on that bug report? Yet!

    Leave a comment:

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