Fuzzy match on standard exits could lead to confusion

[MorquinDevlar]

The PR #402 might need an amendment.

When having a room with a "northeast" exit for instance, and not a "north" one. Typing "north" would send you "northeast" without any indication that you typed a specific different direction.

I would suggest to modify this so standard cardinal directions only respond to either a one or two letter abbreviation or the full name. Then we reserve fuzzy matching for custom exits, that we cannot predict abbreviations for.

[Volte6]

Is it terrible for "north" to take a "northeast" exit, when there is no other north exit? Maybe if someone is in complete darkness and cannot see exits.

What about "nor"? Partial matches on exit names isn't a bad thing... it saves on typing.

If we have a situation of there being a "north" and "northeast" exit, and "north" or "nor" accidentally matched for "northeast" that would definitely be bad.

The directional aliases should always be expanded first, so "n" should always expand to "north" before checking for matches.

[MorquinDevlar]

Honestly I was just not expecting it to move northeast since I only used "north" as the exit command. I was more surprised than anything.

I also just wanted to push this here, so I did not forget to look at it.

I'll take a look and see what the easiest solution is. I do know that we always expand the aliases first yes.