FlyFF - Awakebot (Customizable, Support your own server)
Discussion on FlyFF - Awakebot (Customizable, Support your own server) within the Flyff Hacks, Bots, Cheats, Exploits & Macros forum part of the Flyff category.
Hi? It says game client not found
I already copy the code (<Setting name="ProcessName">Neuz</Setting>)
Edit:
Mine now working, change Neuz to MiniA. Now my problem is awake not stopping when it is already awakened with what I wanted and in the logs it says that no awake found. Help pls thanks guys
[19:32:15] No awake found
I'm having the same problem! it's deciding:
[00:16:56] No awake found
[00:16:56] No awake found
[00:16:56] Preferred awake was not achieved
--almost instantly right after clicking the item to awaken it. i also thought "maybe it's the lag and delay in the awakened stats popping up?" so I maximized the delay to 6 seconds and still no luck. it says no awake found x2, preferred awake was not achieved even though the preferred awake is right there.
this was still working... I tested it on Flyff Insanity as of 11/30/2018
I checked your source code, does the combined equal awake variable was the total value of the awakes with the same name?
I tried to set it on ADOCH with 30 value, but when I encountered 2x ADOCH+17, it doesnt sum up.
2x ADOCH+17 would be 34% and it should exceed the ADOCH 30 value that was set.
btw, nice work...
Yeah, that is correct. If you get two awakes of ADOCH+17, the bot will combine them and understand it as ADOCH + 34.
It works fine, I just tried it on Insanity with that type of awake. As long as you can see that the awakes are read correctly in the bot log, then everything should work as expected.
Por que no se detiene en el awake que elijo ?alguien me ayuda
The bot does not stop at the awake I prefer, example in the mazey flyff that is the one I play, its maximum awake is + 300x3 or 300% x3 and I put that amount and the awake does not stop, how do I solve that?
Yeah, that is correct. If you get two awakes of ADOCH+17, the bot will combine them and understand it as ADOCH + 34.
It works fine, I just tried it on Insanity with that type of awake. As long as you can see that the awakes are read correctly in the bot log, then everything should work as expected.