I don't really mind - they're really not much different from their V versions. Not to say you won't find something that's broken about those, like you did for rangers...

Now I am gretting crashes when leaving the options menue (2nd hit of "ESC") while setting up the subwindows ... started with v226 and happens with v259 as well.
Everything is fine until I try to put PLAYER(EXTRA) on any Term.

... and STATUS doesn't seem to do anything?!?

Latest update should fix this, thanks to backwardsEric and Cuboideb.

FIXED.

But ...

Now I can't leave the "Help file 'commands.txt'" ... SPACE took me to the 2nd page, ESC did not work, screen was only flickering as if trying to do something, then refreshing the help screen.
ESC did work on the subwindows option screen, though. ;)

UPDATE: I tried to close FAA2 using the X button. Little window came up said "you must close all windows". Ok, tried ESC again - and it worked "down" to the main window.

UPDATE2: Can't recreate this. Sadly, can't remember which "exotic" key combination I used that didn't work so the game prompted me to use "?" which I did, what got me stuck in the help screen ...


... aaaand another one:

3-headed hydras aren't supposed to be invisible, right?
Yet, after encountering a "Q", things have started to (not) show up in a strange way. At first I had some small things gnaw at me, that a staff of "Detect Invisible" couldn't detect.
Now I had a Hydra standing right next to me and bite me 2x, and I didn't see it until I used a Rod of Detection?!
The detected invisible monster should be the Mystic "p", right?
I hit it, and it turned invisible again "You miss something. You freeze something (46)". A hydra. Right next to me!?!?
https://smilies.4-user.de/include/So..._sonst_027.gif https://smilies.4-user.de/include/So..._sonst_031.gif ... taptaptaptap ... taptaptapsmack :cool: GROAARR!!! https://smilies.4-user.de/include/Br...ilie_b_352.gif

Is this some new kind of curse? If not, dear devs, you do not need to take note, really ...

Yes, I tried to make a living from this. Didn't work out. Considering the working conditions in the computer gaming industry today, I guess that is a good thing ...

This does seem odd. Do you have the savefile (and randart file if it's not the same character as before)?

I couldn't reproduce the help issue either.

It is.
I have attached the savefile.

No problem, I couldn't either.
Must have been some SHIFT-letter combination .. let me try some ...

OMG!
The auto-ignore-inscription is back! And again the game does not ask every time if I want to drop that ring in the d)-slot.

Did not notice the inscription before I reloaded the save and tried the keys ... and after using SHIFT-K it's gone again?!?!
Why does using SHIFT-K inscribe (and partly uninscribes) slot d) or e) jewelry with "ignore" or "!d, ignore" ... isn't it supposed to do nothing?

Must have been some other key combination that send me to the ?-files, though.

And the Hydra still vanished on the next turn ...

.
And the next one!
At least this one seems to be reproducable from the savefile:
Just ignore the Hyrda and step south-east on the broken door ...
Does not happen on the northern broken door, though.

OK, here's what I have on these ones:

• If you used release 265 or 266, there was a bug introduced which would explain the crash; fixed in 268.
• The hydra being invisible I cannot reproduce.
• 'K' is supposed to make all the already ignored things visible; my guess here is that there's something leftover in your ignoring settings from before I removed the possibility of ignoring ring and amulet types, and now there's no way to remove it...

Not sure if it's the same thing, but there were situations during my Ranger game where I seemed to be having problems directly seeing monsters (but could see them just fine with detects)--I figured it was lighting problems, and never looked into it enough to determine whether it was a bug or not.

To that end, if it's not implemented already, I would suggest explicitly marking any monster that projects unlight as doing so in monster memory, to make ruling such out (or not) easier (I'd just check my monster memory to see if it was implemented, except I seem to have deleted it).

It is implemented already - I will keep on eye out for this problem, though.