Ticket #302 (closed feature: fixed)

Opened 1 year ago

Last modified 8 months ago

Monster order in monsters.txt versus monster memory behavior

Reported by: ctate Assigned to: ctate
Milestone: 3.1.0 Keywords: ui
Cc:

Description

Monster recall asks "Recall details? (k/p/y/n)", offering three different sequences in which to view the set of matching creatures. It's not clear to me that the 'y' ordering is ever useful -- it's the order in which the monsters are defined in monster.txt. Historically this may have been the default, but nowadays there are quite a few "out of order" creatures. For example, the Silver mouse is defined after Morgoth, and Kobold shamans (a depth 3 monster!) are currently monster 604. In earlier days, monster.txt was in strict depth order.

Reordering monster.txt is tedious and (worse) is a savefile breaker. Is there any real reason to offer datafile ordering of recall? I suggest eliminating the unsorted output and collapsing the 'p' behavior to 'y'.

Attachments

Change History

07/29/07 01:39:57 changed by ctate

  • status changed from new to closed.
  • resolution set to fixed.

Fixed in [407]. Unsorted output (monster.txt order) is no longer available; 'y' is now a synonym for 'p'.

07/29/07 02:30:43 changed by ctate

  • keywords set to ui.

05/17/08 09:26:51 changed by takkaria

  • milestone changed from 3.2.0 to 3.1.0.

Add/Change #302 (Monster order in monsters.txt versus monster memory behavior)




Action