[X] My Assistant

Strange, some time ago there was a misterious fix for that, I asked if that wasn't illegal and I was told it wasn't.
(let me search for that and I'll link it with an edit)

I still have the doubt, and still have an older version of Reloader that doesn't allow that.

For example a fix like this would make the first arena doable by hovering 1 time and leaving the mouse on the same point for 5 rounds. It can be done only for that arena but still, it's not an input for the player for every action.

Dont want to break any rules thats for sure

...

It basically is an automatic first attack, so i'd say it's not allowed, like the auto cast on new round that was removed from CC.

This post has been edited by gianfrix94: Feb 11 2017, 23:52

Read on page 164.

Edit:

The only nagging issue I found is that you have to move your cursor/rehover the monster on round start.

Isn't that a required thing that disallows the script picking a target automatically?
I thought so (IMG:[invalid] style_emoticons/default/huh.gif)

No, it's the browser that doesn't get the monster under the cursor if you don't move it.
To bypass that you save the coordinates and use them to select the monster.
So stupid.

This post has been edited by End Of All Hope: Feb 11 2017, 23:58

Read on page 164.

I read that, and yeah the have to move mouse on new round came from browser changes, but this doesn't change the fact that it makes the script less automatic and more inside the rules in my opinion.

Read on page 164.

TLDR:
It's different browser behaviours. Firefox does automagically trigger the hover event after a new render while you have to actually move the pointer 1pixel on chromium browsers.
There is a 10 line or so snippet, that replicates the firefox behaviour for chromium browsers.

CC has it and uses it instead of binding hovers in case the pointer is above a monster (this is actually a speed optimization as well as fixing that annoying imbalance) and i think gianfrix reloader version has a setting for chrome_hover_fix or something like this. Not sure about Sapo's version, only checked the structure for his 1.4 version (IMG:[invalid] style_emoticons/default/happy.gif)

If this behaviour is illegal, you'd also have to ban either firefox or hover-scripts in general as every hover script would need to implement something specifically to hobble firefox.

// read "hover event" as "mouseover event"

This post has been edited by simrock87: Feb 12 2017, 00:04

I don't have such issue on firefox nor on chrome.
The reloader's mousemelee DOES NOT go on if I don't move a bit the mouse on new rounds.
And that's the correct behaviour. And it should not be changed.

My in battle scripts:
1) Reloader 1.3.3a
2) CracklingCast 1.0.3 (blank field in the new round thingy)
3) Stack Counter 1.0.2

This post has been edited by End Of All Hope: Feb 12 2017, 00:09

...

Didn't FF new versions stop the automagic hover? I think they did.

PS: The chrome fix in my reloader is inherited from reloader 1.3.3b, and is not for not having to move the mouse on new rounds but is for tracking the position of the cursor always.

This post has been edited by gianfrix94: Feb 12 2017, 00:12

Didn't FF new versions stop the automagic hover? I think they did.

Not sure, haven't used FF for about a year or so now.
Anyway, it has been okay until now, in the state as it was ironing out browser differences, and the usual stance so far has been to carry on so long until it's no longer okay. (that sentence sounds wrong ... nvm) As it was with the spell_on_new_round that came from HoverPlay.

If you'd like to check ... try with Reloader with everything beside the Reloader part turned off, write a 5 liner that attaches to Reloader_reloaded, then attaches a 'mouseover' event with console.log() output to every monster element, then enable keyboard-mouse (so that you don't accidently move the mouse while clicking), move the mouse over a monster and click with keyboard-mouse (NumPad 5). At least that would've been my approach to be sure.

PS: The chrome fix in my reloader is inherited from reloader 1.3.3b, and is not for not having to move the mouse on new rounds but is for tracking the position of the cursor always.

