This newer version of the mapper is working as intended. I have deleted the old mapper triggers/scripts/aliases, and promoted what were labeled as TEST ones to actual. These are now the default ones I will mess with/fix/inform you about if askedAdael wrote:I spent a bit of time the last couple days working on something for the mapper that I've wanted to do for awhile, but hadn't gotten around to yet.
For anyone who ends up using these, the variable "wotmudmapper.currentID" is no longer a number, but a list, that could be empty, of length 1, or longer. Use that as you will
As of now, this seems to work as intended. I'll probably rewrite some stuff and make it cleaner soon, but lmk if you think anything unintentional is happening.
I also added triggers/scripts/aliases for a tic timer. It appears to be working semi-decently, I don't typically use one myself but others do I know and would like one. It needs to fire off of a trigger once to calibrate and start, which could be (most) anything that normally designates a tic has happened (ie loss of fleelag, sunrise, sunset, etc. The list in the triggers may not be comprehensive however, and I will gladly add anything that might be missing).
Once it has something to kick-start it, the timer should send you a message ~7 seconds before every tic. It gradually updates the average tic length the longer you're logged on, so it may be a second or two off at the start.
You can toggle it on/off with "tictimer" (if you turn it back on, it will need something to calibrate the start of a tic with just like when you first log in), or if it appears to be off you can try to "resettictimer" to fix it (again needing a tic marker to recalibrate the start).