Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#848 closed change (fixed (in master))

Make the monster list more useful

Reported by: jamievicary@… Owned by: magnate
Milestone: 3.1.1 beta Keywords:


There is currently no easy way to tell how far away monsters are, and if you have some form of ESP, it's often difficult to tell if a particular monster is actually in your line of sight. Both of these are important to know if you want to shoot something at the monster, and it's a hassle to always have to go into targeting mode via * to find out.

These problems would be solved if the monster list was made more useful. Here's an example of how it could look:

You can see 2 monsters:
L Lich (60')
o Uruk (100')

You are aware of 19 other monsters:
k Kobold shaman (310')
o Uruk (x18, at least 120')

Here's the forum discussion.

Change History (6)

comment:1 Changed 11 years ago by magnate

If we're going in this direction, could we please also add asleep/awake to the list? That's another piece of info you can get via the Look command, and it would remove a lot of tedium to have it shown on the list. So:

You can see 2 monsters:
L Lich (60', asleep)
o Uruk (100', awake)

etc. Also - could we put them in order of depth?

comment:2 Changed 11 years ago by magnate

  • Owner set to magnate
  • Status changed from new to assigned

[57756ec] (SVN r1415) has them in depth order. I'll have a look at asleep/awake and distance.

comment:3 Changed 11 years ago by jamievicary@…

Cool! I really think the most important thing is splitting the list into into those in field of view, and those not. The depth and asleep/awake would also be very useful, of course.

comment:4 Changed 11 years ago by magnate

  • Milestone changed from Triage to 3.1.2 beta

I think the optimum is in-LOS and outside LOS using player_has_los_bold(y, x), in depth order, colour coded by speed, with #awake noted after the number of monsters.

A bit of work, but should be doable.

comment:5 Changed 11 years ago by magnate

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

[65e4a05] (SVN r1418)

comment:6 Changed 11 years ago by magnate

  • Milestone changed from 3.1.2 beta to 3.1.1 beta
Note: See TracTickets for help on using tickets.