[X] My Assistant

On the current implementation of HVSTAT, MID is used as an index of the array of the monster database. Thus, if a monster which has big MID appears, too much space is consumed. I have recognized this as a problem, and currently working on a solution.

What about IndexedDB, wouldn't that work.. or is that not implemented in chrome yet.. or does it have the same size restrictions.

If it does work, it might even be faster, since you wouldn't have to load all the monster data, but just the ones that are relevant.

What about IndexedDB, wouldn't that work.. or is that not implemented in chrome yet.. or does it have the same size restrictions.

If it does work, it might even be faster, since you wouldn't have to load all the monster data, but just the ones that are relevant.

Chrome supports IndexedDB and WebSQL (Indexed being the better choice).
Chrome is easy enough to fix though, it just needs permission for unlimited storage:

CODE

"permissions": [
    "unlimitedStorage",
]

This would allow unlimited storage for IndexedDB, WebSQL, localStorage, sessionStorage and webkitFileSystem.
It doesn't solve the issue in Firefox though. TBH, I feel the monster data system needs rewriting rather than patching.

Chrome supports IndexedDB and WebSQL (Indexed being the better choice).
Chrome is easy enough to fix though, it just needs permission for unlimited storage:

CODE

"permissions": [
    "unlimitedStorage",
]

This would allow unlimited storage for IndexedDB, WebSQL, localStorage, sessionStorage and webkitFileSystem.
It doesn't solve the issue in Firefox though. TBH, I feel the monster data system needs rewriting rather than patching.

I don't think unlimitedStorage applies to localStorage [developer.chrome.com] http://developer.chrome.com/extensions/manifest.html .. says "applies only to Web SQL Database and application cache"

I don't think unlimitedStorage applies to localStorage [developer.chrome.com] http://developer.chrome.com/extensions/manifest.html .. says "applies only to Web SQL Database and application cache"

Odd, I'm sure I read that somewhere.
From what I've read, it appears localStorage and sessionStorage are the only two that never get unlimited storage (limit of 5MB).

I wish Google would timestamp their docs, it's a pain trying to figure out if their information is outdated.

EDIT: I'll need to run tests.

This post has been edited by GaryMcNabb: Aug 12 2012, 00:40

Yeah that was my bad.
Renamed to HVS_FIREFOX_5.4.1.9.user.js.
You should also be able to install it without installing anything else first.
Apparently Greasemonkey wasn't happy when I shrunk the code.

Okay. Installed 5.4.1.9 on top of nothing. (IMG:[invalid] style_emoticons/default/smile.gif)

A question... is it possible to enable only the "Proficiency Gain Summary"?

If not, in the next version could you make it possible? (IMG:[invalid] style_emoticons/default/biggrin.gif)

I'm using FF with chrome style, when i drag .js file on browser instead of instal the script on GM i open the script... any issue?

Thanks.

Is the extension still .user.js?
The .user is important.

Yes, the one inside the folderyou download, I also try to renameit but still nothing...

Yes, the one inside the folderyou download, I also try to renameit but still nothing...

Download it using this link
(IMG:[i1213.photobucket.com] http://i1213.photobucket.com/albums/cc476/ragnaware/step1.jpg)

Then click and drag the file into a Firefox window.
It should work.

A question... is it possible to enable only the "Proficiency Gain Summary"?

Currently, no.

If not, in the next version could you make it possible? (IMG:[invalid] style_emoticons/default/biggrin.gif)

Perhaps if someone else is free. I'm working to fix another serious bug.

The gem can't be used by clicking manually (above the spell cast bar), also the "+" button doesn't select the highest skill available (for DW). It will be great if these two are fixed. Cheer.

The gem can't be used by clicking manually (above the spell cast bar), also the "+" button doesn't select the highest skill available (for DW). It will be great if these two are fixed. Cheer.

Which version and browser are you using.

Using 5.4.1.9, I had increased dom.storage.default_quota to 1048576, so that shouldn't be the issue. 5.4.1.9 gave me nothing, so I downgraded to 5.4.1.4 [DEBUG4], which gives [pastebin.com] http://pastebin.com/erGc1TQD at least upon scanning. I changed over mid-round, so I don't know the MIDs. Perhaps a debug for 5.4.1.9 would be nice, but if 5.4.1.4 has the same issue it may be unnecessary for now. This seems to be a very intermittent problem, assuming it's just one problem (it has happened before with 5.4.1.9, again assuming so), but it's not one that necessarily fixes itself within the round, which makes it irritating nonetheless.

This post has been edited by oohay: Aug 15 2012, 10:19

Coloring when the character is damaged is different between 5.4.1.4 and 5.4.1.9.
Is this intentional? I think maybe a bug.

5.4.1.4


5.4.1.9

Which version and browser are you using.

5.4.1.9, chrome.

Coloring when the character is damaged is different between 5.4.1.4 and 5.4.1.9.
Is this intentional? I think maybe a bug.

That was a bug. It was fixed when I rewrote the battlelog highlighting function.

5.4.1.9, chrome.

I can't replicate the bug, it might be something else conflicting with it.
Try turning off other extensions or mods and see if it works.

Using 5.4.1.9, I had increased dom.storage.default_quota to 1048576, so that shouldn't be the issue. 5.4.1.9 gave me nothing, so I downgraded to 5.4.1.4 [DEBUG4], which gives [pastebin.com] http://pastebin.com/erGc1TQD at least upon scanning. I changed over mid-round, so I don't know the MIDs. Perhaps a debug for 5.4.1.9 would be nice, but if 5.4.1.4 has the same issue it may be unnecessary for now. This seems to be a very intermittent problem, assuming it's just one problem (it has happened before with 5.4.1.9, again assuming so), but it's not one that necessarily fixes itself within the round, which makes it irritating nonetheless.

greentea039's working on that.

That was a bug. It was fixed when I rewrote the battlelog highlighting function.
I can't replicate the bug, it might be something else conflicting with it.
Try turning off other extensions or mods and see if it works.
greentea039's working on that.

It conflicts with the keybind. I wonder if they can work at the same time...

It conflicts with the keybind. I wonder if they can work at the same time...

Fixed the powerup issue for next release.
I'll try fixing Dual Wield at some point when I have time.

greentea039's working on that.

Okay. I'm actually unable to imbue him again, although I just imbued you. Are there at least six people working on this, and, if so, who are they? It would be nice to have more ability to imbue HV Statters. ;p

How to disable "pick up a gem" pop-up?

How to disable "pick up a gem" pop-up?

Turn off 'Alert on Powerup drops'.