[X] My Assistant

It's probably overkill, but I think the Smart Monster Lab can use [isotope.metafizzy.co] Isotope to further enhance the interface (IMG:[invalid] style_emoticons/default/heh.gif)
You can filter things easily too with its API (IMG:[invalid] style_emoticons/default/happy.gif)

This Isotope looks very nice, whatever it is, but it is really over the top functionality xD

.
Reloader v1.3.1

Changelog
- Fixed a bug on chrome that doesn't let MouseMelee to keep hitting an enemy without moving the cursor.
- Should run fine on chrome.
- Did general script [www.diffchecker.com] cleanups.

Tested a bit yesterday.

I could not make it work correctly as a userscript/unpacked extension (tried both with an old iron and the newest chrome), window.Battle is undefined and status_icons[i].onmouseover.toString() is not correct (chrome apparently wants .attributes.onmouseover).

In Tampermonkey those errors go away but it sometimes stops attacking when switching monsters.

In Tampermonkey those errors go away but it sometimes stops attacking when switching monsters.

Maybe it stops attacking because your HP/MP/SP are low? There is a setting for this...

I did not test as plain script, using tampemonkey - no problem either for second day of testing.

This post has been edited by f4tal: Feb 23 2016, 12:54

Maybe it stops attacking because your HP/MP/SP are low? There is a setting for this...

I'm not dumb (IMG:[invalid] style_emoticons/default/dry.gif)
It restarts if I click on the monsters.

you can try change one line in getMonsterUnderCursor:

CODE

result = ((el.id.match('mkey') && (el.hasAttribute('onlick') || el.hasAttribute('onmouseover'))) ? el : false );

I'm not dumb dry.gif
It restarts if I click on the monsters.

Sorry-sorry, dont want to hurt you ^^

Because I have no such problem - just wildguesing =)

.
Reloader v1.3.1a

Changelog
- Fixed mousemelee stopping if cursor is over a dead monster when new content is loaded.
- Fixed a bug on chrome that doesn't let MouseMelee to keep hitting an enemy without moving the cursor.
- Should run fine on chrome.
- Did general script [www.diffchecker.com] cleanups.

Download
 reloader_1.3.1a.user.js.txt ( 21.99k ) Number of downloads: 188

Links
Old versions by Dan31:
Beta v1.3
Firefox only v1.2
vanilla v1.0.3

Thanks to Sapo84 for reporting the issue.

you can try change one line in getMonsterUnderCursor:

CODE

result = ((el.id.match('mkey') && (el.hasAttribute('onlick') || el.hasAttribute('onmouseover'))) ? el : false );

Thanks, but the fix I found is shorter (IMG:[invalid] style_emoticons/default/happy.gif)
[www.diffchecker.com] https://www.diffchecker.com/i9mgiuz1

——

