Entries by Slarti

I've upgraded the MobMap backend server last week, to ensure that there are more than enough resources for all that database processing work and stuff. However, the new setup did some...strange things...I still don't understand the problem in-depth, as I unfortunately cannot replicate it on my testing machines, but for some unknown reason the server decided to compress some responses to the MobMapUpdater on-the-fly which is something he should never have done. This most probably caused error messages for some people (I'd guess that ~1% of the user base was affected) while using the updater. I hope to have it fixed now (hard to tell if you haven't been able to identify the true source of the problem, but the logs indicate a successful fix as far as I can see), and I'm sorry for the inconvenience.

So there's a tiny new release which fixes two bugs. One is the infamous boss loot table bug: Boss loot tables in MobMap are now fully functional again and more complete than ever! Please note that even though MobMap 3.32 and MobMap 3.33 share the same database format version, you'll still have to update your database in order to profit from this bugfix as there were client- as well as server-side fixes involved.

And the second bug is the no-more-less-infamous "quest-tracker-not-updating-till-its-manually-closed-and-opened"-bug! Sorry for this one, I wasn't able to recreate this for a long time even though I tried pretty hard, finally attributing it to strange interference from other addons I don't know about in some weird combination. But then somebody in a comment here hinted me at the fact that log refresh did indeed work as long as the data collection was left active and stopped working after deactivating it. Thanks to you :) that finally got me on track again to find and eliminate this bug eventually.


3.33 is already online via the MobMapUpdater, manual update packages and a new installer package will follow soon.

...well, I hope so.

I'm currently working on a fix for this issue. Unfortunately I have to rework a whole subsystem which was some kind of dirty hack until now to get this fixed, so I cannot provide an estimate on when I will be done but...I can promise you that a fix is on its way.

Lately several users experienced crashes when trying to upload their collected data to the MobMap server. The source of this problem has been fixed, too :o) Uploads should work fine now.

Another MobMap version - another bunch of bugs (hopefully) fixed!

I highly suggest updating your database copy too when updating to MobMap 3.32! During the last days there were some erroneous databases online for brief periods of time, and if you got one of those errors can appear even with the newest MobMap version! The most current database is now bug-free as far as I know, so please update to it before you report a bug.

Changelog v3.32:
- fixed: The configuration checkbox "automatically show quest comments" does now store its setting correctly instead of enabling the functionality when the checkbox is being disabled and the other way round
- fixed: A compatibility issue with Cartographer which prevented players from opening dropdown menus in instances if both MobMap and Cartographer were enabled
- fixed: Several misbehaviors when searching for quest targets in both the MobMap and the Blizzard quest tracker
- fixed: A stack overflow bug that could cause the WoW client to freeze when displaying the positions of mobs in the Dalaran sewers

Unfortunately the bugfixing phase isn't over yet as it seems. I have just tracked down and fixed another bug that was causing Lua error messages in MobMap_itemdropdata.lua and/or problems when using the quest tracker and wrong search results on quest target searches. Fortunately though, this bug was entirely server-side, so there's no need for a new MobMap release, you just have to fetch a new database to get the fix.

There's a little caveat though: I had to temporarily deactivate the boss loot tables as they are the source of the problem. But since those were horribly wrong and mostly empty anyway and require a "big fix" (which they will get as soon as I can spare the time) that was only a minor loss.

**sincerely hopes that this bugfix will now finally get the post-3.1-MobMap into a reasonably stable state**

When fixing one of the Patch 3.1 problems last night, I seem to have overseen a side-effect of one of my changes that rendered a lot of the position data in MobMap useless: The positions just didn't display in the game, because they weren't included in the database.

The problem has been fixed now, correct and working databases are online. If you have gotten a MobMap update in the last 8 hours, I suggest you to fetch a new database copy, as you probably got a bad one during that timeframe. I'm very sorry for this inconvenience :( but I hope I've at least got most of the big Patch 3.1 problems fixed now.

Oookay, it was a long night (peeking out of the window lets me observe the first daylight right now...), but I think I was able to squish the most problematic bugs, or: the bugs which I have seen a lot in the reports and which I was able to replicate instantly. Unfortunately I had to alter the database format once again, so you'll have to get a new database, too, when downloading v3.31. But to compensate for that I've also added a tiny little feature: recipes are now linkable into chat :)

And then there's one problem that will still remain for about 24-48 hours (just a rough estimate): The malfunctioning new "Guide" feature was malfunctioning due to a very complicated Patch 3.1 side effects problem in my backend database which has partly corrupted some data. That caused most of the guide entries not to be generated which then in turn causes the guide to show all sorts of wacky stuff, like flightmasters which are 20.000 yards away. Fortunately, now that I have found and fixed the problem, the guide will literally "fix" itself pretty soon :o) though it'll take that little time span until most of the corruptions have been corrected by the ongoing data parsing process. So the bottom line is: if you'd like to use the new guide, I suggest you to update your database in about a day or two. Please note though that these problems mainly affect the guide feature, stuff like quest target searching or recipes are working fine.

Update: oops, forgot to switch the manual download versions from 3.30 to 3.31 last night...now 3.31 is up for download.

Update 2: GODDAMMIT! Seems as if one of my fixes last night has caused the position data in newly built databases not to be included correctly, so many mobs and stuff don't show any positions in MobMap at the moment. I definitely shouldn't roll out new releases when I'm tired :( The source of this problem has already been fixed, correct database builds are on their way...

Changelog for v3.31:
-------------------------------
- changed: DATABASE FORMAT CHANGE! You will need to get an updated database copy!
- fixed: A bug in the database routines which caused MobMap to either show wrong quest targets or throw an error in MobMap_itemdropdata.lua for certain quest target searches and which displayed the wrong mob names in the drop database
- fixed: Another bug that caused the wrong recipe reagents to be displayed
- added: Shift-clicking a recipe line in the recipe database will now link it into chat!

I have received and confirmed a bug in the current MobMap database creation routine that seems to create two errors: one is strange search results when searching for certain quest targets, another is a plain error message in WoW. The reason for this bug is still to be researched, but I will get to it as soon as possible. The same goes for the other bugs that have been reported, I'll see what I can reproduce and try to fix them.

I have seen several reports now concerning a refresh problem with the MobMap quest tracker. The problem consists of the tracker not updating automatically whenever a quest target status changes. It is of course intended to update automatically and does so on any test systems I could get my hands on. Therefore I need more information about this bug:

- What addons do you have loaded besides MobMap?
- Is the log updating correctly when you accept a new quest?
- Does the problem persist even if you temporarily deactivate all addons besides MobMap?

If you suffer from this bug I'd be happy if you could drop a message in the comments :)