Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#302 closed change (fixed (in master))

Monster order in monsters.txt versus monster memory behavior

Reported by: ctate Owned by: ctate
Milestone: 3.1.0 Keywords: ui


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'.

Change History (3)

comment:1 Changed 13 years ago by ctate

  • Resolution set to fixed
  • Status changed from new to closed

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

comment:2 Changed 13 years ago by ctate

  • Keywords ui added

comment:3 Changed 12 years ago by takkaria

  • Milestone changed from 3.2.0 to 3.1.0
Note: See TracTickets for help on using tickets.