I don't think this reloader can be made native-chrome-userjs compatible.
If I understand it right, you can't access `window` if you are running it with chrome's built-in userjs support (it's isolated from the page itself).
A lot of things are impossible to do with this restriction, and the script might as well end as something like vanilla reloader with no extra features.
Perhaps there's a way around this problem?

An alternative would be creating an extension and run the userscript as contentscript, but it'd be better to use Tampermonkey anyways if you're willing to do this, no? (IMG:[invalid] style_emoticons/default/huh.gif)

This post has been edited by FabulousCupcake: Feb 23 2016, 13:17

HV Dark Lite NoScript, version beta 1

The more I progress, the slimer it becomes (IMG:[invalid] style_emoticons/default/laugh.gif)

[attachmentid=80865][attachmentid=80866]

So yeah, this one's a speed enhanced version for battle maniacs. The code's been compressed to the maximum. It still has some nice features though:
- Inspired from Battle Compact 2.0; defeated monsters now disappear are hidden.
- The battle log has been removed
- The buffs/debuffs icons don't blink anymore
- Some pics have been hidden/erased to make it faster (mainly the logo and some parts of the hp/mp/sp/oc bars)
- The interface fixes that exist in HV Dark are still there (forge upgrades, etc...)

On the downside:
- There's almost zero userscript support, the only exception being Reloader's/HV Stat Slim's effect counter during battles.
- As its HV Dark Lite brother theme, it does look ugly for anything unrelated to battles...

Screenshot:


This post has been edited by boulay: Feb 23 2016, 21:43

HV Dark Lite NoScript, version beta 1

The more I progress, the slimer it becomes (IMG:[invalid] style_emoticons/default/laugh.gif)

[attachmentid=80860][attachmentid=80861]

So yeah, this one's a speed enhanced version for battle maniacs. The code's been compressed to the maximum. It still has some nice features though:
- Inspired from Battle Compact 2.0; defeated monsters now disappear from the screen. If you run mousemelee/hoverplay/reloader, you now just have to hover the first monster. The others will go up as you kill them.
- The battle log has been removed
- The buffs/debuffs icons don't blink anymore
- Some pics have been hidden/erased to make it faster (mainly the logo and some parts of the hp/mp/sp/oc bars)
- The interface fixes that exist in HV Dark are still there (forge upgrades, etc...)

On the downside:
- There's almost zero userscript support, the only exception being Reloader's/HV Stat Slim's effect counter during battles.
- As its HV Dark Lite brother theme, it does look ugly for anything unrelated to battles...

Screenshot:

Thats pretty extreme with the hp bar thing (IMG:[invalid] style_emoticons/default/blink.gif)
but I like it (IMG:[invalid] style_emoticons/default/biggrin.gif)

Will it really increase load speed? I mean those hp bars are static items.


** you cannot have "defeated monsters now disappear from the screen" **

This post has been edited by Void Domain: Feb 23 2016, 21:10

Thats pretty extreme with the hp bar thing (IMG:[invalid] style_emoticons/default/blink.gif)
but I like it (IMG:[invalid] style_emoticons/default/biggrin.gif)

Will it really increase load speed? I mean those hp bars are static items.

Dunno that, my internet isn't good enough to actually test it. But it should be faster, at least compared to the other themes, since there's less to display.

** you cannot have "defeated monsters now disappear from the screen" **

Why? Is it written somewhere?

This post has been edited by boulay: Feb 23 2016, 21:14

Dunno that, my internet isn't good enough to actually test it. But it should be faster, at least compared to the other themes, since there's less to display.
Why? Is it written somewhere?

https://ehwiki.org/wiki/scripts
Anything that has the function of picking a target automatically, regardless of the actual method.
Anything that interprets the page in any way to pick a target or action.

Yes, boulay it is true.
Tenboro said something like "...you can hide monsters, but you'd have to do it in a way that doesn't move the rest into position/any behavior that has the function of picking a target automatically, regardless of the actual method, is not allowed".
Same deal was with original mousemelee - it had a function to remove dead monster and rearrange enemies pattern, so the hovering on first monster and only on it - will in fact kill on monster in a row. Tenboro said it is "bot-like" and banned all mousemelees below 0.131 version.

It is not like "you made a bad theme, immediately remove it!", but "your theme has a potency to hurt game and occasionally being banned". Sorry to sad you =(

Why? Is it written somewhere?

This is bad thing - no, it is not written somewhere. We just have a few rules we should not a hit, but noone exactly know do some action/script really violate them. For example, look few posts up in this thread and look for request for "press button to forge equip to level 5" script. There is a discussion is it legal or not. We do not have a list of actions that hurts game, but we have a list of ideas that should not be provide with scripts. =(

And bytheway theme looks nice, but I am stick with Battle Compact 2.0 - it is really a NEAT thing, especially if log is off ^^

This post has been edited by f4tal: Feb 23 2016, 21:40

Thats pretty extreme with the hp bar thing (IMG:[invalid] style_emoticons/default/blink.gif)
but I like it (IMG:[invalid] style_emoticons/default/biggrin.gif)

Will it really increase load speed? I mean those hp bars are static items.
** you cannot have "defeated monsters now disappear from the screen" **

Dunno that, my internet isn't good enough to actually test it. But it should be faster, at least compared to the other themes, since there's less to display.
Why? Is it written somewhere?

https://ehwiki.org/wiki/scripts
Anything that has the function of picking a target automatically, regardless of the actual method.
Anything that interprets the page in any way to pick a target or action.

Regarding hiding monsters:
Historically that was a feature that had to be removed from the original mousemelee as it basically turned to script into a bot.
Instead of display:none, visibility:hidden should work better inside those rules, as it cuts out some of the rendering but does not move the monsters

// Edit: darn, too slow (IMG:[invalid] style_emoticons/default/biggrin.gif)


Regarding: removing HP-background
Didn't test the style, but may reduce rendering time a little (like little little little), the major advantage would probably be, when your connection lags and the cache decides to discard the file (sometime have to wait a couple seconds until all the images are loaded in those cases).
If you want to measure the effect of not having to render those things, you can use the dev console in chrome to do so. Go to "Timeline", press record, do 10 turns or so with the style and without it, then compare the render times (IMG:[invalid] style_emoticons/default/happy.gif))

This post has been edited by simrock87: Feb 23 2016, 21:40

https://ehwiki.org/wiki/scripts
Anything that has the function of picking a target automatically, regardless of the actual method.
Anything that interprets the page in any way to pick a target or action.

Yes, boulay it is true.
Tenboro said something like "...you can hide monsters, but you'd have to do it in a way that doesn't move the rest into position/any behavior that has the function of picking a target automatically, regardless of the actual method, is not allowed".
Same deal was with original mousemelee - it had a function to remove dead monster and rearrange enemies pattern, so the hovering on first monster and only on it - will in fact kill on monster in a row. Tenboro said it is "bot-like" and banned all mousemelees below 0.131 version.

It is not like "you made a bad theme, immediately remove it!", but "your theme has a potency to hurt game and occasionally being banned". Sorry to sad you =(

Mkay, no sweat. I'll replace the links asap.

edit: replaced, I settled for hidden, insted of erased. Better safe than sorry...

This post has been edited by boulay: Feb 23 2016, 21:44

// Edit: darn, too slow biggrin.gif

=P

Mkay, no sweat. I'll replace the links asap.

Will test it tomorrow ^^

Didn't test the style, but may reduce rendering time a little (like little little little),

I tested boulay's Battle Compact 2.0 few days ago - it is really do a speed boost. Not a gigantic one (like from 1t/s to 4t/s), but a still significant (like from 1t/s to 1,2t/s). So I believe - every feature-less will do a speed boost xD

edit: replaced, I settled for hidden, insted of erased. Better safe than sorry...

This is same method you used in Battle Compact 2.0?

This post has been edited by f4tal: Feb 23 2016, 21:47

Regarding hiding monsters:
Historically that was a feature that had to be removed from the original mousemelee as it basically turned to script into a bot.
Instead of display:none, visibility:hidden should work better inside those rules, as it cuts out some of the rendering but does not move the monsters

// Edit: darn, too slow (IMG:[invalid] style_emoticons/default/biggrin.gif)
Regarding: removing HP-background
Didn't test the style, but may reduce rendering time a little (like little little little), the major advantage would probably be, when your connection lags and the cache decides to discard the file (sometime have to wait a couple seconds until all the images are loaded in those cases).
If you want to measure the effect of not having to render those things, you can use the dev console in chrome to do so. Go to "Timeline", press record, do 10 turns or so with the style and without it, then compare the render times (IMG:[invalid] style_emoticons/default/happy.gif))

Yeah, I should have looked more into it. It did seem a bit too convenient when I only had to hover the first monster... (IMG:[invalid] style_emoticons/default/dry.gif)
For those bars, it may actually be good for me. I do have lag problems ^^

This is same method you used in Battle Compact 2.0?

No, in battle compact 2.0, the monsters are actually erased via 'display:none'. The big difference is that the other monster cells don't move when one disappears. Their positions are fixed. So you still have to move your mouse when you kill monsters.
Safe! (IMG:[invalid] style_emoticons/default/heh.gif)

This post has been edited by boulay: Feb 23 2016, 21:55

This is same method you used in Battle Compact 2.0?

My bad English - I mean something different, but nevermind - looked through the code and find answer by myself. Thanks for very fast support and fixing ^^

I have an odd request. I'm debugging my Tag Check script and I want to see if it performs as expected and successfully filters the "Down all the following tags:" section into the "Completed:" section, sorted correctly, once tags get successfully removed from the galleries in question. But I think most of the Vigilante regulars (including me) who vote in the Abuse thread have already downvoted the tags in TheGreyPanther's current big tag post - without any changes, I can't debug.

If you read this, could you vote down the tags in this post? (It's nearly the same as TheGreyPanther's post here)

Done, thanks

This post has been edited by Superlatanium: Feb 24 2016, 13:28

I have an odd request. I'm debugging my Tag Check script and I want to see if it performs as expected and successfully filters the "Down all the following tags:" section into the "Completed:" section, sorted correctly, once tags get successfully removed from the galleries in question. But I think most of the Vigilante regulars (including me) who vote in the Abuse thread have already downvoted the tags in TheGreyPanther's current big tag post - without any changes, I can't debug.

If you read this, could you vote down the tags in this post? (It's nearly the same as TheGreyPanther's post here)

Thanks

Done (IMG:[invalid] style_emoticons/default/happy.gif)
Nothing gets moved to the "Completed" section when I did a recheck though, they just get stricken-through