1.The bot not spin supple drop, 2.sometimes can't fire dino

[Archerman888]

The bot not spin supple drop and click X for search again, sometimes can't fire dino because aim always down sometimes target on up or other side

How you setting bulestack ?

[HCA97]

Hi,

It seems like you might need to adjust the time.sleep values (see Adjusting time.sleep #2 (comment)) or you might have selected the Bluestack client incorrectly (see How to select Blue Stack #2 (comment)). Have you checked the comment or the issue in general? In this discussion, you can find helpful tips and tricks on how to use jw_bot. Another person had similar problems with running jw_bot, but they managed to resolve it now. Our conversation might also provide some assistance for your issue.

Note Please keep in mind that depending on your hardware and internet speed, the game might run slower for you. Therefore, you may need to adjust the time.sleep parameters. #2 (comment),

Note Additionally, it's important to accurately select the Bluestack client since the button locations are hardcoded. If you select it incorrectly, the bot might get stuck at certain steps.

P.S. Regarding the Bluestack settings, I used the default shortcuts and set the CPU and RAM to the highest level.

[Archerman888]

Hi,

It seems like you might need to adjust the time.sleep values (see Adjusting time.sleep #2 (comment)) or you might have selected the Bluestack client incorrectly (see How to select Blue Stack #2 (comment)). Have you checked the comment or the issue in general? In this discussion, you can find helpful tips and tricks on how to use jw_bot. Another person had similar problems with running jw_bot, but they managed to resolve it now. Our conversation might also provide some assistance for your issue.

Note Please keep in mind that depending on your hardware and internet speed, the game might run slower for you. Therefore, you may need to adjust the time.sleep parameters. #2 (comment),

Note Additionally, it's important to accurately select the Bluestack client since the button locations are hardcoded. If you select it incorrectly, the bot might get stuck at certain steps.

P.S. Regarding the Bluestack settings, I used the default shortcuts and set the CPU and RAM to the highest level.

I think you right I have to adjust time.sleep but that many time.sleep how I know I mean what the line of time.sleep that use for waiting the bot detect when click on dino or supply drop or when them ramdomly click and wait for detect ?(Now ok detect because I set BlueStacks high core, ram)

But this aim error still happens sometimes cause always aim down this bug ?

[HCA97]

Alright, it seems like you're encountering a similar issue to what someone else faced before #2 (comment). The problem lies in the transition from launching the drone to shooting the dino. There's a check in place to see if there's a loading screen during this transition. This is done by comparing two frames, as you can see in the code here. If there's significant lag, this check might get messed up and you'll end up stuck in the dino shooting state.

I suggest increasing the values for these two time.sleep parameters by adding a second or more:

jw_bot/jw_bot.py

Line 809 in 5529026

time.sleep(2)

jw_bot/jw_bot.py

Line 799 in 5529026

time.sleep(1)

Additionally, try increasing these two time.sleep parameters by adding half a second or more:

jw_bot/jw_bot.py

Line 782 in 5529026

time.sleep(0.2)

jw_bot/jw_bot.py

Line 791 in 5529026

time.sleep(0.8)

If this doesn't fix the issue, try increasing all the time.sleep values in the collect_dino function.

If you still have the problem you can have a look on shoot_dino function and increase the time.sleep values.

Please note that setting up the bot initially can be a bit tricky because Jurassic World is a very laggy game and the amount of lag everyone faces is different.

[Archerman888]

Alright, it seems like you're encountering a similar issue to what someone else faced before #2 (comment). The problem lies in the transition from launching the drone to shooting the dino. There's a check in place to see if there's a loading screen during this transition. This is done by comparing two frames, as you can see in the code here. If there's significant lag, this check might get messed up and you'll end up stuck in the dino shooting state.

I suggest increasing the values for these two time.sleep parameters by adding a second or more:

jw_bot/jw_bot.py

Line 809 in 5529026

time.sleep(2)

jw_bot/jw_bot.py

Line 799 in 5529026

time.sleep(1)

Additionally, try increasing these two time.sleep parameters by adding half a second or more:

jw_bot/jw_bot.py

Line 782 in 5529026

time.sleep(0.2)

jw_bot/jw_bot.py

Line 791 in 5529026

time.sleep(0.8)

If this doesn't fix the issue, try increasing all the time.sleep values in the collect_dino function.

If you still have the problem you can have a look on shoot_dino function and increase the time.sleep values.

Please note that setting up the bot initially can be a bit tricky because Jurassic World is a very laggy game and the amount of lag everyone faces is different.

Almost are better now, but sometimes click dino and show nothing there
or click dino then show launch but go out not launch again and go other....
The real launch little happen

How to make the detect launch(go shoot dino) better ?

[HCA97]

Almost are better now, but sometimes click dino and show nothing there

Sometimes the dino might be mistakenly detected as a supply drop. This can happen from time to time, so it's not unusual.

click dino then show launch but go out not launch again and go other

Hmm, I'm not entirely clear on this. It could still be related to the time.sleep settings. I recommend trying to increase these two parameters:

Additionally, try increasing these two time.sleep parameters by adding half a second or more:

jw_bot/jw_bot.py

Line 782 in 5529026

time.sleep(0.2)

jw_bot/jw_bot.py

Line 791 in 5529026

time.sleep(0.8)

If the issue persists, it might be related to how you're selecting the Bluestack client. Please review the How to select Blue Stack and Running BlueStacks in Non-Full Screen Mode sections in this comment.