Vanalytics May 2026 Update

[u/Soverance]

Just pushed a new update to Vana'lytics and the associated Windower addon. I'm particularly happy with the "hunt" feature of the addon (which will help you hunt NMs). Shoutout to HiPotion for ideas and code around some of the other checklist/tracking features.

https://vanalytics.soverance.com

• Renamed the "Relics" tab on the character detail page to "Ultimate Weapons"
• Fixed a handful of Ultimate Weapon categorization bugs
  • Notable gap: Prime weapons are not accounted for
• Added badges to Ultimate Weapons to indicate stage progression
  • Notable gap: Aeonic weapons do not have good stage progression indicators and may display incorrectly
• Added a "Porter" feature to the Inventory sections that allow you to see items you've stored with a Porter Moogle, and treat those items as a more natural part of your inventory.
• Added new "hunt" feature to the Windower addon, which is super useful for NM camping
  • Track and watch mobs via widescan
  • Robust realtime target information
  • Respawn timers with chat/audio notifications
  • Per-zone NM hunting list
• Various "progress" tracking enrichment tabs were added to the character detail page, including:
  • Current Limit Point  / Merit Point tracking
  • Historical Job Point spend
  • Historical Title obtained tracking
  • Travel markers completion
  • Nation Rank progress tracking
  • Expansion Mission progress tracking
  • Key Item tracking
  • Spell and Trust learnt completion tracking
  • Relic weapon / Dynamis currency progress tracking
• Optimized some of the backend database synchronization functions for improved query performance.

[u/MTDice]

This is really quite amazing! Thanks for putting this together! As someone who just realized the power of Porter Slips, it's nice to be able to see exactly what's stored at any given time.

Amazing work though!

EDIT: The NM Hunt feature is suddenly working for me today. No changes to what I did yesterday, but it's pretty neat. Will love to see where this continues to go!

[u/Soverance → u/MTDice]

Nah, you're not missing anything, thanks for checking it out. This is a backend API error with a misleading error message, queued for a fix.

Figuring out which monsters are NMs from actual game data is harder than it seems. If you just read the DAT files or look at zone spawn data, NMs aren't really any different than regular mobs, so there's no "easy" way to identify them from just looking at the data. It's not like there's a simple boolean flag like "IsNM" or something, and you can't really assume it's a NM just cause it has a special name or sits within some ID range of it's placeholders. So you have to cross-reference with something (a resource I'm not sure exists anywhere), or know which mobs are NMs in advance.

While less than ideal, I had such trouble with identifying NMs programmatically that I settled on basically keeping a manually curated list of NMs for every zone: Vanalytics/src/Vanalytics.Web/public/data/nms at main · Soverance/Vanalytics I scaffolded them using data from BG Wiki, but I didn't go deep diving on every NM, so many of these files are still incomplete (missing placeholder information or respawn timers, for example). Any NM that doesn't have valid curated data falls back to a heuristic that tries to figure out which mobs to track, and that's where you encounter this particular error (in this case, you're likely camping a NM that has a curated PH name but not a PH ID, so the hunt addon thinks it's supposed to track a PH but doesn't know which one to track, so it throws this error).

I'm working on a fix (that includes, at the very least, better error messaging). If you're git savvy, feel free to submit a PR that updates any of these files with accurate info... I'd greatly appreciate the help =)

Would be nice to know which NM you were trying to camp!

[u/MTDice → u/Soverance]

I edited my post just as you had replied, but this is amazing work and greatly appreciated!

For reference, I was using it on Okyupete. It's now letting me know that the NM is "currently dead" and timers all seem to be working. It knows that the placeholder is due. Pretty cool stuff!

[u/Soverance → u/MTDice]

Nice! glad it's working for you now. Let me know if you encounter any other issues.

Yeah if you check my curated file for Misareax Coast you'll see Okyupete has an identified placeholder mob (a Diatryma) that has a null index. BG Wiki for that NM claims the placeholder for that NM is "16879839: DF", or viewed in hex that's "0x0DF". So i need to add "0x0DF" as the placeholder ID to my curated file. Once that's in place, if you ran "//va hunt watch nm okyupete" in game it would track not only the NM spawn, but also it's PH spawn.

The heuristic fix I pushed this morning sounds like it's working, but it should only be tracking the NM for now. Needs that PH ID to get them both tracked with one command (otherwise you have to track both, which takes more effort for the player).

I'll go ahead and update Okyupete now - it'll be fixed properly in the next release. But yeah it's basically going through and doing that for every NM in every zone... which is time consuming and tedious lol