[New Bot] RuBot

Gameforge is already updated!

So all we have to do is wait for the patch on RUBOT

Hey,

yep we are working on it , if it takes longer than expected , the lost days will be compensated as always so don't worry.

Regards

looks great.but need a free one

Awesome , Thanks! My spirit come back ahaha

._.

any word?

Quote:

Originally Posted by HotBitch ._. any word?

Should happen today , as I said don't worry if it takes longer than the usual 1 day - days will be compensated.

Regards

(keep an eye on site / facebook or here for news)

-----------------------------------------------------
News:

Hey,

update 1.7.11.2 for rubot is out!

Download it via updater or grab it directly from my site.

As always please report any bugs you may encounter.

Regards

-----= EN =-----
- support game clients NA and EU
- fixed a bug with the first cell hotbar
- fixed replays in a combo

Can the bot split twisp or other such bundles? (Craft). Double-click to use them one at a time. I heard about macros for it but don't know how to use it.

Why do I sometimes see the bot standing for a minute trying to select something and writing "Failure, resource is not selected"? If the radius is small (15m), why won't it simply pass it by?? When I set 25m it creates difficulties with getting to Wrud Log/Salix Log, cause they are always at a tree, so a character encounters a tree.

(I'm working with not updated bot now, from 2013-08-03, cause I used to have problems with updated versions since some time. Dunno, maybe it doesn't matter ...)

Quote:

Originally Posted by Goddevilf666ck Can the bot split twisp or other such bundles? (Craft). Double-click to use them one at a time. I heard about macros for it but don't know how to use it. Why do I sometimes see the bot standing for a minute trying to select something and writing "Failure, resource is not selected"? If the radius is small (15m), why won't it simply pass it by?? When I set 25m it creates difficulties with getting to Wrud Log/Salix Log, cause they are always at a tree, so a character encounters a tree. (I'm working with not updated bot now, from 2013-08-03, cause I used to have problems with updated versions since some time. Dunno, maybe it doesn't matter ...)

Try to run very close to the gatherables and put the radius to 6 m.

That message could also come up if a player is close and you have the ignore if player is near option active.

For the unbundling check the example script on my site or the unbundle script by user (Daniil Ovcharenko) [Only registered and activated users can see links. Click Here To Register...] and adjust it to your items + cooldown for it.

Regards

Regards

Sometimes After a fight with a mob i refuses to sit down.
You cant even click the sit button that is on the nr 1 skill
you cant use , key on keybord.
You need to move forward one step then the character sits down.
Note that there is no mob buff like poison or anything similar like that.

I dont know what trigers the sit to not work from time to time.
The char keeps standing up until regenerated.

Please note i did see this in previous versions before ( before this patch )

Hope to help in figuring this out

Kind regards

Quote:

[7:37:49 PM] The main attacker is a cycle ... [7:38:10 PM] Scored 16 quest mob! [7:38:10 PM] Warrior Spirit - 16/17 [7:38:11 PM] Loot from Shaman Spirit (41) [7:38:12 PM] Looting success. [7:38:12 PM] Regeneration HP / MP... [7:38:34 PM] Sat again [7:38:37 PM] Sat again [7:38:39 PM] Sat again [7:38:42 PM] Sat again [7:38:44 PM] Sat again [7:38:46 PM] Sat again [7:38:49 PM] Sat again [7:38:51 PM] Sat again [7:38:54 PM] Sat again [7:38:56 PM] Sat again [7:38:59 PM] Sat again [7:39:01 PM] Sat again [7:39:04 PM] Sat again [7:39:06 PM] Sat again [7:39:08 PM] Sat again [7:39:11 PM] Sat again [7:39:13 PM] Sat again [7:39:16 PM] Sat again [7:39:18 PM] Sat again [7:39:21 PM] Sat again [7:39:23 PM] Sat again [7:39:26 PM] Sat again [7:39:28 PM] Sat again [7:39:30 PM] Sat again [7:39:33 PM] Sat again [7:39:35 PM] Sat again [7:39:38 PM] Sat again [7:39:40 PM] Sat again

this is what the log say's it is longer but you get the point.

Quote:

Originally Posted by Deruddy this is what the log say's it is longer but you get the point.

Have you changed anything else ?

Can you try to default all keys and options , and then run a fresh rubot ? (without configs from earlier)

Because my resting , works fine here (testing currently on gunslinger)

Regards

when you compensate 2 days ? I still read expirated time 13 sept on my rubot :)

Quote:

Originally Posted by bigsuirlife when you compensate 2 days ? I still read expirated time 13 sept on my rubot :)

The time for the update was only 1 Day, and that is in the acceptability time.

Regards

Quote:

Originally Posted by kintarooe Try to run very close to the gatherables and put the radius to 6 m. That message could also come up if a player is close and you have the ignore if player is near option active. For the unbundling check the example script on my site or the unbundle script by user (Daniil Ovcharenko) [Only registered and activated users can see links. Click Here To Register...] and adjust it to your items + cooldown for it. Regards Regards

What means "you have the ignore if player is near option active"? Another player?

Thanks for the Unbundle script, how do I use it?

I get a repeating glitch with mantras for a long time. It happens not always, but happens sometimes - I turn the bot on and the character begins to spin mantras one after another repeatingly, or if it's 1 mantra, turn it on and off and again. Then I only can remove mantras from skills, turn then on manually and work further with the bot. Please fix it!

Quote:

Originally Posted by Goddevilf666ck I get a repeating glitch with mantras for a long time. It happens not always, but happens sometimes - I turn the bot on and the character begins to spin mantras one after another repeatingly, or if it's 1 mantra, turn it on and off and again. Then I only can remove mantras from skills, turn then on manually and work further with the bot. Please fix it!

put only 3mantra's not all , and from the moment the bot is in attack modus the rotation stops.