`'*~♥~*'´
would it be possible to allow manually setting the "stop bot in..." time?
i have a macro with levitate before the lure and it has to cast before the 10m is up.
It was working fine for me last night, then got the bright idea "HEY SELF! LETS USE TEAMVIEWER TO KEEP AN EYE ON IT AT WORK! @_@"
So as Nemo was fishing away, I installed team viewer and tested it on my cell phone, worked great! In a cell phone with dual core 1.2ghz 1gb RAM kind of great....
Woke up and I was D/Cd. (this always happens for some reason, about 5am) so I reconnected and Nemo got "Bobber not found"
I was like, "HRMMM" I closed out team viewer and then the Bobber was found. (can't remember if I restarted WoW)
So, make sure team view is closed, open WoW, get to fishing spot, open Nemo, start fishing, open team viewer, be lazy or OCD at work with fishing - Profit.
I think this may have something to do with TeamViewer getting it's 'hooks' into the WoW window first for presentation sharing before Nemo.
I already got the reason. Nemo!Bot isn't the only one with issues. Updated the informations @Firstpost
Bobber not found
For this version please deactivate the TeamViewer - Quick Launche-Option for wolrd of warcraft.
That causes the bobber not found bug.
-- How to configure TeamViewer --
`'*~♥~*'´
..........
Last edited by Trosik; 08-07-2016 at 01:42 PM.
yupp, this bot roxx hard
Seriously, just have to say, in the times I've used this, it's just been f'ing wonderful.
Yea, there's no flying around, fishing up pools, but that would totally bring on suspicion.
I find myself a nice place in the middle of nowhere with my raft, and just fish fish fish away. With Team Viewer (thanks for that work-around!) I can keep an eye on it at work.
With how much fish I fill my bags with, I don't need to do it every day or night. So many tokens. THE TOKENS!
Great work fortiZ!
What if we are experiencing the 'Bobber not found" bug but do not use TeamViewer?
cool bot but there are some severe security issues...
1 - name of application file is Nemo!Bot.exe
warden is checking which applications are running next to wow and getting their executable file name is very easy!
you should change the file name to something like notepad.exe or something inconspicuous
2 - application file attributes are very suspicious
file description: Nemo!Bot
product name: Nemo!Bot
LegalTrademarks: fortiZ
Original Filename: Nemo!Bot.exe
warden can find the running executable files very easily (above) and read the files attributes.
you should get rid of this information which clearly can identify Nemo!Bot being running
3 - application main form has title Nemo!Bot 1.x...
the main form titles of running processes can easily be read by warden and identify Nemo!Bot
you should get rid of that main form title or switch it to something inconspicuous
4 - are you reading data from the ram memory wow is running in? you seem to be reading character health, chat etc
warden is checking if other processes access the wow reserved memory since its not allowed and
since this used by most of the existing wow bots its critical
so in my opinion blizzard can definetely and easily find your bot running until you change at least this things!
(and there are even more issues). even i could write a software which would be capable of checking this things
and find your bot.
not being banned doesnt mean that your bot is secure since blizzard would never ban everyone botting and
lose a lot of customers and money doing so.
totally secure bots are the bots which just simulate user input - e.g. check pixels on the screen, simulate
mouse and keyboard clicks and pretend to be default windows program everyone has on his pc. they dont
interact with the wow process and memory at all and dont have their real name added in the attributes,
form title or other easily accessible places.
and of course you can still mess up running a totally secure bot with behaving in a wrong way,
like farming 24/7 etc but that you ppl do know already!