French, Male, 23yo – Computer Science Student
I'm Upsilon, a scripter from France. I work mostly around Torn to create useful tools and automation. My journey started thanks to my spouse, LatexDove [3243958], who got me into scripting – initially for our own use with tools like TornBuddy. From there, my spouse and I started sharing and lightly commercializing scripts when the opportunity came. I'm not trying to turn scripting into a factory job, but I always welcome exciting or rewarding projects.
Outside of scripting for Torn, I occasionally develop on Salesforce, AWS and other enterprise stuff — just enough to keep my professional side fed while my Torn-side stays happy and mostly simple.
Streamline messaging, trading, and item sending in Torn. Add favorites and interact quickly without typing names every time.
Track multiple time zones with custom labels. Perfect for coordinating wars and planning with teams across the globe.
Revive smarter and faster. Set a threshold so you only revive targets above a certain success chance.
Free – Built for my spouse.
Between $80M and $120M – Monitors cache price trends over time.
$20M–$30M – Displays timers efficiently on mobile devices.
Around $30M - Show a the training you've done today at well at the history over the last week.
Other custom/private scripts are not shown here out of respect for client privacy. I value confidentiality more than reputation.
If you're interested in working with me, please reach out to my spouse LatexDove [3243958]. She will act as the first point of contact, collecting the relevant information and sharing it with me for review.
Each request is assessed on a case-by-case basis, taking into account the scope, complexity, and expected impact of the project. Pricing is determined based on a combination of development time, technical requirements, and the value the solution may provide.
Projects with substantial commercial potential may be priced accordingly, while smaller utility-focused tools may come at a lower cost. This approach ensures fair and contextual pricing aligned with the nature of each request. It's the difference between profit and not profit :)
This refers to the duration a piece of data or a cache entry is considered valid before it expires and needs refreshing. Managing TTL properly ensures your data stays up-to-date without excessive requests.
These are unique identifiers used to authenticate requests to torn service. Handling API keys securely is crucial to prevent unauthorized access or service interruptions. Common issues include key revocation, and managing the rate limits imposed by the API.
For example, Torn's API allows a maximum of 100 requests per minute per API key. Exceeding this limit results in temporary blocks, which can interrupt script operations and require careful request management.
Scripts must anticipate and gracefully manage unexpected errors to avoid crashes or data corruption. This includes retry mechanisms, logging, and user notifications.
The user interface of Torn can sometimes be tricky to work with. Modifying the UI to add or improve features often requires intricate adjustments that take a surprising amount of time — and, to be honest, I absolutely hate doing this part! But it’s necessary to ensure a smooth and usable experience for users.
I am currently looking to purchase public API keys for Torn. I offer $500k per key, per person.
This offer applies exclusively to public API keys to support my scripting projects efficiently.
If you are interested, please contact me directly to discuss further details.