EQBuddy v1.99.1

What's new in 1.99.1

• FIXED (discussion #228, thanks joeymavity) - RESPAWN TIMERS NO LONGER COME BACK AFTER YOU CLEAR THEM. Clearing a timer with the X really did remove it - and then EQBuddy read your log again (on the next start, or when you switched character) and built the very same timer back out of the kill line it had just been told to forget. "Randomly" was the restart. Clearing now remembers WHICH kill you dismissed, and remembers it across restarts, so that kill stays gone. Killing the mob again still starts a fresh timer, because that is a real new spawn - and if you start one by hand with the play button, that always wins.
• THE RESPAWN TIMER NOW BELIEVES THE GAME WHEN IT SAYS A MOB IS RARE (discussion #185, thanks elderbit and bjstrange). Considering a rare mob prints "- a rare creature -" right in the line, and EQBuddy now reads it. Two things come out of that. First, a bug: that insert used to get swallowed into the mob's name, so considering the very named you were camping silently failed to count as a sighting. Second, the feature: named mobs whose names look like trash ("A ghoul executioner") could never be auto-discovered before, because the only signal was the no-article naming convention - now, if you've considered it this session and the game called it rare, your kill starts a discovered timer just like a proper-named mob. Same honest rules as all discovery: first kill shows "killed N ago", the second kill measures the cycle, and only your own kills count.
• FIXED - A NAMED MOB EQBUDDY DISCOVERS ON ITS OWN NO LONGER STARTS A COUNTDOWN INSIDE A RAID INSTANCE. Since 1.72.0 kills inside instanced raid zones start no timer (discussion #109) - but that rule only ever applied to mobs on the curated list. A named the list did not know, killed inside a raid instance, was auto-discovered and timed anyway, which is exactly the countdown #109 exists to prevent. Same fence, now on both doors.
• FIXED (discussion #226, thanks LeBigNasty and Frankthetankk, and #65 where it was first asked for) - THE DROPS TAB CAN RE-READ A CREATURE'S WIKI PAGE ON DEMAND, AND SAYS HOW OLD ITS LAST READ IS. The red marks that say "the wiki doesn't know this drop yet" were compared against a copy of the page EQBuddy keeps for seven days - so when you did the thing the mark asks for and corrected the wiki, the mark stayed lit for a week with nothing to say why. Every creature heading now shows when its page was read ("wiki read just now", "wiki read 5d ago") and has a small refresh button beside it that reads the page again right then. Two courtesies toward eqlwiki, which is run by volunteers: a page read in the last thirty seconds is not asked for again, and EQBuddy never has more than two wiki requests going at once - it used to fire one per creature the moment the tab opened. If the wiki cannot be reached, the old read stays on screen with its age, rather than the marks vanishing into "not checked". And the Wiki contribution pack window has a "Re-check N pages" button beside Copy that re-reads just the creatures it is about to claim something for - so you can fix the wiki, come back, and paste a pack that agrees with it.
• FIXED (discussion #109, thanks Frankthetankk) - PLANE OF SKY'S CHAINED AND TRIGGERED SPAWNS NO LONGER GET COUNTDOWNS OR "DUE". The bee chain (Bzzzt, Bazzt Zzzt) and the Spirocs (Guardian, Lord) do not respawn on a clock - each appears when the previous one dies, or when a particular spiroc is killed - and eqlwiki already says so, as "Respawn Time: Triggered" on their pages. EQBuddy was not only counting them down from the zone's 8-hour default; worse, it was LEARNING a respawn from the gap between two kills on Bee Island and saving it, so two Bzzzt three minutes apart became a three-minute timer that went DUE forever after. The catalog now carries the wiki's own word for these four, the Spawns window's row reads "triggered" and names what brings the mob, nothing is learned from their kills, any wrongly learned value already in your file heals itself on the next kill, and a shared zone archive can never put one back. Your own typed respawn time still wins, as it always has. Frankthetankk proposed exactly this distinction, and the wiki turned out to have it already. And from his log: a personal Plane of Sky instance enters with a line identical to the open world's, so EQBuddy now reads the "creating instance" line that comes one step before it - inside a personal Sky instance, no named starts a countdown at all, the same rule the other raid instances have had since 1.72.0.
• EQBuddy is a BETA - if something reads wrong, tell us: (gear) - Help - Send feedback.