[X] My Assistant

2. Multi-shrine does multiple actions (clicking the continue button) on multiple page loads. It's allowed because it's pretty much harmless, as it doesn't hugely affect the economy or the server's bandwidth

That's still one-click per move, theoretically. It just helps to select the type of equips, and it's out of battle so you won't get anything more from that.

There's a time when a bug hits the ponies so you won't lose them when you shrine them. If you do the shrining automatically, you'll get all your materials stripped unless you can provide evidence that it's not intended.

The 2nd clause is very vague. What exactly is "using parsing the state of the game". Is "querySelector", or even accessing the document object considered "parsing"?

As for the first clause, harmless scripts like MultiShriner or SellAll, or even my planned script MoogleSpam automate multiple action. Heck, MoogleSpam might not be considered harmless because there's no hard-limit to the amount of mail you can send, and such script could drain a lot of server's bandwidth or destructive spamming (Having said that, I should just keep it private after all :/ )

The focus of the 2nd clause should be 'take any in-game action'. We already have scripts that check everything from HP/MP/SP to monsters' name, so accessing the object shouldn't be the problem.

IMO it's always better to have a way to stop your script, due to the incident stated above. Out-of-battle scripts should be fine but do note that shit happens to Tenboro's code. (IMG:[invalid] style_emoticons/default/tongue.gif)

This post has been edited by varst: Jan 21 2014, 16:12

However, it should be okay if
-> you bind the scan to a key so you don't need to click that multiple times
-> notify you when you have less than 50% HP (notify =/= take action)

Let's replace Cure with Flee. AutoFlee whenever I'm down by a certain amount should be bannable offence, right? even though such act won't benefit me in any way, except saving me a few MP/SP and a wounded pride.

Now let's replace scanning HP with a desired item in the bazaar, and cure with buying it. That's still a bannable offence, right? So the rule applies to outside of battle

Now let's replace your HP with your monster's stamina, and cure with feeding food. Monsterlab will keep feeding monsters until they reach 100%. By that rule, shouldn't Monster Lab be banned as well?

At the end of the day, we judge the legality of a script by how much potential damage it can cause to the community/server, not what it actually does.

what about clause "auto-selecting target for spell\attack (scan)" ?

At the end of the day, we judge the legality of a script by how much potential damage it can cause to the community/server, not what it actually does.

I disagree with it. The legality here should be separated from the profitability. It's of Tenboro's discretion to determine what's 'potential damage to the community/server', so you're always as risk of some shit happening. Like if Tenboro mistakenly wrote the code so monster's stamina won't cap at 100%.

If Tenboro do have some auto-ban script that works if you do anything to 'monsters that only exist in code'... (IMG:[invalid] style_emoticons/default/rolleyes.gif)
I'm not sure about this, but in case he really does, how much grinding time you'll have to tell him that you're just 'scanning for monsters'?

This post has been edited by varst: Jan 21 2014, 16:33

@original discussion about scan: There is already constantly-updated database of jenga201's . Use it, you'll need to scan less.

holy_demon: As a rule, the script rules are applied in battle only, unless you do something freaking stupid, like write a bot that f5's bazaar every 250 ms to buy any mag+ equipment.(Hello mpmpmpmpmp)

what about clause "auto-selecting target for spell\attack (scan)" ?

My bad.

That's still one-click per move, theoretically. It just helps to select the type of equips, and it's out of battle so you won't get anything more from that.

