update for new units?

[Berokk]

could you please update this to work for the new units :((((?

[Newb420]

yes please update!!! this bot is too good

[Jimm1432]

Check my fork

[hatehackppl]

Check my fork

Hi mate, thanks for the updates... But there few bugs 1) PVP ads not working 2) game will stuck in several minutes (10-15min), restarting game not working

• suggest to force restart bluestack and re-open the game (if possible) 3) can priority on upgrade rank instant of upgrade level?

Thanks in advanced if possible to help, or can you teach me how to modify the bugs

[Jimm1432]

I haven't spent much time looking deeply at the code but there are a lot of ads/collection of rewards that doesn't either work or totally not implemented.

The game does freeze and throwing the adb codes doesn't always close it when it crashes like that. I could get it to close bluestacks but then you will have issues with reconnecting to a new client. it would be more work then it's worth if i can fix the problem in the first place.

the mana level is just upgraded each combat cycle I think, it could be removed from the cycle or only upgraded when the ranks reach a certain level which should be better, I'm working on things like this but I don't have a lot of time to work on it right now. if you have the knowledge then a IF rank = 15-20 etc would be a quick fix for now. combat loop is within bot handler, line 68. right now the bot has no way to read the mana level itself I don't think but it does add the ranks up so can be stopped that way.

I'm going to try and get all ads working smoothly and get the speed of bot a bit faster, since this is someone else's work I've had to work stuff out and my first priority was getting it to work as it was but I'm now trying to improve what's there.

[Newb420]

awesome! im glad someone is updating this project tho! will be following for any updates!

Exception in thread Thread-1: Traceback (most recent call last): File "C:\Users\civic\AppData\Local\Programs\Python\Python39\lib\threading.py", line 980, in _bootstrap_inner self.run() File "C:\Users\civic\AppData\Local\Programs\Python\Python39\lib\threading.py", line 917, in run self._target(*self._args, **self._kwargs) File "C:\Users\civic\Desktop\Rush-Royale-Bot-main-all unit fork\Src\gui.py", line 109, in start_bot self.bot_instance.bot_stop = False AttributeError: 'NoneType' object has no attribute 'bot_stop' get this error when starting

On Sat, Jun 17, 2023, 4:12 PM James @.***> wrote:

I haven't spent much time looking deeply at the code but there are a lot of ads/collection of rewards that doesn't either work or totally not implemented.

The game does freeze and throwing the adb codes doesn't always close it when it crashes like that. I could get it to close bluestacks but then you will have issues with reconnecting to a new client. it would be more work then it's worth if i can fix the problem in the first place.

the mana level is just upgraded each combat cycle I think, it could be removed from the cycle or only upgraded when the ranks reach a certain level which should be better, I'm working on things like this but I don't have a lot of time to work on it right now. if you have the knowledge then a IF rank = 15-20 etc would be a quick fix for now. combat loop is within bot handler, line 68. right now the bot has no way to read the mana level itself I don't think but it does add the ranks up so can be stopped that way.

I'm going to try and get all ads working smoothly and get the speed of bot a bit faster, since this is someone else's work I've had to work stuff out and my first priority was getting it to work as it was but I'm now trying to improve what's there.

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1595862212, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASSSXUJ4PRAVJOXW67TJAODXLYMVJANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Jimm1432]

either restart your pc or kill the adb process before starting bluestacks again.

[Newb420]

either restart your pc or kill the adb process before starting bluestacks again.

hmm seems neither worked :/

add me on discord if u can please newb4u or newb4u#9171

[Jimm1432]

I'll add my current files to my fork later, I'm working on the ads right now but my bot is running stable for me right now so I'll post it. It's not working on the ads correctly yet but close

On Wed, 21 Jun 2023, 16:55 Newb420, @.***> wrote:

either restart your pc or kill the adb process before starting bluestacks again.

hmm seems neither worked :/

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1601099930, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWO3UQPRDTR4A4IULCDXMMKN7ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Newb420]

I'll add my current files to my fork later, I'm working on the ads right now but my bot is running stable for me right now so I'll post it. It's not working on the ads correctly yet but close … On Wed, 21 Jun 2023, 16:55 Newb420, @.> wrote: either restart your pc or kill the adb process before starting bluestacks again. hmm seems neither worked :/ — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWO3UQPRDTR4A4IULCDXMMKN7ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.>

sounds good i'll check back later and see if your update fixes my issue.

thanks alot!

[Newb420]

