ChatGPT said:
If we're talking about TestPedroDev [3613560] on TORN, there's enough public forum material to do a much deeper analysis than simply "he's an admin who says no." I wouldn't treat "twat" as an objective fact about him, but I can absolutely unpack why his public communication can come across that way.
1. The fundamental problem: he's often technically reasonable while being socially irritating
A recurring feature of Pedro's posts is that he tends to answer the literal/technical question rather than the human complaint underneath it.
The clearest example is the January 2026 scraping dispute.
Players were using scripts that watched a chain timer and alerted them when the chain was getting low. The practical complaint was essentially:
"This has worked for years, why is this suddenly a problem, and why can't I have the game open while I'm doing something else?"
Pedro's answer was effectively: scraping is permitted only while the relevant page is actively being viewed, and if people want chain-watching functionality they should use the API. TTorn+1
That's a coherent rules answer.
But socially, it's frustrating because it doesn't really engage with the thing the player is pissed about: the distinction between "automating gameplay" and "having a browser tab make a noise when something happens."
And then he follows it with:
"I would like to draw your attention to our excellent API documentation"
That's exactly the sort of sentence that can make somebody want to throw a shoe at their monitor. TTorn
It's not necessarily hostile. It's just spectacularly corporate.
2. He has a particular talent for responding to complaints with a requirements-gathering exercise
Look at the recent forum-search discussion.
Players say, essentially, "the search is shit."
Pedro doesn't say:
"Yeah, we're aware it's shit."
Instead:
"Top things you'd improve on it? Use-cases for what you want to be able to achieve and can't, easily, at the moment?"
Then, when somebody gives examples, he asks what specific problem they're trying to solve and whether they're looking for a particular post. TTorn
From a software-development perspective, this is actually a perfectly sensible response. He's trying to turn:
"search sucks"
into:
"users need filters X, Y and Z because they perform tasks A and B."
That's useful product feedback.
But from the player's perspective, it can feel like:
"Thank you for your emotional complaint. Please convert it into a Jira ticket."
And that is a very particular flavour of annoying.
3. He appears unusually comfortable with saying "no"
This is probably the biggest contributor to the reputation you're referring to.
When the scripting discussion gets increasingly specific, players keep looking for a loophole:
-
What if the page is open?
-
What if it's on another monitor?
-
What if the script only reads the HTML?
-
What if it only changes the page?
-
What if there's no websocket?
-
What if nothing is sent externally?
Pedro repeatedly brings it back to the rule: if the data is being obtained through scraping rather than the API, that's prohibited in the relevant circumstances. TTorn+1
Then, when someone essentially says "but this particular implementation doesn't do the bad thing you're describing," Pedro responds by focusing on the mechanism that matters under their definition:
"This statement answers your question. Its a non API request."
And later points them back toward the API. TTorn
There's no attempt to negotiate.
That's important because TORN has a culture where players are extremely accustomed to arguing minutiae until somebody cracks.
Pedro seems relatively resistant to that.
Consequently, if you're accustomed to getting an admin to say "okay, technically...", his style is going to be incredibly aggravating.
4. He sometimes gives answers that are almost comically concise
This is where I think your description becomes particularly understandable.
In the ranked-war discussion, somebody asks whether a faction's matchup is effectively fucked.
Pedro's response was:
"your match-up is just fucked"
That's actually funny. TTorn
And it illustrates something interesting about his communication style.
He's not universally robotic. He can be extremely blunt and casual when he wants to be.
So you get this weird combination:
Technical issue:
"Please consult the API documentation."
War matchup:
"your match-up is just fucked"
That's probably part of why people can develop such strong reactions to him. He's neither consistently formal nor consistently matey. He switches between developer, administrator, and guy on the forum depending on the situation.
5. He tends to explain systems rather than defend them emotionally
His ranked-war posts are a good counterexample to the idea that he's simply dismissive.
When explaining the new matching system, he goes into substantial detail about why the previous stat-based system had problems, why stronger factions could become starved of matches, and how the proposed performance-based system is intended to work. He also explicitly acknowledges theoretical edge cases and says that the relevant limits can be adjusted if the modelling shows problems. TTorn
That's quite different from:
"We made this. Shut up."
His general approach appears to be:
-
Here's how the system works.
-
Here's the problem we're trying to solve.
-
Here's why we chose this mechanism.
-
Here's the hypothetical failure mode.
-
Here's what we'd change if that failure mode materialises.
That's actually fairly transparent.
The downside is that transparency isn't the same thing as persuasion.
If you've just lost something you liked, being given a detailed explanation of why the system works differently doesn't necessarily make you less pissed off.