Bambo

Anyone else mass loosing northdale bots? Just lost like 15 account. Pretty much all at the same time. Doesnt look like reports bans since I lost all 15 with independent IPs and different profiles. All within 30mins.

Are your northdale bots fine?

Er hat vermutlich entdeckt dass man unter General settings das Skinning erstmal aktivieren muss unter Skin/Gather/Mine Mobs 

1 hour ago, Droidz said:

If you can try with the new update

Whatever you did. Keep it like that. Works like a charm.

3 hours ago, Droidz said:

One of your profiles/plugins/fightclasses change bad wow/wrobot settings. Do you have low FPS in game? 

Yea i have very low fps as soon as i start running more than 4 wrobots. I personally think that it is something on your end to be honest. Because my fightclasses have not changed. And i was able to run 9 sessions a few weeks ago. now 5 sessions are laggy as hell

13 hours ago, Droidz said:

Do all steps:

1. Disable all wow addons.
2. Download and install WRobot in new folder, install only your profile (don't install plugins/fightclasses).
3. Run Wow in window mode (not full screen, and never minimize wow window!).
4. Put lower wow graphics quality, but try to get good FPS (40 or more)
5. Run WRobot and check CPU usage and if Wow don't freeze during few minutes. (tell me here with your log file if you get freeze/cpu usage problem)
6. Now start to add you fightclass and check again CPU/freeze during few minutes.
7. Now add one per one Wrobot plugins, wow addons.

This is what I did. Multiple times already. It works a few days but then performance cracks down again.

Looks like there might be some temp files that should be deleted from time to time or something like that. 
I can not reinstall my wrobot and all my classes every few days droidz, this is not gonna work out.

push

problem is still existent

Edit: update fixed it!

Can you be a little bit more specific? What do i do now?

reduced it to 4 active sessions, now it is performance wise really fluent.

from 9 sessions down to 4... i am so upset right now xD

Hey guys, Hey Droidz,

unfortunately I still have huge CPU problems. I already reinstalled the wrobot many times. After a reinstall it seems to be working better. But now after a few days it is pure Horror again.

I can run about 6 instances. It is really choppy already but it works. Anything more and I risk my CPU exploding. A few days ago I botted with 8 sessions with waaay better performance.

I am using the "Low Cpu Usage Vanilla" plugin. I am helpless guys. This is no fun. 

Even if I wanted to I would NEVER pay the plan for 10 wrobot sessions because I simply can not get them to work well without my cpu constantly hitting 100%...

I am really clueless... Some people say they do not have problems at all. Some people's PC crack down under 2 Wrobot Instances.

For anyone who is interested:

CPU: I7 6700HQ 

GP:U: GTX1060

RAM: 16Gigs

This really is destroying my Wrobot experience since I am looking to be a mass botter. Droidz plx fix xD

EDIT: Yes i tried No Framelock.exe or No DX.exe...

4 minutes ago, Bastilla said:

@Bambo das ein BOt immer langsamer sein soll als Menschen das ist absoluter Unsinn. Der Bot kann so programmiert werden, dass a) immer nur die Quests angenommen werden, welche sich zeitmäßig auch lohnen und wenn grinden schneller ist, dann wird gegrindet b) es werden immer die Quests in einer optiumalen Reihenfolge abgearbeitet c) Es werden Pfade einprogrammiert, welche sehr sicher sind und der Char nicht stirbt.

Ich habe nur den bisherigen Ist Zustand mal ein wenig umrissen. Dieses Profil kann man wenn überhaupt als Beta bezeichnen und dafür dann 28€ zu verlangen finde ich absolut unverschämt. In Deutschland würde ich sofort das Produkt wieder zum Fachhändler zurück geben mit dem Hinweis, dass das Produkt halt nur halbfertig ist und die Gesetzeslage gibt mir da absolut Recht.

Ich werde mir das Geld nun bei VISA zurück holen, da wie schon gesagt hier ein sehr schlechtes Produkt zu abenteuerlichen Preisen hier dem Kunden verkauft wird.

Wenn es irgendwann mal halbwegs fertig ist, kann es sein, dass das auch die 28€ Wert ist.

P.S.