I'll add my current files to my fork later, I'm working on the ads right now but my bot is running stable for me right now so I'll post it. It's not working on the ads correctly yet but close … On Wed, 21 Jun 2023, 16:55 Newb420, @.> wrote: either restart your pc or kill the adb process before starting bluestacks again. hmm seems neither worked :/ — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWO3UQPRDTR4A4IULCDXMMKN7ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.>

Still throwing Exception in thread Thread-1: Traceback (most recent call last): File "C:\Users\civic\AppData\Local\Programs\Python\Python39\lib\threading.py", line 980, in _bootstrap_inner self.run() File "C:\Users\civic\AppData\Local\Programs\Python\Python39\lib\threading.py", line 917, in run self._target(*self._args, **self._kwargs) File "C:\Users\civic\Desktop\Rush-Royale-Bot-main\Src\gui.py", line 109, in start_bot self.bot_instance.bot_stop = False AttributeError: 'NoneType' object has no attribute 'bot_stop'

[Jimm1432]

I'm not sure what to tell you, from what I think is happening is that the thread attached to the bot has frozen\crashed and it's not getting the state it expected.

If you are moving to my fork from the main fork I would recommend deleting the whole bot folder before reinstalling it.

Make sure you are using the correct python version in the read me file and that you have added the Path during installation.

The bot requires that python version, I have tried newer versions but they don't work, I'm not sure if it's just because of the virtual environment or changes within python itself.

I do want to bring everything up to the latest software in current repos then it should be fine for a few years but that's not a priority.

On Thu, 22 Jun 2023, 16:15 Newb420, @.***> wrote:

I'll add my current files to my fork later, I'm working on the ads right now but my bot is running stable for me right now so I'll post it. It's not working on the ads correctly yet but close … <#m-8798869432947546393> On Wed, 21 Jun 2023, 16:55 Newb420, @.> wrote: either restart your pc or kill the adb process before starting bluestacks again. hmm seems neither worked :/ — Reply to this email directly, view it on GitHub <#67 (comment) https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1601099930>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWO3UQPRDTR4A4IULCDXMMKN7ANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWO3UQPRDTR4A4IULCDXMMKN7ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.>

Still throwing Exception in thread Thread-1: Traceback (most recent call last): File "C:\Users\civic\AppData\Local\Programs\Python\Python39\lib\threading.py", line 980, in _bootstrap_inner self.run() File "C:\Users\civic\AppData\Local\Programs\Python\Python39\lib\threading.py", line 917, in run self._target(*self._args, **self._kwargs) File "C:\Users\civic\Desktop\Rush-Royale-Bot-main\Src\gui.py", line 109, in start_bot self.bot_instance.bot_stop = False AttributeError: 'NoneType' object has no attribute 'bot_stop'

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1602821815, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWKMXH5A4WRY5LQC2PTXMRORPANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Newb420]

I'm not sure what to tell you, from what I think is happening is that the thread attached to the bot has frozen\crashed and it's not getting the state it expected. If you are moving to my fork from the main fork I would recommend deleting the whole bot folder before reinstalling it. Make sure you are using the correct python version in the read me file and that you have added the Path during installation. The bot requires that python version, I have tried newer versions but they don't work, I'm not sure if it's just because of the virtual environment or changes within python itself. I do want to bring everything up to the latest software in current repos then it should be fine for a few years but that's not a priority. … On Thu, 22 Jun 2023, 16:15 Newb420, @.> wrote: I'll add my current files to my fork later, I'm working on the ads right now but my bot is running stable for me right now so I'll post it. It's not working on the ads correctly yet but close … <#m-8798869432947546393> On Wed, 21 Jun 2023, 16:55 Newb420, @.> wrote: either restart your pc or kill the adb process before starting bluestacks again. hmm seems neither worked :/ — Reply to this email directly, view it on GitHub <#67 (comment) <#67 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWO3UQPRDTR4A4IULCDXMMKN7ANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWO3UQPRDTR4A4IULCDXMMKN7ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.> Still throwing Exception in thread Thread-1: Traceback (most recent call last): File "C:\Users\civic\AppData\Local\Programs\Python\Python39\lib\threading.py", line 980, in _bootstrap_inner self.run() File "C:\Users\civic\AppData\Local\Programs\Python\Python39\lib\threading.py", line 917, in run self._target(self._args, self._kwargs) File "C:\Users\civic\Desktop\Rush-Royale-Bot-main\Src\gui.py", line 109, in start_bot self.bot_instance.bot_stop = False AttributeError: 'NoneType' object has no attribute 'bot_stop' — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWKMXH5A4WRY5LQC2PTXMRORPANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

