Create a new windows account that will be used in RDP.
Run CMD as administrator and execute net localgroup "Remote Desktop Users" [account_username] /add .
WIN + R → regedit → Goto HKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Client
Create a DWORD value named RemoteDesktop_SuppressWhenMinimized and set it to 2.
WIN + R → mstsc.exe → Show advanced options → Point to localhost & set to rdp username to login
Click on connect
Inside that windows account, place a shortcut to EvE online and install/download Sanderling.
Open EvE client and set al visual settings to low (just a bot, he doesn’t need to see everything beautiful.)
Switch the window mode to Windowed, otherwise, everytime you log in remotely, the EvE client will be minimized (stupid windows)
Disable Dynamic Camera Movement. This way game wont change the camera position, allowing you to set it half distance from ship to not hear the noise, just important sounds like incoming attacks.
Now you can run sanderling and let him do it’s job. It will work as long as you are connected and have the screen openend or minimized. Closing the connection will make Windows go GUI less mode on RDP account , so bot will fail to perform any task.
I don’t know if anyone else had problems getting this to work since the creator update, I sure as hell did!
But someone else found the solution thank god, so I will post it here if anyone else wants to do this but cannot get Remote Desktop to cooperate:
Unzip it into the C:\windows\system32 folder (if the file with the same name exists, rename it to rfxvmt.dll.old).
Do these steps with Administrator rights:
Download the right file for your version windows 32/64, from the above links
Put the file in C:\windows\system32 folder (if the file with the same name exists, rename the old file to rfxvmt.dll.old).
Just a note of warning. Unless you have a way to change the hardware names on each desktop, it will look like you are just using the same computer. So, if you intend to do heavy botting with this, you need to solve that or find a different solution.
I tried following all the replies here and also in the forum of the github for the rdpwrap but i keep getting that listener is not working and service state says stopped
Does this still work for people?
I’m running Win7. I have Desktops v2 running.
I have added two users to the the RDP Group and using rdpwrap I have an rdp conenction to my ip address on each desktop.
When I start eve launcher (alpha account ) in one desktop no problems.
If I then start eve launcher on the other desktop/rdp and try and log in to an omega account it says I can’t because I’m already running alpha.
The accounts are not linked on eve launcher they have separate email accounts.
RDP does not simulate an other machine with an other ip adress, it just allows you to have an other session on the same. Hence regarding CCP you have the same ip adress for each desktop, then for each Eve process. => issue with alpha accounts.
I also tried with multiple IP addresses through a vpn and I could not get an alpha and omega account to reliably connect. I believe I did have both on at same time once but can’t remember what I did to make that happen.
I think it might have been a Virtual machine and your regular windows account.
But Bitenbois is correct RDP doesn’t work with alpha and omega accounts.
All this does is allow you to run several separate EVE instances that each has their own mouse/keyboard input for automation.
This does indeed not hide or mask your IP, if you are worried about your accounts don’t bot
pointed to this topic by one of members here…
reading thru this is semi interesting… some of you guys are trying to wave red flad in front of ccp and wondering why u’ve been caught
freaking never combine alphas and omegas! ccp does have checks for alpha accounts being connected at same time from same computer since very very begining. why someone even trying this?
use omegas only and there is literally NOTHING against having multiple omega clients on same ip/mac address!
sanderling is NOT broadcasting same commands to all clients at same time and even if you are stupid enough to have botted accouns botting in same system eventho there is almost non probability it will give same command at very same millisecond in case of neuts jump in.
and indeed if you are “playing” 5accounts 20hours a day everyday… just dont
rdpwrapper + registry hack works flawlessly even on creators update btw.
if I’m not mistake, you have to enter in the second account ( normal bot) and " let others to connect" -or something similar( add first account to list )
and there it was somthing with the password also
Maybe we will get a more stable option with Windows Sandbox, that does not need to be adapted so often. Not sure though when it is ready for production.
Running two or three mining bots on the same PC is no problem.
The bots can use input focus scheduling to avoid interfering with each other’s inputs. How many you can run in parallel this way depends on the saturation per bot, meaning how many percent of the time it needs to send input. (You can check this for any of your app sessions in devtools)
Starting with the version from December 2020, the engine does this automatically. You only need to switch your app to use the new interface to the host.
