dufelt wrote:
If the exit wasn't listed as 'se' then I would accept laziness in my typing as being the cause.
Obvious exits: n(closed) e s(closed) se(closed)
It is, though.
It's appreciated that at some point in the past shop listings became numbered as I can't recall how many times I purchased the wrong item and wasted valuable gold in the process.
To build on this, is there any merit in being able to determine which 'se' applies to which? Could exits be given priority since they are the least innocuous? (you can't cast a direction without a target as well)
I guess anything that can aid disambiguation would be welcomed.
There is a quick solution that will work for now.
Make a client-side alias that works like the following:
alias "open se" send "open southeast"
MUSHClient and the other variants I've tried can handle space-containing aliases, so it should be okay.