what version of python? 3.9.13? because thats the one im using. This might be the issue tho since other bot throws this error when starting but finds a connection through different port cannot connect to daemon at tcp:5037: cannot connect to 127.0.0.1:5037: No connection could be made because the target machine actively refused it. (10061)

• daemon not running; starting now at tcp:5037
• daemon started successfully Found ADB device! emulator-5554

[Jimm1432]

You should delete everything and redownload it. Make sure you are getting the repo from my fork not the main. Your running the correct python version so that is fine.

The error you are putting up shouldn't be possible with my fork since it shows emulator-5554 and my files would show the scrpy window title.

Delete the bot folder, redownload the repo from Jimm1432's Fork, extract it where you want it, run install.bat then the launch_gui.bat.

[Kurouoe]

You should delete everything and redownload it. Make sure you are getting the repo from my fork not the main. Your running the correct python version so that is fine.

The error you are putting up shouldn't be possible with my fork since it shows emulator-5554 and my files would show the scrpy window title.

Delete the bot folder, redownload the repo from Jimm1432's Fork, extract it where you want it, run install.bat then the launch_gui.bat.

i have the same issue, whit the guy in here Exception in thread Thread-1: Traceback (most recent call last): File "C:\Users\piru_\AppData\Local\Programs\Python\Python39\lib\threading.py", line 980, in _bootstrapinner self.run() File "C:\Users\piru\AppData\Local\Programs\Python\Python39\lib\threading.py", line 917, in run self._target(*self._args, **self.kwargs) File "C:\Users\piru\OneDrive\Escritorio\REWOERDKED\Rush-Royale-Bot-main\Src\gui.py", line 109, in start_bot self.bot_instance.bot_stop = False AttributeError: 'NoneType' object has no attribute 'bot_stop'

[Jimm1432]

Do you guys have allow discord and usb debugging turned on?

On Tue, 27 Jun 2023, 21:33 Kurouoe, @.***> wrote:

You should delete everything and redownload it. Make sure you are getting the repo from my fork not the main. Your running the correct python version so that is fine.

The error you are putting up shouldn't be possible with my fork since it shows emulator-5554 and my files would show the scrpy window title.

Delete the bot folder, redownload the repo from Jimm1432's Fork, extract it where you want it, run install.bat then the launch_gui.bat.

i have the same issue, whit the guy in here

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1610173753, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWNG6UHUGDHFHKQ7RNLXNM7RFANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Kurouoe]

of curse, i have allow discord on BStacks and debuggin on

[Jimm1432]

Has it ever worked for you and when did you start having issues? Is it only my fork that does it?

On Wed, 28 Jun 2023, 15:32 Kurouoe, @.***> wrote:

of curse, i have allow discord on BStacks and debuggin on

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1611537798, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWMXAHOHES5L34SO4TLXNQ57VANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Kurouoe]

yes, its only u fork, the mein bot works normaly whit no new unitys, thats weird

[Jimm1432]

Take the all_units folder from my fork and use it with the main fork. It will add the new units.

On Wed, 28 Jun 2023, 19:17 Kurouoe, @.***> wrote:

yes, its only u fork, the mein bot works normaly whit no new unitys, thats weird

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1611875732, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWPF3KONBFP5F6CRVMTXNRYKBANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Kurouoe]

Yes i ready do that, and the old old code works, but ur code has the ads watch what the old not have, or that i read in the description of ur rework code

[Berokk]

Check my fork

since new update your version dosent work anymore for me before it worked perfectly

[hatehackppl]

to fix the error just copy original file (.scrcpy) to your new downloaded folder... problem solved

[Jimm1432]

I'll check it out, It might need rolling back to scrpy 1.24. I have no issues but if others are it might be best.

On Thu, 29 Jun 2023, 08:11 hatehackppl, @.***> wrote:

to fix the error just copy original file (.scrcpy) to your new downloaded folder... problem solved

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1612533262, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWMJ6A42PTCCNCAHY4LXNUTD3ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Kurouoe]

to fix the error just copy original file (.scrcpy) to your new downloaded folder... problem solved

that not solve the problem, the issue is still there

[Kurouoe]

I'll check it out, It might need rolling back to scrpy 1.24. I have no issues but if others are it might be best. … On Thu, 29 Jun 2023, 08:11 hatehackppl, @.> wrote: to fix the error just copy original file (.scrcpy) to your new downloaded folder... problem solved — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWMJ6A42PTCCNCAHY4LXNUTD3ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.>

