3.3 RC: squelch/ignore functionality + lvl feelings

[Antoine]

That NPP stuff is genius. I wish I'd thought of it. It needs more wide spread application, and not just in the prevention of scumming (as I envision it). I always thought that you should be given some sort of minor award for exploration. If nothing else it would interesting to see what % of each level is explored, at least I think it would be.

What NPP stuff are you referring to?

A.

[Nick]

What NPP stuff are you referring to?

A.

Did you even read the thread, Antoine?

(Hint - post 8)

[jens]

That NPP stuff is genius. I wish I'd thought of it. It needs more wide spread application, and not just in the prevention of scumming (as I envision it). I always thought that you should be given some sort of minor award for exploration. If nothing else it would interesting to see what % of each level is explored, at least I think it would be.

To me it has always felt like it must be too high an overload just to avoid stairscumming. But I guess todays computers can handle it... But I like Angband being able to run well on any old machine as well.

In any case I really like the idea of using it for a lot of other stuff that we might think of. I've also wanted an award for exploring, for instance ;-)

[Antoine]

Did you even read the thread, Antoine?

(Hint - post 8)

No need to shout. I thought it might have been a reference to Derakon's #13 - "variants that explicitly try to start the player out in a cul-de-sac without any monsters nearby" - which NPP does - but wasn't sure, hence the question.

A.

[Nick]

No need to shout. I thought it might have been a reference to Derakon's #13 - "variants that explicitly try to start the player out in a cul-de-sac without any monsters nearby" - which NPP does - but wasn't sure, hence the question.

A.

Sorry #jokefail

[bulian]

Just bumping the bulk of the initial post to hopefully get some clarification on the new "ignore" function. Thanks.

- What happened to the destroy command 'k'? It has been replaced by "ignore" which has seemingly weird functionality. I accidentally hit the "ignore all" on some !CSW I had while trying to destroy something on the ground. The !CSW started acting as if squelched unless in "unignore mode" - going back to regular mode causes them to disappear from inventory, though they are not toggled under the squelch menu or the "autoinscription menu" as being squelched. If "ignore" has the same functionality as squelch they should be linked to the submenu. To undo this I had to go into unignore mode ('shift + k') and 'destroy' the stack again ('k'). What was wrong with destroy? Does "ignore" on an unidentified artifact cause the artifact to remain visible? It seems to have no effect on identified artifacts. Personally not a fan of this change.

[Derakon]

Yeah, objects can't be destroyed any more. Destruction has been replaced by squelching just that one object, which has the disadvantage of requiring more keystrokes and the advantage of being reversible in the event of accidents. "Ignore" and "squelch" should directly correspond to each other, so if you encounter a situation in which a class of items (as opposed to a specific item or stack of items) is ignored but not updated in the squelch or knowledge menus, that probably qualifies as a bug.