Did you follow the directions? Like doing tmap mapsetup

Can you give me a map and steps where I can reproduce it?

Hi, the version that is on github is far superior than the package version. It has quite a few critical bug fixes. What I would do is this: 1) tmap dirclear -- this clears the direction queue 2) tmap findme -- to set your current position 3) try mapping now If this still doesn't work, give me steps ...

Thanks for this. It makes me want to add custom right click hooks for the general mud screen now (similar to the mapper hooks I made). I think a hover (word hilited, hover and it fires a sysHoverEvent type thing), double left click (sysEventDoubleLeftClick can hook to auto-attack, etc.), and a right...

If you are running the development version and reporting bugs, you want to ensure they are not occurring in the development branch (the 'master' branch points to SourceForge which is significantly behind)

It's a QTimer. Here's some info on it (https://qt-project.org/forums/viewthread/32970 and http://qt-project.org/doc/qt-5.1/qtcore ... rType-enum). We don't specify any timer type, and the default isn't documented so I have no idea what it is.

This has been addressed in the development versions of Mudlet, and will be available soon enough.

This request defeats the point of hashes. If you don't have unique features, don't use a hash. If you do have a way to figure out one room from the other, then you have something unique -- incorporate that into the string you pass to hash.

Tossing in my native English opinion. The suggestion is far too formal, and how it is currently sounds natural to me.

I imagine you are calling 'hunt <mob>' somewhere else, causing an infinite loop.