please, ur are god

[Berokk]

I'll check it out, It might need rolling back to scrpy 1.24. I have no issues but if others are it might be best. … On Thu, 29 Jun 2023, 08:11 hatehackppl, @.> wrote: to fix the error just copy original file (.scrcpy) to your new downloaded folder... problem solved — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWMJ6A42PTCCNCAHY4LXNUTD3ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.>

Exception in thread Thread-3: Traceback (most recent call last): File "C:\Users\grad9\AppData\Local\Programs\Python\Python39\lib\threading.py", line 980, in _bootstrap_inner self.run() File "C:\Users\grad9\AppData\Local\Programs\Python\Python39\lib\threading.py", line 917, in run self._target(*self._args, **self._kwargs) File "C:\Users\grad9\OneDrive\Desktop\Rush-chad\Src\bot_handler.py", line 83, in bot_loop config_selector.move_window(event) NameError: name 'event' is not defined

this is the error i get any fix?

[Jimm1432]

i added my .scrpy folder to my fork, try deleting yours and throwing it in.

[Kurouoe]

i added my .scrpy folder to my fork, try deleting yours and throwing it in.

where is it?

[Jimm1432]

sorry i had to change the folder name, it'll need renaming to .scrpy from @scrpy. github wouldn't upload it as it was

[Kurouoe]

sorry i had to change the folder name, it'll need renaming to .scrpy from @scrpy. github wouldn't upload it as it was

Exception in thread Thread-3: Traceback (most recent call last): File "C:\Users\piru_\AppData\Local\Programs\Python\Python39\lib\threading.py", line 980, in _bootstrapinner self.run() File "C:\Users\piru\AppData\Local\Programs\Python\Python39\lib\threading.py", line 917, in run self._target(*self._args, **self.kwargs) File "C:\Users\piru\OneDrive\Escritorio\3a\Rush-Royale-Bot-main\Src\bot_handler.py", line 83, in bot_loop config_selector.move_window(event) NameError: name 'event' is not defined

Nothing changed, the error persists with your code :(

[hatehackppl]

Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.move_window(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =)

[Jimm1432]

I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up.

On Sat, 1 Jul 2023, 01:34 hatehackppl, @.***> wrote:

Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.move_window(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =)

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1615308420, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Kurouoe]

I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … On Sat, 1 Jul 2023, 01:34 hatehackppl, @.> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.move_window(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.>

now the bot works and starts correctly, but when it comes to start farming floor 5 it gets stuck infinitely in"menu: star 1" [10:44] Bot mainloop started [10:44] menu, wait count: 0 menu, wait count: 1 menu, wait count: 2 menu, wait count: 3 menu, wait count: 4 menu, wait count: 5 infinitely per hours, never starts a coop

[Jimm1432]

Change the game to English it won't work correctly otherwise

On Sat, 1 Jul 2023, 14:43 Kurouoe, @.***> wrote:

I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … <#m7464466501590339274> On Sat, 1 Jul 2023, 01:34 hatehackppl, @.*> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.move_window(event)' > Ctrl

• S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 (comment) https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1615308420>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.*>

ahora el bot funciona e inicia correctamente, pero a la hora de comenzar a farmear el piso 5 queda trabado infinitamente en "menu: star 1" "menu: star 1" "menu: star 1"

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1615920154, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWNFPNDVGKZODL2NDLTXOASPZANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Kurouoe]

Change the game to English it won't work correctly otherwise … On Sat, 1 Jul 2023, 14:43 Kurouoe, @.> wrote: I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … <#m7464466501590339274> On Sat, 1 Jul 2023, 01:34 hatehackppl, @.> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.move_window(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 (comment) <#67 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.> ahora el bot funciona e inicia correctamente, pero a la hora de comenzar a farmear el piso 5 queda trabado infinitamente en "menu: star 1" "menu: star 1" "menu: star 1" — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWNFPNDVGKZODL2NDLTXOASPZANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.>

I already have it in English

[Newb420]