Mir ist absolut bewußt, dass das verdammt viel Arbeit ist inkl. sehr vielen Tests. Es ist mir trotzdem ein absolutes Rätsel wofür hier auf Discord hier Tester braucht um seine Skripte zu testen. Es wäre viel günstiger, wenn er selbst sich auf Kronos einen neuen Char anlegt sein Profil laufen lässt und wenn er feststellt, dass der Char irgendwo stirbt oder irgendwo hängen bleibt dann muß man sich Gedanken machen, wie man das an der Stelle verhindert.

Viele Grüße

Ich bleibe bei meinen Standpunkten.

Viele Grüße.

Der Entwickler enraged hat die arbeiten an diesen Profilen aufgenommen und steckt jeden tag zeit und arbeit in die bugfixes. Bitte geh auf das entsprechende discord und überzeuge dich selbst. Melde ihm bugs und erwarte ein fix innerhalb weniger tage.

Mfg

Ps: natürlich ist per hand spielen effektiver. Kein profil der welt wird das ändern.

It is possible using C#. Or you afford the 15 dollar for the plugin Human Master Plugin. It is the price of a cheap restaurant menu and your bottinglife will become so much easier. Worth the money for sure.

You will get way more than just auto equip if you buy humanmaster plugin.

To be honest I can not even think about not using this plugin anymore. It feels like it is a part of the bot itself. You NEED it, if you ask me.

1 hour ago, Droidz said:

Ok nice, thank you. Update WRobot and if you can confirm the problem still resolved.

I can try in about 5 hours. 

Greetings

22 minutes ago, tonycali said:

It works for you with humaninzingplugin on ?.

yes so far it works with the new robotManager.dll

55 minutes ago, Droidz said:

One per one it is better

running for a little more than an hour now, robotManager.dll seems to do the job.

I still have cpu problems though. 7 instances are heavy sometimes...

I am using your new Vanilla Low Cpu Usage plugin, it helps a little bit at least.

2 minutes ago, Droidz said:

Like that here, if someone can test with this file: authManager.dll

i can test after i tested the robotManager.dll if you want? or want me to try both at the same time?

26 minutes ago, Droidz said:

If someone can try with this file: robotManager.dll (close wrobot, download and move this file in folder "wrobot\Bin\" (replace existing file and ignore update resquest when you start WRobot))

Running 7 wrobot.exes now with the new robotManager.dll

Will keep you up to date.

Seit dem Update von Matenias Plugin gibt es keinerlei Probleme mehr die quests abzugeben.

Mfg

6 hours ago, Droidz said:

If sometime you get freeze, you need to put lower value at the sleep times 

Where do I find that sleep time setting? Does that mean I could go for more active sessions? Is there any fps limit where you would say that the bot will not work anymore? Or is Everything memory based and the fps are just for visuals? 

Just now, Matenia said:

Since the last update, it happens sometimes that wRobot "doesn't do anything". So my plugin for example, will log "looting NPC", but nothing happens. It will think it's stuck because it hasn't moved in a while, the unstuck event is sent and my plugin tries to use hearthstone, but none of my Lua calls or SpellManager function calls actually do anything to the game.

does it help to alt tab into to that specific wrobot.exe? because thats what i was experiencing as well. lowering down the overall number of active sessions has helped me so far

I am the same guy from this thread Buddy xD yea i use it. Do I uncomment that line now?

BTW: I am also experiencing many WoW and wrobot crashes recently. Dont know how to fix that either ?

After a clean fresh install it is a little bit better. This is the second reinstall within 3 days. How can i keep this state? Are there any hidden temp files that i should delete sometimes?

For now the wrobots dont seem to forget about themselves but I am sure in a few days it will be broken again.

Any ideas?

Hey,

now that my cpu usage got a little bit better I am running 8 wrobot instances at once. Still very laggy sometimes.. ;(

but the real problem here is that some wrobot.exes just seem to forget they even "exist". the bots do absolutely nothing until i tab in the wrobot.exe. then it suddenly realizes that it should do something and the bot starts his work...

is this due to cpu overload ? is there any way to reduce cpu usage (except for the main.cs plugin by Droidz)? Or how can i fix those "stucks"?

Thats why I am running 12 instances. I hope for 30% Survival rate.