It's pretty much autoclicker. If I write a script that will keep clicking the same monster after my first click, I'm sure it would get me banned. (In case I'm wrong about that though, I would add that feature to spellspam, sounds awesome to me (IMG:[invalid] style_emoticons/default/tongue.gif) )

The focus of the 2nd clause should be 'take any in-game action'. We already have scripts that check everything from HP/MP/SP to monsters' name, so accessing the object shouldn't be the problem.

I don't think you understand my point. To make myself clear, let's use these 2 example script: one will decide which buffs to use just by pressing hotkey, that is obviously bannable, the 2nd script will click continue whenever the "you are victory" notice appears. The 2nd script take an in-game action (cancelling the popup), from parsing in-game information (the victory element). How is that still in HVStat. You can argue that it doesn't enhance combat in anyway, but that's exactly my argument for a ScanAll script

If Tenboro do have some auto-ban script that works if you do anything to 'monsters that only exist in code'... (IMG:[invalid] style_emoticons/default/rolleyes.gif)

Then anyone who uses MouseMelee or SpellSpam will get banned (IMG:[invalid] style_emoticons/default/tongue.gif)

This post has been edited by holy_demon: Jan 21 2014, 16:43

It's pretty much autoclicker. If I write a script that will keep clicking the same monster after my first click, I'm sure it would get me banned. (In case I'm wrong about that though, I would add that feature to spellspam, sounds awesome to me (IMG:[invalid] style_emoticons/default/tongue.gif) )

Well as I said, shit DID happen to multi-shrine. And you surely know the line here. (IMG:[invalid] style_emoticons/default/smile.gif)

I don't think you understand my point. To make myself clear, let's use these 2 example script: one will decide which buffs to use just by pressing hotkey, that is obviously bannable, the 2nd script will click continue whenever the "you are victory" notice appears. The 2nd script take an in-game action (cancelling the popup), from parsing in-game information (the victory element). How is that still in HVStat. You can argue that it doesn't enhance combat in anyway, but that's exactly my argument for a ScanAll script

The NoPopUp got the specific permission from Tenboro.

https://forums.e-hentai.org/index.php?s=&am...t&p=2084278

You should ask him if ScanAll script is okay.

Then anyone who uses MouseMelee or SpellSpam will get banned (IMG:[invalid] style_emoticons/default/tongue.gif)

Not sure, but I don't think those two would be affected by invisible monsters?

Main point here: when in doubt, ASK TENBORO.

This post has been edited by varst: Jan 21 2014, 16:55

Mousemelee has been used for months and has hundred of downloads, plus the code₁ has been seen₂ by Tenboro₃. I'm sure people would notice if it got them banned.

Of course, by then they're banned though. In any case, if you are not sure, PM the guy. The rules are determined so you don't have to ask everything, the final decision is still up to him. So rules-lawyer to make stuff that sodomizes the server and at the very least, your script will be taken down.

As for clicking the monster after the first click, have you looked into a numpad or mousemelee?

₁ Version 1.3 one, not most recent rewrite.
₂ Maybe.
₃ When taking it down due violation with css.

This post has been edited by Lement: Jan 21 2014, 17:02

You should ask him if ScanAll script is okay.

I agree with it.

Just ask Tenb!

Let the ponys decide it. (IMG:[invalid] style_emoticons/default/rolleyes.gif)

Disable\Enable button is pretty handy for mousemelee btw (IMG:[invalid] style_emoticons/default/happy.gif)

Improved it more after sending :3

Is a script that disables all flashing of player's/monsters' status effects possible?

Is a script that disables all flashing of player's/monsters' status effects possible?

It's possible, just have to change get all the elements with id "effect_expire", change them into something else.

Or you could just put this at the end of any battle script

CODE

new function() {
var nl = document.querySelectorAll("*[id*='effect_expire']");
for (i = 0; i < nl.length; i++) {
nl[i].id = nl[i].id.replace(/expire/,"expire_null"); //stop flashing
nl[i].style.opacity=1 //restore opacity
}
}();

This post has been edited by holy_demon: Jan 21 2014, 20:53

Is a script that disables all flashing of player's/monsters' status effects possible?

It's not only possible, it's done!

No Blinking for Firefox: Disable buff/debuff blinking when they are about to end.
 hvnb.user.zip ( 686bytes ) Number of downloads: 106


That was my first time fiddling with @run-at document-start, it was kinda interesting.

Edit: dubbed it "for Firefox".

This post has been edited by Dan31: Jan 22 2014, 17:42

Quoting Tenboro's words:
Theoretically scanning multiple monsters would go into the 'automates multiple actions' category. Something like 'cast cure when you have less than 50% HP' would violate the 'takes in-game actions based on parsing the state of the game'.

However, it should be okay if
-> you bind the scan to a key so you don't need to click that multiple times
-> notify you when you have less than 50% HP (notify =/= take action)

Scan mousemelee!

I appended your code to the MouseMelee script and it works. thanks. (IMG:[invalid] style_emoticons/default/happy.gif)

Doesn't seem to work for me. Do I have to edit the script before using? I do like the idea of having a seperate script for this function...

Scan mousemelee!

Scan is in a skill list. SpellSpam already supports it, just put scan on hover. It's not intelligent though, and it will keep scanning the same monster to eternity you mouse over, instead of moving to every monster on the list. :/

This post has been edited by holy_demon: Jan 22 2014, 05:14

I appended your code to the MouseMelee script and it works. thanks. (IMG:[invalid] style_emoticons/default/happy.gif)
Doesn't seem to work for me. Do I have to edit the script before using? I do like the idea of having a seperate script for this function...

DIY: Beginner's guide to making your first (HV) user script.


Step 1: Put this in the beginning of your script (Edit Script, Script Description, Script Version, and Script author to your liking)

// ==UserScript==
// @name Script name
// @namespace hentaiverse.org
// @description Script description
// @include http://hentaiverse.org/*
// @version Script version
// @author Script author
// ==/UserScript==

Step 2: Put in the content of the script (This should be the code I gave you)

Step 3: Save the script in a name like this: "Script name_Script version.user.js". The ".user.js" part is mandatory

Step 4: Run the script. Congrats, you've made your first userscript

This post has been edited by holy_demon: Jan 22 2014, 05:57

Step 5: Use either chromium-based browser or Scriptish/GreaseMonkey/ViolentMonkey extension to actually have the script in your browser.

Step 5: Use either chromium-based browser or Scriptish/GreaseMonkey/ViolentMonkey extension to actually have the script in your browser.

Blergh, I'm assuming that anyone who's viewing this thread at least knows how to use userscript

This post has been edited by holy_demon: Jan 22 2014, 05:57

Doesn't seem to work for me. Do I have to edit the script before using? I do like the idea of having a seperate script for this function...

The script is kinda simple, it runs before any script from the page executes and it overrides a function used in battles. The new function is exactly the same but with one less line, namely the one responsible for the blinking. If you can't make it work, it probably means that your browser don't support @run-at document-start. What browser/extension are you using?

It may also be because another script is messing with it. Try running it first before any script? I can see it happening the way I wrote the script (ie inserting the overriding function in an existing <script> block instead of creating a new one), so I will edit it accordingly later. My bad.

This post has been edited by Dan31: Jan 22 2014, 13:57