I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … On Sat, 1 Jul 2023, 01:34 hatehackppl, @._> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.movewindow(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @_._>

now the bot works and starts correctly, but when it comes to start farming floor 5 it gets stuck infinitely in"menu: star 1" [10:44] Bot mainloop started [10:44] menu, wait count: 0 menu, wait count: 1 menu, wait count: 2 menu, wait count: 3 menu, wait count: 4 menu, wait count: 5 infinitely per hours, never starts a coop

All you did was delete 'config_selector.move_window(event)'? to get working tried this and still getting same error did u do anything else?

[Newb420]

Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.move_window(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =)

thanks for fix! needed scrpy 1.24 also

[Newb420]

I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … On Sat, 1 Jul 2023, 01:34 hatehackppl, @._> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.movewindow(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @_._>

now the bot works and starts correctly, but when it comes to start farming floor 5 it gets stuck infinitely in"menu: star 1" [10:44] Bot mainloop started [10:44] menu, wait count: 0 menu, wait count: 1 menu, wait count: 2 menu, wait count: 3 menu, wait count: 4 menu, wait count: 5 infinitely per hours, never starts a coop

u have to make sure its in 1600x900

[Jimm1432]

Yeah follow the instructions in the readme before you say it doesn't work

On Sun, 2 Jul 2023, 06:36 Newb420, @.***> wrote:

I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … <#m7979019613981548819> On Sat, 1 Jul 2023, 01:34 hatehackppl, @.*> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.move_window(event)' > Ctrl

• S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 (comment) https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1615308420>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @*.>

now the bot works and starts correctly, but when it comes to start farming floor 5 it gets stuck infinitely in"menu: star 1" [10:44] Bot mainloop started [10:44] menu, wait count: 0 menu, wait count: 1 menu, wait count: 2 menu, wait count: 3 menu, wait count: 4 menu, wait count: 5 infinitely per hours, never starts a coop

u have to make sure its in 1600x900

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1616386367, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWMNAFZ5RYXXX3LMXYLXOECG5ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Kurouoe]

Yeah follow the instructions in the readme before you say it doesn't work … On Sun, 2 Jul 2023, 06:36 Newb420, @.> wrote: I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … <#m7979019613981548819> On Sat, 1 Jul 2023, 01:34 hatehackppl, @.> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.movewindow(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 (comment) <#67 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @._> now the bot works and starts correctly, but when it comes to start farming floor 5 it gets stuck infinitely in"menu: star 1" [10:44] Bot mainloop started [10:44] menu, wait count: 0 menu, wait count: 1 menu, wait count: 2 menu, wait count: 3 menu, wait count: 4 menu, wait count: 5 infinitely per hours, never starts a coop u have to make sure its in 1600x900 — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWMNAFZ5RYXXX3LMXYLXOECG5ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.>

I did all the right things, I know how to read, the old one works perfectly, I don't know what's wrong with yours.

[Jimm1432]

Then use the old one, I don't really care if you can't get it to work since everyone else has it working. There is no reason it shouldn't be working if you follow the instructions.

If you're using anything other than win 10+ and have it set to English language, using the correct resolution and the game in English language then I can't help you, my changes aren't anything that would cause it to not work over the original.

On Sun, 2 Jul 2023, 17:08 Kurouoe, @.***> wrote:

Yeah follow the instructions in the readme before you say it doesn't work … <#m-4355198513047349484> On Sun, 2 Jul 2023, 06:36 Newb420, @.*> wrote: I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … <#m7979019613981548819> On Sat, 1 Jul 2023, 01:34 hatehackppl, @.> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.movewindow(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 https://github.com/AxelBjork/Rush-Royale-Bot/issues/67 (comment) <#67 (comment) https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1615308420>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @._> now the bot works and starts correctly, but when it comes to start farming floor 5 it gets stuck infinitely in"menu: star 1" [10:44] Bot mainloop started [10:44] menu, wait count: 0 menu, wait count: 1 menu, wait count: 2 menu, wait count: 3 menu, wait count: 4 menu, wait count: 5 infinitely per hours, never starts a coop u have to make sure its in 1600x900 — Reply to this email directly, view it on GitHub <#67 (comment) https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1616386367>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWMNAFZ5RYXXX3LMXYLXOECG5ANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWMNAFZ5RYXXX3LMXYLXOECG5ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

hice todo lo correcto , se leer chico, el viejo funciona perfectamente, nose que tiene el tuyo

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1616714157, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWLDGN46MEMGNCBG3LLXOGMHNANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Newb420]

