With a great addition on the log view i'm hoping that it will become accessible via api soon? I know this has been put on the roadmap by the dev's but just want to "up" the request ;)
Because I foresee some serious page scraping if not added to the api, this has also been discussed before, i know.
Why don't the dev's change the API system to Websockets, polling stale data is so 90's...
This (ok I admit this is a big change) would free up a ton of resources on the torn side and that is something that would benefit us all.
Like for example the attack endpoint, we keep polling a 100 item array to see if anything changes, with websockets it would dramatically reduce calls to the servers and database query's.
If the WS middelware is added to the DB middleware you would cut out API DB query's.
On the bot makers side we would authenticate via API key and subscribe to certain channels we want, when the backend does a DB update it would send out a message to the channel linked to that.
It's a system that would greatly benefit the Torn servers, but also make bot's event driven and not history driven.
Really stale stuff like the Torn endpoints could just be send on "welcome" when subscribed to the WS channel. If missed events on a bot side problem would be an issue the "welcome" message for dynamic channels could also send X past results.
Hope dev's read this and give it a thought, because I can imagine the extra resources freed by such a change would come in handy during Torn events ;)
There seems to be a limit on "logtypes" (10) and i can't seem to poll more than 1 "logcategories".
Do log calls also count for our 100k daily limit (if so the category/type cap is a real issue) or is that on a different counter that caps on 100k lines fetched?
The banner showing the max amount that can be bought is not correct for plushies when you got the company perk (Toy Store). I know that it only counts for plushies, but this way I tend to forget that I can buy 32 plushies :(
There seems to be a limit on "logtypes" (10) and i can't seem to poll more than 1 "logcategories".
Do log calls also count for our 100k daily limit (if so the category/type cap is a real issue) or is that on a different counter that caps on 100k lines fetched?
A API key reset would be a big inconvenience for factions running a tool and discord bots and even players with various tools, scripts, websites.
As stated, there is not a lot of extra data compared to the API system as is, just waaaay more detailed, gonna yield some cool stats ;)
On the other hand most people don't really grasp what info they share when they add their API key to a tool or bot or whatever. A reset with a message and a checkbox is not gonna magically change that, any tool would just state "enable that checkbox" and most people will without fully grasping what they are sharing.
The banner showing the max amount that can be bought is not correct for plushies when you got the company perk (Toy Store). I know that it only counts for plushies, but this way I tend to forget that I can buy 32 plushies :(
With a great addition on the log view i'm hoping that it will become accessible via api soon? I know this has been put on the roadmap by the dev's but just want to "up" the request ;)
Because I foresee some serious page scraping if not added to the api, this has also been discussed before, i know.
Yeah maybe not replacing completely, but if you just use it for occasional historic data (even though that could also be done with WS) it would still mean a huge shift in resources.
Why don't the dev's change the API system to Websockets, polling stale data is so 90's...
This (ok I admit this is a big change) would free up a ton of resources on the torn side and that is something that would benefit us all.
Like for example the attack endpoint, we keep polling a 100 item array to see if anything changes, with websockets it would dramatically reduce calls to the servers and database query's.
If the WS middelware is added to the DB middleware you would cut out API DB query's.
On the bot makers side we would authenticate via API key and subscribe to certain channels we want, when the backend does a DB update it would send out a message to the channel linked to that.
It's a system that would greatly benefit the Torn servers, but also make bot's event driven and not history driven.
Really stale stuff like the Torn endpoints could just be send on "welcome" when subscribed to the WS channel. If missed events on a bot side problem would be an issue the "welcome" message for dynamic channels could also send X past results.
Hope dev's read this and give it a thought, because I can imagine the extra resources freed by such a change would come in handy during Torn events ;)
I've got a feature request for the API. I know automation's are not allowed (as a coder I fully understand why!) and the API is read only, but hear me out...
A lot of factions have a discord bot that handles fun stuff like lotto's and giveaways. It would be cool to have a faction API key that would allow a few simple automation's:
Allow members to send an item to a special faction "game" vault so the discord bot can start a giveaway or lotto
Let the discord bot send the won item to the winner via the faction "game" vault
Extra: let a discord bot handle vault transactions under very strict conditions
Leslie, Duke and Jimmy die in a car accident on Christmas Eve. They all find themselves at the Pearly Gates waiting to enter heaven. On entering they must present something relating to or associated with Christmas. Leslie searches his pocket, and finds some mistletoe, so he is allowed in. Duke presents a cracker, so he is also allowed in. Jimmy pulls out a pair of stockings. Confused at this last gesture, St Peter asks, 'How do these represent Christmas?' Answer: 'They're Carol's.'
![[image: i.imgur.com]](https://i.imgur.com/QWgAfU0.png){kind=link}
![[image: i.imgur.com]](https://i.imgur.com/doPMU8p.jpg){kind=link}