Jump to content

Recommended Posts

You are going to need to convert the profiles.  With the WRobot conversion tool I think the outcome is dependant on the type of profile, grinder, gatherer or quester.

If you look at the structure of the XML files grinder and gatherer are easy.  Usually its just a bunch of co-ordinates(Vectors)  to make the path and if its a grinder there will be a section of the XML file that has the NPC ID's for the mobs you want to attack...  For gatherer / grinder i would expect the conversion tool to work fine.

 

Quester is a different story.  all the HB profiles i have seen that are worth a damn are shipped with custom "plugin packages".  The profile actually calls that plugin to change the way the bot works for that quest pulse.  Obviously without the plugin package you are in trouble.  On top of this- it will require a load of 'code sanitation' as the HB profiles have a lot more steps that wrobot doesnt use.  My experience with HB quest conversion was a 1-60 profile.. i had a function Wrobot 1-60 quester with ~1300 steps... the converted HB profile had just over 4000... it was probably easy to just remake the quest profile rather than try to get the converted file to work with all the debug it would take.

 

post a link to the HB profiles you have- maybe we can get some of them working..

 

Link to comment
https://wrobot.eu/forums/topic/4794-profile-crossover/#findComment-22181
Share on other sites

18 minutes ago, eeny said:

You are going to need to convert the profiles.  With the WRobot conversion tool I think the outcome is dependant on the type of profile, grinder, gatherer or quester.

If you look at the structure of the XML files grinder and gatherer are easy.  Usually its just a bunch of co-ordinates(Vectors)  to make the path and if its a grinder there will be a section of the XML file that has the NPC ID's for the mobs you want to attack...  For gatherer / grinder i would expect the conversion tool to work fine.

 

Quester is a different story.  all the HB profiles i have seen that are worth a damn are shipped with custom "plugin packages".  The profile actually calls that plugin to change the way the bot works for that quest pulse.  Obviously without the plugin package you are in trouble.  On top of this- it will require a load of 'code sanitation' as the HB profiles have a lot more steps that wrobot doesnt use.  My experience with HB quest conversion was a 1-60 profile.. i had a function Wrobot 1-60 quester with ~1300 steps... the converted HB profile had just over 4000... it was probably easy to just remake the quest profile rather than try to get the converted file to work with all the debug it would take.

 

post a link to the HB profiles you have- maybe we can get some of them working..

 

Thanks for this it was exactly what i was looking for too.

Link to comment
https://wrobot.eu/forums/topic/4794-profile-crossover/#findComment-22182
Share on other sites

Ok, didn't have much time so i took the easy one first.  Lorlathil grinder

If you look at the XML the layout isnt too bad.  Its a pretty simple profile, the only important thing i can see is the "hotspots"

<Hotspot X="2338.24" Y="6528.67" Z="140.95" />
<Hotspot X="2367.066" Y="6532.46" Z="146.4146" />
<Hotspot X="2418.231" Y="6543.658" Z="149.7744" />
<Hotspot X="2445.596" Y="6543.863" Z="152.2986" />
<Hotspot X="2474.635" Y="6546.638" Z="151.9977" />
<Hotspot X="2504.943" Y="6523.815" Z="156.4359" />
<Hotspot X="2562.169" Y="6491.031" Z="169.0529" />
<Hotspot X="2591.067" Y="6485.735" Z="173.2177" />
<Hotspot X="2612.29" Y="6479.464" Z="173.6712" />
<Hotspot X="2607.982" Y="6399.977" Z="182.7195" />
<Hotspot X="2579.087" Y="6426.262" Z="178.0221" />
<Hotspot X="2568.908" Y="6439.497" Z="170.0796" />
<Hotspot X="2550.416" Y="6442.442" Z="169.0914" />
<Hotspot X="2505.228" Y="6476.29" Z="162.0123" />
<Hotspot X="2439.17" Y="6491.189" Z="157.1621" />
<Hotspot X="2449.913" Y="6428.704" Z="161.6144" />

 

if you notice- they look a lot like Wrobots "vector3's".  so all that needed to be done here is insert these into a blank grinder profile and change "hotspot" or "vector3".  That takes care of the movement- the thing i noticed was the HB profile doesnt identify any targets?  My assumption here is the profile is set to kill anything within 40 yards... so i redirected one of my Val' sharah bots for a min to get some targets.. comes up with this:

 

 

N-Grind--100-110 lorlathil_modified.xml

 

Look a look at the other-  just looking over the XML- see this

    <CustomBehavior File="RunCode" Type="Definition"><![CDATA[
      PluginContainer StudioCompanion = Styx.Plugins.PluginManager.Plugins.FirstOrDefault(p => p.Name == "Studio Companion");      
      
      System.Type studioCompanionHelper = System.AppDomain.CurrentDomain.GetAssemblies().Select(a => a.GetType("Studio60.StudioCompanionHelper", false, false)).FirstOrDefault(a => a != null);
      System.Type petBattleStudioHelper = System.AppDomain.CurrentDomain.GetAssemblies().Select(a => a.GetType("Studio60.PetBattleStudioHelper", false, false)).FirstOrDefault(a => a != null);

 

Noped outa that one...

Link to comment
https://wrobot.eu/forums/topic/4794-profile-crossover/#findComment-22186
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...