2 ms·

Apparently the patch for the bug I reported in 2004 (C343-20) didn't make it into this version, despite being fixed four years ago. The glacial timescales are k

• hapnin 9y ago
  They just moved to github so maybe time will be measured in months instead of decades.
  • earenndil 9y ago
    They didn't move to github, they just maintain a mirror on github.
• ggm 9y ago
  Your pull request crumbles into dust...
  • Alex3917 9y ago
    Not my PR! The issue is that if you die by having a cursed ball and chain fall onto your head while descending a staircase, the screen doesn't transition to the lower level so it's not clear on which level the bones file would be generated. (Per emails from the dev team, it does get correctly generated on the lower level.) Apparently fixing this issue somehow required rewriting huge portions of the graphics engine, which probably explains the snarky comment next to the bug in the issue tracker. :-)
    • simcop2387 9y ago
      That's one hell of a bug to find. That's kind of hilarious. That does suck about how difficult to fix though.
    • danShumway 9y ago
      :) To be fair, if I was writing any program and someone came to me with a bug like that, my first thought would be "#!@? I don't want to deal with this."
    • ckemere 9y ago
      Confused - the change log includes "don't show the old level when you die going down the stairs because of an iron ball"