Yeah follow the instructions in the readme before you say it doesn't work … On Sun, 2 Jul 2023, 06:36 Newb420, @._> wrote: I do wonder if you guys are updating the repo correctly because I removed the event error right after I saw the post, the threading error isn't the code it's normally when there was an issue with scrpy or bluestacks and adb.exe isn't getting hooked up. … <#m7979019613981548819> On Sat, 1 Jul 2023, 01:34 hatehackppl, @._> wrote: Found the Bug 'Event' Go to Scr > bot_handler.py (right click edit with ide) > (ctrl + F find 'Event') Delete the column 'config_selector.movewindow(event)' > Ctrl + S (save) Running well for me now ( thanks me later) =) — Reply to this email directly, view it on GitHub <#67 (comment) <#67 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY https://github.com/notifications/unsubscribe-auth/AI2CHWOAUAZTQTOAV5WC7DDXN5WBXANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @_.__> now the bot works and starts correctly, but when it comes to start farming floor 5 it gets stuck infinitely in"menu: star 1" [10:44] Bot mainloop started [10:44] menu, wait count: 0 menu, wait count: 1 menu, wait count: 2 menu, wait count: 3 menu, wait count: 4 menu, wait count: 5 infinitely per hours, never starts a coop u have to make sure its in 1600x900 — Reply to this email directly, view it on GitHub <#67 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWMNAFZ5RYXXX3LMXYLXOECG5ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.**>

I did all the right things, I know how to read, the old one works perfectly, I don't know what's wrong with yours.

I just told you how to fix just make sure you start bluestacks in 1600x900 and it'll work!

[hatehackppl]

Bot not running after game patched... any solution for bot to start the game again?

[Kurouoe]

Bot not running after game patched... any solution for bot to start the game again?

You know I think the bug comes with the first win of the day banner, I have done everything and tried everything, followed each and every one of the instructions to the letter but still it stays infinitely in the start menu in loop, both the old code and the code made by james,

[hatehackppl]

Game wont start, error in loop... any idea?

[08:27] GUI started! [08:27] Stored settings to config! [08:27] Starting bot... [08:27] Selected units: banner, bruser, demon_hunter, trapper, frost [08:27] PVE is set to True [08:27] Bot mainloop started [08:27] menu, wait count: 0 [08:27] menu, wait count: 1 [08:27] menu, wait count: 2 [08:28] menu, wait count: 3 [08:28] menu, wait count: 4 [08:28] menu, wait count: 5 [08:28] menu, wait count: 6 [08:28] menu, wait count: 7 [08:28] menu, wait count: 8 [08:28] menu, wait count: 9 [08:28] menu, wait count: 10 [08:29] menu, wait count: 11 [08:29] lost, wait count: 12 [08:29] lost, wait count: 13 [08:29] lost, wait count: 14 [08:29] lost, wait count: 15 [08:29] lost, wait count: 16 [08:29] lost, wait count: 17 [08:29] lost, wait count: 18 [08:29] lost, wait count: 19 [08:29] lost, wait count: 20 [08:29] lost, wait count: 21

[Kurouoe]

Game wont start, error in loop... any idea?

[08:27] GUI started! [08:27] Stored settings to config! [08:27] Starting bot... [08:27] Selected units: banner, bruser, demon_hunter, trapper, frost [08:27] PVE is set to True [08:27] Bot mainloop started [08:27] menu, wait count: 0 [08:27] menu, wait count: 1 [08:27] menu, wait count: 2 [08:28] menu, wait count: 3 [08:28] menu, wait count: 4 [08:28] menu, wait count: 5 [08:28] menu, wait count: 6 [08:28] menu, wait count: 7 [08:28] menu, wait count: 8 [08:28] menu, wait count: 9 [08:28] menu, wait count: 10 [08:29] menu, wait count: 11 [08:29] lost, wait count: 12 [08:29] lost, wait count: 13 [08:29] lost, wait count: 14 [08:29] lost, wait count: 15 [08:29] lost, wait count: 16 [08:29] lost, wait count: 17 [08:29] lost, wait count: 18 [08:29] lost, wait count: 19 [08:29] lost, wait count: 20 [08:29] lost, wait count: 21

We have the same issue

[Jimm1432]

I haven't checked it myself but you do need to remove the first win of the day for the bot to run correctly since it blocks something needed to see the home screen

On Thu, 6 Jul 2023, 01:42 Kurouoe, @.***> wrote:

Game wont start, error in loop... any idea?

