Skip to content
TORNLIFE More

[ANSWERED] Userscript clarification

Started by Aevyn [4427995] on in Questions & Answers.

9 replies · 71 views · thread synced · yesterday · View on torn.com
About this thread

Posts archived: 10 / 10 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
10
Discussion span
→
People posting
4
Likes on archived posts
5
Authority score
60 / 100
Historical score
19 / 100
Story score
38 / 100
Engagement score
69 / 100

Most-liked replies

Aevyn [4427995]

So in the rules for tools and userscripts it says

“Such software must not make additional non-API requests to Torn”

But doesn’t quick items for both torntools and w3b companion script both send non-API post requests?

and if thats allowed any clarification on whats actually not allowed?

Kalends [2032147]

I am not sure what w3b does, but scripts can make non-additional non-api requests to torn that are triggered manually. ie if a non api request can be made by a normal button on that page, then you can create your own button to make it, and torntool's quick items is essentially a button thats equivalent to changing the item tab or using said item (2 clicks since 2 non-api requests) 

 

for something like this though, if done not perfectly it can be considered illegal / automated scripting, so you'd always want to send it to Velthir or IceBlueFire for review before publishing it. torntools, and I assume W3B, did get approval

fsh [2565962]

It's a bit of a weird one. Quick items (and other confirmation-skipping stuff) is allowed because it's you making the request, not the script/website.

 

Usually when you try to use an item, it brings up a confirmation; the "use" button is just cosmetic and only serves to bring up the confirmation, making no requests; only the "yes" on the confirmation sends anything to the server. Quick items are basically equivalent to moving that confirmation "yes" button to the top of your screen so it's always there.

 

This makes it okay so long as it's on the same page (so quick items are always on your item page, or on faction's armoury page; you can't e.g. have a "use medkit" button on someone's attack page) and so long as it's always one user input per request (so you clicking it once only uses one of the item, you can't have a "drink 48 beers" button).

 

Similar idea with quick-busting/bailing (only the "yes" on "are you sure you want to bust...?" is a request) and there're some for skipping the confirmation on item market purchases too.

fsh [2565962]

if they were to ban it they'd have to fed like half the playerbase, so don't worry about it :P

Kalends [2032147]

if you're just using torntools / W3b then you can rest easy, torntools is the most used thing in the game and is open source and made by people who ensure it follows rules, and staff have approved it as legal. W3B is made by a helper (junior member of staff). if you're making your own script, Velthir and IceBlueFire are the authority. 

Weav3r [1853324] Helper

As far as W3B goes, any automated requests it makes use your API key on an interval to update key data or power things such as trade updates while sitting on the trade page. None of these requests take any action for you on any page. 

 

Certain details are pulled from your own browser directly and there are certain bits that make non-API requests but it's only ever for a page that you are viewing, initiated by you, and only one request per click.