What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Rift Bot - Yet Another Rifter!

Status
Not open for further replies.
DyingHymn said:
.26 seems pretty good with DB release. Considering recommending an upgrade. Need more testing tho
Click to expand...
Code: 
System.Exception: Element RiftQuestAndStep is not supported. Please check your XML and try again. (<RiftQuestAndStep questId="337492" stepId="1">
  <If condition="CurrentWorldId == 288454">
    <MoveToMapMarker questId="312429" stepId="2" exitNameHash="1938876094" interactRange="15" destinationWorldId="288685" />
    <MoveToMapMarker questId="312429" stepId="2" exitNameHash="1938876094" destinationWorldId="288685" />
  </If>

The profiles are still set for the plugin so gotta still use the plugin even with the new version of trinity.. because of the difference in tags:)
 
gotteshand said:
Code: 
System.Exception: Element RiftQuestAndStep is not supported. Please check your XML and try again. (<RiftQuestAndStep questId="337492" stepId="1">
  <If condition="CurrentWorldId == 288454">
    <MoveToMapMarker questId="312429" stepId="2" exitNameHash="1938876094" interactRange="15" destinationWorldId="288685" />
    <MoveToMapMarker questId="312429" stepId="2" exitNameHash="1938876094" destinationWorldId="288685" />
  </If>

The profiles are still set for the plugin so gotta still use the plugin even with the new version of trinity.. because of the difference in tags:)
Click to expand...

I will not remove .8 recently. Some optimization are performed in the plugin + it add special support for tower of the damned/halls of agony type maps
 
DyingHymn said:
I will not remove .8 recently. Some optimization are performed in the plugin + it add special support for tower of the damned/halls of agony type maps
Click to expand...

That makes sense might be a good idea to mention it in the first post that the new trinity will still need the rift plugin before 1000 posts of people complaining about it "not working" lol..:)
 
okey, so previously i just downloaded the latest xml from the svn directory manually... now i installed svn.

where do i put this code?

"<Repository>
<Kind>Profile</Kind>
<Name>Rift Bot</Name>
<RepoName>Rift Bot</RepoName>
<RepoURL>https://subversion.assembla.com/svn/rift-bot/</RepoURL>
<SourceDirectory>trunk\Profiles</SourceDirectory>
<Enabled>true</Enabled>
<LastUpdate>0001-01-01T00:00:00</LastUpdate>
</Repository>" ??
 
DyingHymn said:
Yes will update. thx
Click to expand...

.26 is the best trinity I've seen so far avoidance working perfect not causing lag or performance timeouts. Pathing and combat are also vastly improved, no more forth and back between a chest and pathing or exploring pretty much 99% of the issues from .24 and .25 are gone. I'd say upgrading to .26 is pretty much a must.
 
I'm getting a lot of "Execution of the block" error with Trinity .26. Tried both the Beta and official release of DB.

Code: 
[Trinity][Performance] Execution of the block HandleTarget took 1006.26ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1028.63ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1040.05ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1040.29ms.
[Trinity][Performance] Execution of the block HandleTarget took 1081.22ms.
[Trinity][Performance] Execution of the block HandleTarget took 1002.90ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1135.05ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1147.28ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1147.56ms.
[Trinity][Performance] Execution of the block HandleTarget took 1385.18ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1553.16ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1564.50ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1564.83ms.
[Trinity][Performance] Execution of the block HandleTarget took 1591.23ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1061.14ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1072.09ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1072.33ms.
[Trinity][Performance] Execution of the block HandleTarget took 1310.66ms.
 
Testing trinity .26 with quest tools .50 right now :)
Done 2 rifts already everything went smooth, no backtracking, seems to be working even better now : D
Also, not Trinity Performance issues so far.

Will let you know again in a couple of hours
 
Oksehode said:
I'm getting a lot of "Execution of the block" error with Trinity .26. Tried both the Beta and official release of DB.

Code: 
[Trinity][Performance] Execution of the block HandleTarget took 1006.26ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1028.63ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1040.05ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1040.29ms.
[Trinity][Performance] Execution of the block HandleTarget took 1081.22ms.
[Trinity][Performance] Execution of the block HandleTarget took 1002.90ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1135.05ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1147.28ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1147.56ms.
[Trinity][Performance] Execution of the block HandleTarget took 1385.18ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1553.16ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1564.50ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1564.83ms.
[Trinity][Performance] Execution of the block HandleTarget took 1591.23ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache.Kiting took 1061.14ms.
[Trinity][Performance] Execution of the block RefreshDiaObjectCache took 1072.09ms.
[Trinity][Performance] Execution of the block HandleTarget.CheckForNewTarget took 1072.33ms.
[Trinity][Performance] Execution of the block HandleTarget took 1310.66ms.
Click to expand...

You still get them from time to time but nowhere near as often as you used to.. they turn up when you encounter multiple elites doing AOE stuff.. obviously the more area's the bot has to "avoid" the harder it gets to find "safe" space and move around.. just watch it a while you'll notice doesn't happen anywhere near as often as it used to and even when it does its still faster then before.
 
gotteshand said:
You still get them from time to time but nowhere near as often as you used to.. they turn up when you encounter multiple elites doing AOE stuff.. obviously the more area's the bot has to "avoid" the harder it gets to find "safe" space and move around.. just watch it a while you'll notice doesn't happen anywhere near as often as it used to and even when it does its still faster then before.
Click to expand...

It's the other way around for me. I almost never had this with Trinity .24 and Quest Tools .45. Now I get this all the time and not only on elite packs.
 
Oksehode said:
It's the other way around for me. I almost never had this with Trinity .24 and Quest Tools .45. Now I get this all the time and not only on elite packs.
Click to expand...

I had it all the time with .24 and .25 I had to turn off all avoidance to make it work on these two version in .26 I can use avoidance just fine.
 
gotteshand said:
Also getting suck a lot of times on this one: 352713 he is exploring it with [Rift Bot] Explore Catacomb @ 30/30/0.2

ngkK7bs.jpg


Stuck points marked down yellow.
Click to expand...

Just had the "same" map again and can confirm running it at Explore Catacomb @ 13/30/0.3 works like a charm. Please update Catacomb settings to 13/30/0.3 :)
 
Status
Not open for further replies.
Back
Top