[08:27] GUI started! [08:27] Stored settings to config! [08:27] Starting bot... [08:27] Selected units: banner, bruser, demon_hunter, trapper, frost [08:27] PVE is set to True [08:27] Bot mainloop started [08:27] menu, wait count: 0 [08:27] menu, wait count: 1 [08:27] menu, wait count: 2 [08:28] menu, wait count: 3 [08:28] menu, wait count: 4 [08:28] menu, wait count: 5 [08:28] menu, wait count: 6 [08:28] menu, wait count: 7 [08:28] menu, wait count: 8 [08:28] menu, wait count: 9 [08:28] menu, wait count: 10 [08:29] menu, wait count: 11 [08:29] lost, wait count: 12 [08:29] lost, wait count: 13 [08:29] lost, wait count: 14 [08:29] lost, wait count: 15 [08:29] lost, wait count: 16 [08:29] lost, wait count: 17 [08:29] lost, wait count: 18 [08:29] lost, wait count: 19 [08:29] lost, wait count: 20 [08:29] lost, wait count: 21

We have the same issue

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1622743930, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOQ5I2JMQCSOPLQXBTXOYCYNANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[Jimm1432]

There are no bugs with the bot, a lot of you guys problems are either you're not following the install instructions or the update has put a banner over the PvP start button which has to be a removed before it will run correctly.

I will only be answering people that put issues on my fork from now on because I'm answering people for the main repo and it's not the same as my fork.

On Thu, 6 Jul 2023, 02:46 James Doble, @.***> wrote:

I haven't checked it myself but you do need to remove the first win of the day for the bot to run correctly since it blocks something needed to see the home screen

On Thu, 6 Jul 2023, 01:42 Kurouoe, @.***> wrote:

Game wont start, error in loop... any idea?

[08:27] GUI started! [08:27] Stored settings to config! [08:27] Starting bot... [08:27] Selected units: banner, bruser, demon_hunter, trapper, frost [08:27] PVE is set to True [08:27] Bot mainloop started [08:27] menu, wait count: 0 [08:27] menu, wait count: 1 [08:27] menu, wait count: 2 [08:28] menu, wait count: 3 [08:28] menu, wait count: 4 [08:28] menu, wait count: 5 [08:28] menu, wait count: 6 [08:28] menu, wait count: 7 [08:28] menu, wait count: 8 [08:28] menu, wait count: 9 [08:28] menu, wait count: 10 [08:29] menu, wait count: 11 [08:29] lost, wait count: 12 [08:29] lost, wait count: 13 [08:29] lost, wait count: 14 [08:29] lost, wait count: 15 [08:29] lost, wait count: 16 [08:29] lost, wait count: 17 [08:29] lost, wait count: 18 [08:29] lost, wait count: 19 [08:29] lost, wait count: 20 [08:29] lost, wait count: 21

We have the same issue

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1622743930, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWOQ5I2JMQCSOPLQXBTXOYCYNANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>

[hatehackppl]

There are no bugs with the bot, a lot of you guys problems are either you're not following the install instructions or the update has put a banner over the PvP start button which has to be a removed before it will run correctly. I will only be answering people that put issues on my fork from now on because I'm answering people for the main repo and it's not the same as my fork. … On Thu, 6 Jul 2023, 02:46 James Doble, @.> wrote: I haven't checked it myself but you do need to remove the first win of the day for the bot to run correctly since it blocks something needed to see the home screen On Thu, 6 Jul 2023, 01:42 Kurouoe, @.> wrote: > Game wont start, error in loop... any idea? > > [08:27] GUI started! [08:27] Stored settings to config! [08:27] Starting > bot... [08:27] Selected units: banner, bruser, demon_hunter, trapper, frost > [08:27] PVE is set to True [08:27] Bot mainloop started [08:27] menu, wait > count: 0 [08:27] menu, wait count: 1 [08:27] menu, wait count: 2 [08:28] > menu, wait count: 3 [08:28] menu, wait count: 4 [08:28] menu, wait count: 5 > [08:28] menu, wait count: 6 [08:28] menu, wait count: 7 [08:28] menu, wait > count: 8 [08:28] menu, wait count: 9 [08:28] menu, wait count: 10 [08:29] > menu, wait count: 11 [08:29] lost, wait count: 12 [08:29] lost, wait count: > 13 [08:29] lost, wait count: 14 [08:29] lost, wait count: 15 [08:29] lost, > wait count: 16 [08:29] lost, wait count: 17 [08:29] lost, wait count: 18 > [08:29] lost, wait count: 19 [08:29] lost, wait count: 20 [08:29] lost, > wait count: 21 > > We have the same issue > > — > Reply to this email directly, view it on GitHub > <#67 (comment)>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/AI2CHWOQ5I2JMQCSOPLQXBTXOYCYNANCNFSM6AAAAAAYNEUFXY > . > You are receiving this because you commented.Message ID: > @.***> >

