Jump to content
  • Relogger is not using additional wrobot args.


    mich125
    • Version: All Product: Relogger Type: Bug Status: Not a Bug

    @Droidz I pmed you this issue, but you didnt reply, could you plz check it out, its importatnt for me.

    I use remote desktop to connect to my botting pc.

    1. If i start Wrobot using Wrobot.exe, it will run ok, but it will crash if i connect to my botting pc using remote desktop.

    2. If i start Wrobot using WRobot.exe -nodx -nolockframe, it will run ok, and it wont crash when i connect to my botting pc using remote desktop. So it is all ok this way.

    But there is an issue if i use relogger.

    In relogger i cant use wrobot.exe, i have to use this other exe file, i do put -nodx -nolockframe, in general settings, additional Wrobot args, like that:

    lQXlOVF.png

    It will run ok, but it will crash when i connect to this pc using remote desktop. It is like relogger doesn't use additional wrobot args that i putted in.



    User Feedback

    Recommended Comments

    Droidz

    Posted

    Hello, I test and args works (you can look your WRobot logs). Is wow, wrobot or the relogger that crash? Can you share your log files

    mich125

    Posted

    Wow stops responding the moment i connect to pc using rdp, if i use  WRobot.exe -nodx -nolockframe without using relogger it works fine when i connect using rdp, so dnno why using relogger changes it.

    Droidz

    Posted

    Do you have try without WRobot (if wow freeze when you using rpd)? You can also try to use teamviewer instead of rdp.

    mich125

    Posted

    No its not freezing, without wrobot ofc, also if i use wrobot without relogger it doesnt freeze.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...