*cough* check if (settings.chromeFix) { and the following lines, it does exactly that (IMG:[invalid] style_emoticons/default/wink.gif) There is no other reason to track mouse movements in any battle script.
Also, yeah it's been in there for a while, even though Reloader, to my knowledge at least, doesn't work well with chrome (without tampermonkey).

even though Reloader, to my knowledge at least, doesn't work well with chrome (without tampermonkey).

Do scripts even work without an extension for scripts? I thought only very basic ones work without extensions.

This post has been edited by End Of All Hope: Feb 12 2017, 00:34

Do scripts even work without an extension for scripts? I thought only very basic ones work without extensions.

FF doesn't have basic UserScript support built in afaik, so FF still needs GreaseMonkey in any case.
Chrome has UserScript support, but HV scripts tend to need some interaction with the page itself, so you need to circumvent the sandboxing in these cases, which is generally not done for most scripts.
If you want to try, try Vanilla Reloader (v1.1.1 nerfthis fix) with CC. Vanilla Reloader(VR) takes care of the on-page stuff by injecting itself into the page and CC then abuses the controls VR put in place to circumvent its own sandboxing issues (IMG:[invalid] style_emoticons/default/smile.gif)

But, it's usually just about 20 lines of copy/paste for the injecting part to get FF-Only/GM scripts working in chrome. (check the first and last lines of VR)

PS: I switched from old Iron Portable to Chromium Portable as it got quite dated and Chrome does the stupid userscript deleting stuff (hint: Chromium != Chrome)

// Edit:
Reason you'd want to use scripts without TM is that TM also has some overhead that needs to run with each script, which in the days of Reloader is not that annoying anymore, but why carry a 2MB JS around if you don't need it?

This post has been edited by simrock87: Feb 12 2017, 00:43

I don't have problems with that fortunately.
I play on FF with Greasemonkey to use Reloader+CC+Stack Counter + some forum/non battle script.
And I have Tampermonkey to eventually use on Chrome too. It depends on how many tabs I have open on FF (IMG:[invalid] style_emoticons/default/laugh.gif)

*cough* check if (settings.chromeFix) { and the following lines, it does exactly that (IMG:[invalid] style_emoticons/default/wink.gif) There is no other reason to track mouse movements in any battle script.
Also, yeah it's been in there for a while, even though Reloader, to my knowledge at least, doesn't work well with chrome (without tampermonkey).

Isn't that for getting the cursor position from the last round and updating it whenever cursor moves?
I tried it without that, but without it on Chrome you need to move the cursor EVERY turn for it to work.
It's not for attacking on new round, but on new turn without moving cursor.

Do scripts even work without an extension for scripts? I thought only very basic ones work without extensions.

In Chrome they don't anymore, they blocked scripts from out of the store.
Or maybe you can do it in developer mode? I'm not sure, since i use Tampermokey.
You can directly install Userscripts in Chromium and Iron, i think.

Isn't that for getting the cursor position from the last round and updating it whenever cursor moves?
I tried it without that, but without it on Chrome you need to move the cursor EVERY turn for it to work.
It's not for attacking on new round, but on new turn without moving cursor.

Correct, in Chromium based browsers you have to move the mouse for ANY mouseover to trigger again from a "resting" position.
In FF you didn't have to for anything as turn and round behaved the same way before Reloader.

This post has been edited by simrock87: Feb 12 2017, 00:53

Didn't FF new versions stop the automagic hover? I think they did.

If I remember correctly 49 was the last version where the automagic hover on new round worked.
Still using that btw, playing with 50+ felt really crappy so I went back to 49 half an hour later.
I've yet to test 51.

i have firefox 47 and i never noted it.

double post



This post has been edited by RoadShoe: Feb 12 2017, 03:35

Does CC work for just 'attack'?

ie - can I set it to mousemelee monsters on their head with a staff?

I can't seem to make it work anymore.

I use reloader 1.3.5 for mage, but I can't make it work for whakamonster either.
If I change the line from 'Smite', 'Smite', 'Paradise Lost', etc. to just 'attack', it places me in click mode only.


And clicking through a 150 round arena??

...

For normal Attack on my Reloader (1.3.5d) you just need to leave the field blank( so hover: [] ).
I think i wrote that in the comments, maybe i was a bit unclear though.

This post has been edited by gianfrix94: Feb 12 2017, 03:37

For normal Attack on my Reloader (1.3.5d) you just need to leave the field blank( so hover: [] ).
I think i wrote that in the comments, maybe i was a bit unclear though.

wow! double posted again.

It doesn't like that gif. (IMG:[invalid] style_emoticons/default/laugh.gif)

This post has been edited by RoadShoe: Feb 12 2017, 03:42

For normal Attack on my Reloader (1.3.5d) you just need to leave the field blank( so hover: [] ).
I think i wrote that in the comments, maybe i was a bit unclear though.

That worked! Thank you sir.


I should have read the comments, but.....