+- The Bytecode Club (https://the.bytecode.club)
+-- Forum: Lobby (https://the.bytecode.club/forumdisplay.php?fid=1)
+--- Forum: Game Cheating, Botting & Reverse Engineering (https://the.bytecode.club/forumdisplay.php?fid=97)
+--- Thread: Developing Bot (/showthread.php?tid=155)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
RE: Developing Bot - k3iroll - 01-01-2015
Tested V5 until V5.3.
By the way, what is the definition of dead base by the bot? Is it full collector? or something else?
The bot was skipping full collector bases when I'm using them.
Haven't got any hit of "dead base" so far.
RE: Developing Bot - shock - 01-01-2015
happy new year to all..
thank you for this..
"this app is not install, please install the app and try again"
this message comes out when the bot detected that it was not on mainscreen..
i try to edit the script to the location of the clash of clan .lnk
"C:\Program Files (x86)\BlueStacks\HD-RunApp.exe" Android com.supercell.clashofclans com.supercell.clashofclans.GameApp"
but it will maximize bluestack..
please help thanks..
RE: Developing Bot - GkevinOD - 01-01-2015
RE: Developing Bot - shock - 01-01-2015
RE: Developing Bot - korpsx - 01-01-2015
So I tested the bot for about 45 minutes and there were some minor glitches. I had to watch and assist it but it was rather awesome watching the bot run.
1. For some reason, when it was "training the troops" it kept bringing down the notification bar of Bluestack and i think it might have messed up finding the barracks as the logs kept saying Barrack 2 Not available etc.
2014-12-31 20:24:25 : Barrack 3 is not available
2014-12-31 20:24:30 : Training Troops Complete
2014-12-31 20:25:02 : Training Troops...
2014-12-31 20:25:15 : Training Troops Complete
2014-12-31 20:25:48 : Training Troops...
2014-12-31 20:26:01 : Training Troops Complete
2014-12-31 20:26:05 : ===============Searching For Base===============
2014-12-31 20:26:18 : Cannot locate Next button, Restarting Bot
2014-12-31 20:26:23 : Training Troops...
2014-12-31 20:26:36 : Training Troops Complete
2014-12-31 20:26:41 : ===============Searching For Base===============
2014-12-31 20:26:53 : Cannot locate Next button, Restarting Bot
2014-12-31 20:26:58 : Training Troops...
2014-12-31 20:27:10 : Training Troops Complete
2. Also in the log above, after it trained the troops, it didnt find the "Attack" button so it had to reset itself because it couldnt find the "Next" button. It looped itself third times, so I just assisted it and hit Attack button first to start Searching for the base.
Suggestion.
I think TH detection would greatly help with the Bot. If it could detect TH, you could have a TH8 attack Th7, etc. (The Bully Mode)
RE: Developing Bot - DiviniT3a - 01-01-2015
Ran into an odd issue earlier. I was using v5.2 bots without a problem until a couple hours ago. It clicked each barracks without issue but failed to click the "Train Troops" button. It said Barrack is not available for each of them. After I went through the process of locating the barracks manually, it trained the troops fine however after attacking it again failed to train troops. I tried restarting the bot, deleting my config file, and restarting blue stacks to no avail. I even tried upgrading to v5.3, and downgrading to v5. I tried locating barracks after each but again couldn't fix the issue. Finally I restarted my computer which didn't solve the issue until I located the barracks manually again. It has been working absolutely fine since. It really isn't an issue since it was fixed with a restart but I thought I would let you know. I'll post if I run into it again and can identify what seemed to cause it.
RE: Developing Bot - GkevinOD - 01-01-2015
RE: Developing Bot - korpsx - 01-01-2015
RE: Developing Bot - shock - 01-01-2015
RE: Developing Bot - DiviniT3a - 01-01-2015
Okay it happened again for me. No Idea what the issue is. I experienced the "Cannot locate Next button, Restarting Bot immediately" problem before it so I don't know if that has anything to do with it.