i think you hide the issue in your fork page

[Jimm1432]

It's simple, The bot uses pictures to locate buttons and click in the right location. If you don't have the game in English and Bluestacks in the correct resolution it can't locate them. The bot uses scrpy to watch the screen and adb commands to click/swipe. The only thing that can stop the bot working correctly is it not seeing what it needs to or not grabbing the correct bluestacks adb.

The problem when the console says the machine is not available or has a threading problem is almost always after you close bluestacks\Game crashes within bluestacks. The best way to fix the problem is restarting your pc or you can close the bot, close bluestacks then open task manager and close adb.exe then start again but this doesn't always work so a restart is best.

If the bot is getting stuck trying to click a button or won't start PvE then either you're resolution is wrong or you don't have the game in English. If both are correct and the bot works but got stuck then just stop then start it. It's not a bug like you seem to want to tell me it is and since I changed none of the core bot logic there can not be a single introduced bug in the way the basic bot works since v1.1.

Since they updated the first win of the day banner gets in the way of the bots recognition of a icon it's looking for and must be removed before the bot will run correctly. It's also best to click on each of the shop items with a yellow dot just so that the dot on the main page turns purple.

So since you're going on and on about it being stuck at home then resetting, it's just stuck unable to find and icon or unable to click. As I've explained that is setup problems or you have the first win banner there nothing to do with bug.

To say I'm hiding issues on my fork is just ridiculous, unless there is some setting that is default and stops people posting issues then you just haven't done it.

I want to do a major overhaul but I simply don't have the time, I would like to fix the ads, add collecting rewards and rework how the bot chooses it's merges and when to merge dps units, add the new hero buttons so the bot knows when it's active and doesn't just click it every loop. I'd also get the bot to spawn 3-4 unit right away when a game starts because I don't like how slow it is right now.

There is a lot I have planned but I really don't know when/if it'll ever happen.

On Thu, 6 Jul 2023, 06:08 hatehackppl, @.***> wrote:

There are no bugs with the bot, a lot of you guys problems are either you're not following the install instructions or the update has put a banner over the PvP start button which has to be a removed before it will run correctly. I will only be answering people that put issues on my fork from now on because I'm answering people for the main repo and it's not the same as my fork. … <#m-2510534644471009203> On Thu, 6 Jul 2023, 02:46 James Doble, @.> wrote: I haven't checked it myself but you do need to remove the first win of the day for the bot to run correctly since it blocks something needed to see the home screen On Thu, 6 Jul 2023, 01:42 Kurouoe, @.> wrote: > Game wont start, error in loop... any idea? > > [08:27] GUI started! [08:27] Stored settings to config! [08:27] Starting > bot... [08:27] Selected units: banner, bruser, demon_hunter, trapper, frost > [08:27] PVE is set to True [08:27] Bot mainloop started [08:27] menu, wait > count: 0 [08:27] menu, wait count: 1 [08:27] menu, wait count: 2 [08:28] > menu, wait count: 3 [08:28] menu, wait count: 4 [08:28] menu, wait count: 5 > [08:28] menu, wait count: 6 [08:28] menu, wait count: 7 [08:28] menu, wait > count: 8 [08:28] menu, wait count: 9 [08:28] menu, wait count: 10 [08:29] > menu, wait count: 11 [08:29] lost, wait count: 12 [08:29] lost, wait count: > 13 [08:29] lost, wait count: 14 [08:29] lost, wait count: 15 [08:29] lost, > wait count: 16 [08:29] lost, wait count: 17 [08:29] lost, wait count: 18 > [08:29] lost, wait count: 19 [08:29] lost, wait count: 20 [08:29] lost, > wait count: 21

We have the same issue > > — > Reply to this email directly, view it on GitHub > <#67 (comment) https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1622743930>, or unsubscribe > https://github.com/notifications/unsubscribe-auth/AI2CHWOQ5I2JMQCSOPLQXBTXOYCYNANCNFSM6AAAAAAYNEUFXY . > You are receiving this because you commented.Message ID: > @.***>

i think you hide the issue in your fork page

— Reply to this email directly, view it on GitHub https://github.com/AxelBjork/Rush-Royale-Bot/issues/67#issuecomment-1622995023, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI2CHWPOK45QWR7XNEERS2DXOZB27ANCNFSM6AAAAAAYNEUFXY . You are receiving this because you commented.Message ID: @.***>