[X] My Assistant

Thanks for the reply, but.. could I get that in layman terms? Or rather, in setting?

Eh, I thought that you want to modify the script. They are architectural issues of HV Stat.

In settings, probably most time consuming function is 'Show monster info from database', especially when a lot of monsters appear.

a very little bug


and since the developer seems to be busy with more important bug, here is the fix

i'm sorry for anyone who feel offended by this.



1. ctrl+f then type cloth, the screen should looks like above
2. match the number in the _prof.armorproftotals bracket according my picture (my 2nd black box)
3. save (obvious)

it's done (IMG:[invalid] style_emoticons/default/smile.gif)

edit: thats the 5.4.5 version

This post has been edited by MirandaKerr: Nov 18 2012, 18:12

a very little bug

Interesting. Of note is that its not just cloth, its cloth and light that are wrong. (everything else is correct)

This post has been edited by mrttao: Nov 18 2012, 21:46

a very little bug


and since the developer seems to be busy with more important bug, here is the fix

i'm sorry for anyone who feel offended by this.



1. ctrl+f then type cloth, the screen should looks like above
2. match the number in the _prof.armorproftotals bracket according my picture (my 2nd black box)
3. save (obvious)

it's done (IMG:[invalid] style_emoticons/default/smile.gif)

edit: thats the 5.4.5 version

Thanks for reporting. I'll fix it at the next release.

(IMG:[invalid] style_emoticons/default/mellow.gif)
AVG just quarantined hvstat jquery-uimin.js in my pc

"Infection"
"Virus found Script/Generic"

False positive? (IMG:[invalid] style_emoticons/default/mellow.gif)

Never mind.
AVG's false positive (IMG:[invalid] style_emoticons/default/faint.gif)

tried with chrome (and iron) version 22 & 23, with 5.4.5.1, the leak is here again :/

tried with chrome (and iron) version 22 & 23, with 5.4.5.1, the leak is here again :/

My environment has no problem.
What happens by disabling all other extensions?

5.4.5.1 working great on iron23 with monster data disabled, faster than iron21 actually.

But my powerup UI is gone (I mean the little box in the corner that shows what powerup has dropped). Is that the UI delete that fixed the memory leak?

Edit: The round counter on the top right isn't there too.

I did use the fix posted by mirandakerr by extracting the crx then loading the unpacked plugin. That wouldn't have done me in would it?

Edit2: The options are there like you said. I guess I didn't think to check for new options XD

This post has been edited by loserneo: Nov 23 2012, 06:29

But my powerup UI is gone (I mean the little box in the corner that shows what powerup has dropped). Is that the UI delete that fixed the memory leak?

Edit: The round counter on the top right isn't there too.

Confirm options 'Show Round Counter' and 'Show Powerup Box' in Battle Enhancement section. Now their default values are off.

My environment has no problem.
What happens by disabling all other extensions?

Found the culprits : No popup & quickbar 2 (quickening)

Just wondering: why do so many features not support the HV Font Engine? Is it cost-prohibitive to convert the vertical background positions of each child div to a character and vice versa? When I switch to downloadable fonts all the text gets significantly larger and doesn't fit very well (e.g. 'Equipment Shop' on the Bazaar menu wraps and runs into Item Shop) and when I use a custom local font some elements shrink while other grow larger and either readability or layout suffer.

tried with chrome (and iron) version 22 & 23, with 5.4.5.1, the leak is here again :/

The leak is in v22+ of chrome and derivatives no in HVSTAT. Using a workaround script that minimizes its effects would still not fully eliminate it since its a problem in chrome itself.
I suggest you stick to v21 until google fixes the issue.

This post has been edited by mrttao: Nov 24 2012, 22:47

HVSTAT v5.4.6
Minor update version

Changes

• Added New option: Automatically advance the round when "You are Victorious"
  (Because GaryMcNabb's No "You are Victorious" Popup script is not compatible under Firefox, it has been integrated into the HV Stat.)

Bug fixes

• Fixed bug that health alerts don't work at the second and subsequent on a round
• Fixed bug that armor proficiencies are wrong on proficiency pop-up

Known issues

• Effect Expiring Warnings might not work under Firefox when holding down the hotkey '1' - '0'.

[github.com] Download Chrome Edition
[github.com] Download Firefox Edition

[github.com] Old Version Downloads
[github.com] Changelog History

Just wondering: why do so many features not support the HV Font Engine? Is it cost-prohibitive to convert the vertical background positions of each child div to a character and vice versa?

I don't know what past developers thought.
At least I have no motivation to implement it because it is very laborious.

When I switch to downloadable fonts all the text gets significantly larger and doesn't fit very well (e.g. 'Equipment Shop' on the Bazaar menu wraps and runs into Item Shop) and when I use a custom local font some elements shrink while other grow larger and either readability or layout suffer.

The issue is not directly related to HV Stat.
Try to ask here.

This post has been edited by greentea039: Nov 25 2012, 05:23

I don't know what past developers thought.
At least I have no motivation to implement it because it is very laborious.

I started writing a user script to parse stats before I found out about HV STAT and converting the font engine text to actual characters proved pretty simple. I didn't try doing it in reverse but I can't imagine it would be much harder. If you or any of the devs are interested I'd be glad to share the code.

The issue is not directly related to HV Stat.
Try to ask here.

Thanks, I'll inquire there.

Memory bug [code.google.com] http://code.google.com/p/chromium/issues/detail?id=113983
Has been fixed in v24 beta. I am sticking to v21 until it goes stable but if you can't wait you are welcome to try it.

i want to begin using monster stat function, so i have a few question
1. whats the difference between scan result and skill data?
2. where does the scan result stored? (cached web content or offline web content, firefox)
3. i guess i can edit the TSV version?
3. i only want to show monster with piercing attack, i guess it will only cause an unnoticeable delay in loading speed?

i want to begin using monster stat function, so i have a few question
1. whats the difference between scan result and skill data?
2. where does the scan result stored? (cached web content or offline web content, firefox)
3. i guess i can edit the TSV version?
3. i only want to show monster with piercing attack, i guess it will only cause an unnoticeable delay in loading speed?

1. When you scan a monster you get a list of info about it. It looks like

Scanning Need0213...
HP: 14524/14524 MP: 296/799 SP: 5/387
Monster Class: Giant, Power Level 866
Monster Trainer: need0213
Melee Attack: Crushing
Weak against: Piercing
Resistant to: Crushing, Fire, Cold
Impervious to: Nothing

Notice nowhere does it say what the monster's skill/spell/spirit attack are. You find those out when they actually use one of them on you. At which point it records that info to present to you more complete info about said monster.

2. Where-ever your browser stores [en.wikipedia.org] https://en.wikipedia.org/wiki/Indexed_Database_API data.
You can use the export/import functions though to get it to a file

3. Is that a question? What is TSV? This is an open source project so you may edit whatever you want.

4. There is no such option currently. Adding one will just make things slower though because the process would be:
step 1: Retrieve monster attack
step 2: Determine if piercing
Step 3: Display if piercing
(well, not exactly I was simplifying, it would be an if-else function for the display instead of just displaying).

This is more work then just retrieving it and displaying it so it will actually be slower.

This post has been edited by mrttao: Dec 2 2012, 23:57

Memory bug [code.google.com] http://code.google.com/p/chromium/issues/detail?id=113983
Has been fixed in v24 beta. I am sticking to v21 until it goes stable but if you can't wait you are welcome to try it.

From some of the new comment it sounds like while one memory leak was fixed, the issue specific to IndexedDB was not (which is what is causing the biggest problem with HVSTAT).