I need to fill an input field. As i understand, simulation of a key press is not violating any rules, am i right?
Simulate a key press
Started by kermon [2493903] on in Tools & Userscripts.
About this thread
Posts archived: 12 / 12 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Counted by TornLife from the archived posts.
- Archived posts
- 12
- Discussion span
- →
- People posting
- 8
- Likes on archived posts
- 2
- Posts by staff, officers and moderators
- 2
- Authority score
- 56 / 100
- Historical score
- 18 / 100
- Story score
- 31 / 100
- Engagement score
- 56 / 100
Most-liked replies
- DeKleineKobini [2114440] Committee
· 1 likes ·
It's hard to tell, the rules suck in explaining anything. Simulating a button click is forbidden for sure, even if only client sided.
Mentioned in this thread
MikePence [2029670] ×1
Don't simulate a key press, I'm not sure if that's against the rules but it's not efficient
Just modify the value of the field directly lol
Just modify the value of the field directly lol
Im pretty sure it´s illegal
i`m pretty sure it is not.
i have tried a lot of things, value is changing, but in the end it does not work as it should
i want to change poker bet input field, MikePence maybe u could help me? :
i have tried a lot of things, value is changing, but in the end it does not work as it should
i want to change poker bet input field, MikePence maybe u could help me? :
Mentions: MikePence [2029670]
and now i have red
Note: Manually firing an event does not generate the default action associated with that event. For example, manually firing a key event does not cause that letter to appear in a focused text input. In the case of UI events, this is important for security reasons, as it prevents scripts from simulating user actions that interact with the browser itself.even keypress will not help
It's hard to tell, the rules suck in explaining anything. Simulating a button click is forbidden for sure, even if only client sided.
What exactly are you trying to do? It might be possible and you're just going about it wrong
Just copy however DocTorn does the 'max' input filling and you should be fine.
[image: i.imgur.com]
Raise will be the same 2K, until i manually type numbers in the text field
Raise will be the same 2K, until i manually type numbers in the text field
Just throwing my two cents in about rules:
I take this to mean if you interact with your own script such as clicking a button that you have generated in your user script, that counts as a 'manual trigger' and can replace another action such as entering text in a field or clicking another button, or in your case setting the money in the betting field.
If the software you're using makes non-API requests that are not manually triggered by you, it is not allowed and can be tracked.
I take this to mean if you interact with your own script such as clicking a button that you have generated in your user script, that counts as a 'manual trigger' and can replace another action such as entering text in a field or clicking another button, or in your case setting the money in the betting field.
The way i am interpreting that rule is: Anything non-manually-triggered that causes an HTTP request to be launched (clicking on a button, anything that would trigger an ajax call, etc.) is forbidden. That is how auto-clicking on a yes confirmation link, on an egg, etc. actually breaks that rule.
Inputting a value in a field shouldn't be breaking that, as long as NO HTTP request to Torn is triggered as a result of that action.
Kind of reinforcing what cryosis7 said above, if you are adding your own buttons and stuff, and then clicking them (manually or automatically), as long as an that does not trigger an HTTP request to torn then it should be fine IMO (my own interpretation of the rule).
Jamop, maybe things are not working for you because of some validation on that field? It happened to me on the company inventory refill input fields, i had to enter a value and then call blur on the input field for it to be "validated" by the form on that page and being able to use things properly.
Inputting a value in a field shouldn't be breaking that, as long as NO HTTP request to Torn is triggered as a result of that action.
Kind of reinforcing what cryosis7 said above, if you are adding your own buttons and stuff, and then clicking them (manually or automatically), as long as an that does not trigger an HTTP request to torn then it should be fine IMO (my own interpretation of the rule).
Jamop, maybe things are not working for you because of some validation on that field? It happened to me on the company inventory refill input fields, i had to enter a value and then call blur on the input field for it to be "validated" by the form on that page and being able to use things properly.
agree with Goltred about meaning of the rules. we can click anything until it makes server-side activity
unfortunately focus()->blur(), select()->blur() didnt help
unfortunately focus()->blur(), select()->blur() didnt help