Garan

No problem. Glad it's sorted.

Alktor

Hello,

I use "plugins manager" and when I load the plugins, the map open.
Do you know if it's possible to not open the map automatically when we load plugins ?

Regards,
Alktor

Garan

Hi,
With the plugin loaded, click the gears icon near the top left (between the positioning arrows and the region dropdown list).
In the Options dialog, there is a checkbox near the top, just under the Language dropdown list, captioned "Load Minimised". Check that checkbox and click "Save". TerrainMap will now be minimized on load. You can then either use the icon or the chat command "/terrainmap show" to display the map.

The next version (1.36) will have a "/terrainmap options" chat command to display the options dialog directly.

Markulyas

Hi,

Thank you very much for this plugin. I'm a new player (3-weeks) and already feel your plugin is a must have.

I have one question and one possibly bug report.

My question is, is it not possible to have the character marker update on the map in real time, instead of clicking the red location button every time I open the map? Even if not "update in real time", "update when map is opened" will also be good.

Possible bug is, when I add an annotation, ex: Copper as ore node and save it with an empty description field, it automatically adds the title to the description, so I see Copper twice on the annotation. The title is enough, I need no descriptions. If that can be fixed, that would be awesome.

Thanks!

Garan

Ver 1.37 is finally available. This one took even a bit longer than the usual delay due to having a new region to contend with as well as the Mordor region expanding again to the west (eastern expansions are trivial, western expansions are a royal pain). I had hoped to get this out in time for XMas but our Malinois decided to require a 5 hour visit to the emergency vet on Christmas Eve which threw a monkey wrench into my schemes (and left me with a hefty bill and a head cold to boot). Anyway, she is fine and it is here. Enjoy.

Garan

Hi. Thanks for your interest.

As to the auto updating of the location, the answer is unfortunately, no. The API does not allow programmatically accessing the player location so we have to acquire it from the /loc chat command which can only be generated by a user interaction, thus the need to press the update button (which basically just issues the /loc chat command). You can, however, use a programmable keyboard to generate the "/loc" chat command on a timer but I would not recommend doing that if you are actively raiding or doing any other activity where automated chat commands could accidentally start going to the wrong chat channel or otherwise interfere with your game play. You can also assign the /loc chat command to one of the built-in Quickslots and then you could activate it using a key binding instead of using the mouse (you use the /shortcut command to assign the /loc command).

Regarding the annotations, that sounds like it is working as intended since the annotations are actually added by a second plugin that has to be sent the parameters to add the annotation in an encoded string (again, due to limitations in the API) so the format for the parameters is a bit rigid and a title and description are required. I will look into it to be sure it is actually working as intended.

Markulyas

Thank you for the detailed reply.

Let's forget about automatically updating the location. Currently we open Terrain Map by clicking on its icon. Is it not possible to bind /loc command to that click, and update the location while opening the map at the same time?

Garan

Unfortunately, the answer is no. Automatically showing the plugin every time a /loc command is issued would break the functionality for most users. You see, there are many plugins that use the response to the /loc command to get player location info, so a /loc quickslot is a very common feature of many plugins. If TerrainMap and Moormap use that to trigger displaying the plugin, then not only would they be battling each other for which is displayed, they would be doing so every time a /loc command is issued, even if it wasn't for either one of them. Isolating the /loc that is generated by the plugin winds up not being trivial and also not reliable.

Ashleylin

Hello, this plugin looks absolutely amazing. Would there be any way to display my current quest objectives on the map?

Garan

Hi. Thanks for your comment. Unfortunately quest data is not exposed to Lua so there is no way to display it in plugins.

mcrain88

I was messing with this in game the other day. Is there a way to remove all the annotations on the map and then populate it with your own annotations? It seems I can only make one at a time, I make one and then try to make another and it just replaces the one I just made.

Garan

Hi. Thanks for your interest, sorry you are having an issue.

You can hide annotations by right clicking on the plugin which will pop-up a filter list. If you click 'Hide All' it will hide ALL annotations, including Custom POI (Point of Interest). You will then have to right click again and manually turn on Custom POI or they will not show. Note, unlike MoorMap, Terrainmap treats all custom annotations as POI and uses the same icon for all custom annotations.

EDIT:
I believe I know what has caused your issue. You most likely went into Options and turned off "Show Annotations". Doing this will prevent ALL annotations from showing and will disable the right click filter menu. It should also disable the "Add Annotation" menu option but I notice that it does not - this is a bug. I will fix that for the next version. If this is what you were doing, you will need to go back into Options and reselect "Show Annotations" and then use the right click menu to hide the types you want hidden - note, all the custom ones that you had previously made will suddenly reappear - they were there all along, just not being shown. You can remove unwanted custom annotations by left clicking on them, click Edit, then click Delete.

The reason for the Options->ShowAnnotations option is for users who's machines can not handle loading annotations dynamically. This option prevents the plugin from even attempting to access the annotation data files so the plugin will be more responsive when moving around the map. Sorry for the confusion.