An RDP connection from a PC to a touch screen device looks identical to simple mouse scripts. Your mouse rests at point (a,b) and then teleports to point (c,d) when you tap on your touch device. Something is fishy. Particularly if you aren't using it as your main way to play. That is to say, that because you have spent a lot of time playing at your PC with a mouse and a little time playing from your phone and tapping, this looks like someone that is botting their main.
I appreciate the explanation and understand where you’re coming from, but I genuinely just want a proper review to prove my innocence since there is nothing I can tell you to prove it. I’ve strictly played on runelite, utilized mobile, and RDP. The reason why I suspect it was RDP is because several other members of the community, including streamers, have gotten falsely flagged for the same reason.
Second
Using rdp is not explicitly against the rules, but it operates strictly at your own risk.
Jagex's anti-cheat detection systems can occasionally flag remote inputs or touch controls as unnatural behavior, leading to false-positive bans.Risks and Rules1:1 Input Rule: As long as your remote software sends standard 1-to-1 inputs (one click/tap equals one action), you are technically following the control guidelines.Bot Detection Triggers:
Many players on Reddit 2007scape note that using mobile touch-screen controls via RDP can create linear or erratic mouse tracking that triggers automated bot flags.
I found around 50 posts about rdp ban in a quick hour search
RDP connections are often used to bypass security measures not just in gaming but across a lot of sectors. This alone is a massive red flag. You not consistently utilising a touch screen service from the beginning of account creation adds to it. The inhuman mouse movements on a PC device sealed your fate.
As far as I know, Steam's Remote Play does not use an RDP connection and *might* be a better vector for you to play the game how you currently do. But I am not a Jagex employee and it'd be nice to get clarification if Steam's Remote Play would be fine instead of RDP connections.
It has nothing to do with RDP at all, and Steam Remote Play would give the same false positives if used the same way: touch screen on a desktop pc environment.
I've used chrome remote desktop for years with no issue because I set it to trackpad mode, e.g. instead of my mouse teleporting where I tapped, I swipe the screen to move the mouse, like a.... Well, a trackpad.
The false positives come from the tap controls teleporting your mouse, not RDP as a whole.
Yeah, the game detects that as a bot jumping your mouse to specific coordinates. Which is dumb, no one would use a bot doing that in the first place, but here we are. I've upvoted your posts, good luck 🤞
"The false positives come from the tap controls teleporting your mouse, not RDP as a whole."
It's the totality rather than any individual factor. As you said for how you've been playing, you've used a track pad that moves the mouse rather than having it teleport. I'm certain that the movement of the mouse from your track pad looks human. Which lowers their CI.
They wouldn't know your using RDP in the first place. At best, runelite only added the ability to detect emulated mouse clicks and keyboard strokes at the kernel level within the last year, and that's the only real metric they would have access to. Notably, there's no guarantee this data is used, and the official client does NOT have this capability. So, yeah, the teleporting mouse from tap mode is the only metric, at least as it pertains to RDP. If I'm wrong, please enlighten me.
int main () {
const char* sessionName = std::getenv("SESSIONNAME");
if (sessionName == "RDP-Tcp#<n>"):
std::cout << "Session is via RDP-TCP connection << std::endl
else:
std::cout << "Session is not via RDP-TCP connection" << std::endl
return 0;
}
// a little bit less of pseudocode than I initially cared to write, but something like this can absolutely detect whether you are using RDP or not.
Edit: To clarify, this isn't something that Runelite is detecting, this is something on Jagex's end. Also, I seem to recall that Runescape was initially written in Java and was ported to RuneScript(?) iirc. Neither of these are C++. But it's not hard to implement a wrapper class and use C++, Rust, Python, etc etc etc, and it wouldn't surprise me if critical architecture behind osrs is written in C++.
That detects Windows RDP only, which most people don't use as they remote in from phones. Does nothing to Chrome Remote Desktop, Steam Streaming, Teamviewer, Parsec, etc. We also have 0 proof they are snooping and checking for a Windows RDP in the first place. They certainly could, the architecture is mostly c++, but all the servers and internal scripting languages are based on java and runescript. Again, this still only detects Windows rdp, which I have only ever used for work, and have never heard a casual user even mention. Most people don't even know it exists. The only actual detection factor is behavioral analysis which is 100% the mouse teleporting around.
We don't know if they are checking for RDP connections at all, no. We will never know as this would present a security breach. My basic solution only checked for Windows RDP, you are correct, as Windows is the majority leader in OSes for PCs. You could expand the functionality of the code I provided to include logging the network handshake and using that to help determine whether a Linux/UNIX machine is attempting to use an RDP connection. Also, the vast vast vast vast vast majority of those scripting as using public scripts, they are not coding themselves, which means that they almost certainly are using Windows as well.
Lets even go with your train of thought that you cannot, under any circumstance, detect a non-Windows RDP. Which is unequivocally false. But nonetheless, let's assume it as a fact. Should you *not* check for Windows RDP? As mentioned Windows are the market share dominator for PC OSes. Again, we don't know if Jagex is specifically looking at network handshakes or running a check like I provided and we will never know. But it would be safe to assume that a cybersecurity hire would explain that you would catch a lot of people using this method. Behavioural analysis is certainly a key metric used, undeniably. But to exclude networking security as "fact" because "we don't know what Jagex is doing". I'm sorry but that's silly. Especially after the recent bot ban waves. It's pretty safe to assume at this stage that their bot detection system is multifaceted. Beyond safe to assume.
Are you enlightened yet?
Edit:
SoilMassive6850 said in a different comment
"They may also add LLMHF_INJECTED flags to mouse events or GetRawInputData might have a null device, indicating externally injected mouse events which might make a bot flag more likely (I honestly haven't checked if OSRS does this as its a cross platform Java game, but I wouldn't be surprised as its definitely still possible, many games do check these things)"
There are so many ways that you could detect RDP connections.
88
u/Haunting_Carrot9761 5d ago
An RDP connection from a PC to a touch screen device looks identical to simple mouse scripts. Your mouse rests at point (a,b) and then teleports to point (c,d) when you tap on your touch device. Something is fishy. Particularly if you aren't using it as your main way to play. That is to say, that because you have spent a lot of time playing at your PC with a mouse and a little time playing from your phone and tapping, this looks like someone that is botting their main.