[Destiny V2] FateBot Automation

[Wheredidigo]

I'm tired of Mastahg saying everything anyone else does is bad. I've removed my stuff from the forums and will be posting them elsewhere online.

 

[Endus]

Great job. That'll definitely come in handy for 50-60 and leveling up the 3 new Jobs in the expansion.

 

[y2krazy]

Great job. That'll definitely come in handy for 50-60 and leveling up the 3 new Jobs in the expansion.

^ This! Thanks for the update!

 

[phaedrus]

What is the best zone settings?

 

[Wheredidigo]

Thanks a bunch, can I confirm if what it will do is similar to the original destiny, and will swap around to keep levels equal? Personally I prefer maxing one at a time, but thats easily doable here by setting all but one to zero.
It changed to my paladin set, then kept trying to change to gladiator.

Yeah looks like same problem for dragon. It spams this...

19:59:29.587 N] [Destiny V2.0.0.0] Trying to change job to Lancer

I've updated the plugin and it should fix that issue. In the future, please attach an entire log file instead of just a snippet.

 

[matt84]

where was this 2 weeks ago like, i literally just leveled up 5 jobs from 1 - 50

 

[10thVongola]

Hey, Thanks for this, so far so good. Haven't ran into any problems as of yet, appreciate it. Just curious to if there is a possibility of and SVN releasing soon? Thanks again!

 

[Kurae]

Hello, nice work, i've used it all night and it works flawlessy... just one request: is possible to add an auto decline party invite feature?

 

[Wheredidigo]

Hey, Thanks for this, so far so good. Haven't ran into any problems as of yet, appreciate it. Just curious to if there is a possibility of and SVN releasing soon? Thanks again!

Probably not. I like being able to see how many download's of my stuff I've gotten. And while I'm not sure if the "views" are 100% accurate, it at least gives me some idea.

Hello, nice work, i've used it all night and it works flawlessy... just one request: is possible to add an auto decline party invite feature?

First, I'm pretty sure that there isn't anything in the RB API to be able to do that yet. I'm not 100% positive, but I can't think of anything off the top of my head that would do it. Second, that's kind of outside the scope of this Plugin. This plugin is all about making FateBot work the way we want it to. Lastly, if you just type /busy in your chat, it'll change your status and people won't be able to send you party invite's. They also won't be able to send you /tell's.

Thanks, for the feedback guys. I'm glad it's working well for you.

 

[altnob]

please explain gear set number more. i don't get what it's for.

 

[Wheredidigo]

please explain gear set number more. i don't get what it's for.

GearSet's correlate to you in-game GearSets. For example, let's say I am a level 20 Conjurer. I can equip all my level 20 Conjurer gear, and then save it to a GearSet. If it's my first GearSet, it will save it to GearSet 1. Lets say I then change my equipped gear and now I'm a level 30 Ninja. I can save that gear to GearSet2. Now, all I have to do is click on the correct GearSet and it will change my class/equip that set of gear.

With Destiny, if you set a GearSet for a class to 0, then the plugin won't try to level that class.

If you just don't know what a GearSet is at all, then please click this link: What is a Gear Set?

 

[The Red Terror]

Would it be possible for a Level 11-15 fate change? Also will it bring up a prompt screen asking about confirming which routine we'd like to use when it changes classes. Or does that preferred routine change that?

 

[Wheredidigo]

This error is thrown with a fresh install of RB and Destiny.

[01:02:34.863 D] Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: job
   at DestinyPlugin.Extensions.BaseClass(ClassJobType job) in c:\Reborn\Plugins\Destiny\Extensions.cs:line 102
   at DestinyPlugin.Destiny.<ChangeJob>d__13.MoveNext() in c:\Reborn\Plugins\Destiny\Destiny.cs:line 207
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at TreeSharp.ActionRunCoroutine....()
   --- End of inner exception stack trace ---
   at Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
   at Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
   at Buddy.Coroutines.Coroutine.Resume()
   at TreeSharp.ActionRunCoroutine.Run(Object context)
   at TreeSharp.Action.RunAction(Object context)
   at TreeSharp.Action.<Execute>d__0.MoveNext()
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.Decorator.<Execute>d__0.MoveNext()
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.<Execute>d__0.MoveNext()
   at TreeSharp.Composite.Tick(Object context)
   at ff14bot.Behavior.HookExecutor.Run(Object context)
   at TreeSharp.Action.RunAction(Object context)
   at TreeSharp.Action.<Execute>d__0.MoveNext()
   at TreeSharp.Composite.Tick(Object context)
   at TreeSharp.PrioritySelector.<Execute>d__0.MoveNext()
   at TreeSharp.Composite.Tick(Object context)
   at ff14bot.TreeRoot.() --> System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: job
   at DestinyPlugin.Extensions.BaseClass(ClassJobType job) in c:\Reborn\Plugins\Destiny\Extensions.cs:line 102
   at DestinyPlugin.Destiny.<ChangeJob>d__13.MoveNext() in c:\Reborn\Plugins\Destiny\Destiny.cs:line 207
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at TreeSharp.ActionRunCoroutine....()

Not posting a log since the fix is to simply go to Plugins > Destiny > Settings > then create Gear Sets in-game and match the Gear Set number with the numbers in the Class/Job Gear Set Selection of the plugin. With a fresh install all the Gear Sets in the plugin are set to 0 which is whats causing this error.

May want to add a small setup tutorial to the first post since its not super obvious when first installing this plugin that you 100% must create Gear Sets ingame.

You could also add a message box popup or just a chat line in RB telling the user to first setup the Class/Job Gear Set Selection instead of the plugin just shutting down / spitting errors.


After setting up the gear sets, this plugin worked very very well. I thought i installed it wrong or maybe this version of Destiny was packed wrong because of the errors on a fresh install. Just wanted to give new users a heads up that if you are getting an error, its a very simple fix.


EDIT:



Just read that from your previous post. If all classes are set to 0 (fresh install) the plugin throws errors instead of telling the user to set up gear sets. Simple fix, thanks for the awesome plugin!

So, let me make this clear. You ALWAYS need to post a full log. If you'll notice back on the first page, there used to be 2 more posts from people reporting bugs. They didn't provide logs. So what happens is all I have to do is report the post with a message of "Bug reported with no log attached", and a forum mod will go in an delete the posts. Expect that to happen to your post in the next few days unless you edit it to provide a log.

Now that that's out of the way, I do appreciate the report of the bug, but you are incorrect in your assessment of what is causing this(and if you posted a full log it would probably show this in the log).

The problem is in the Extensions.cs class at line 102. Line 102 is the last portion of a switch statement on what your current class/job is. Here is the code for the method that is throwing the error:

public static ClassJobType BaseClass(this ClassJobType job)
{
	switch (job)
	{
		case ClassJobType.Paladin:
		case ClassJobType.Gladiator:
			return ClassJobType.Gladiator;
		case ClassJobType.Monk:
		case ClassJobType.Pugilist:
			return ClassJobType.Pugilist;
		case ClassJobType.Warrior:
		case ClassJobType.Marauder:
			return ClassJobType.Marauder;
		case ClassJobType.Dragoon:
		case ClassJobType.Lancer:
			return ClassJobType.Lancer;
		case ClassJobType.Bard:
		case ClassJobType.Archer:
			return ClassJobType.Archer;
		case ClassJobType.WhiteMage:
		case ClassJobType.Conjurer:
			return ClassJobType.Conjurer;
		case ClassJobType.BlackMage:
		case ClassJobType.Thaumaturge:
			return ClassJobType.Thaumaturge;
		case ClassJobType.Carpenter:
			return ClassJobType.Carpenter;
		case ClassJobType.Blacksmith:
			return ClassJobType.Blacksmith;
		case ClassJobType.Armorer:
			return ClassJobType.Armorer;
		case ClassJobType.Goldsmith:
			return ClassJobType.Goldsmith;
		case ClassJobType.Leatherworker:
			return ClassJobType.Leatherworker;
		case ClassJobType.Weaver:
			return ClassJobType.Weaver;
		case ClassJobType.Alchemist:
			return ClassJobType.Alchemist;
		case ClassJobType.Culinarian:
			return ClassJobType.Culinarian;
		case ClassJobType.Miner:
			return ClassJobType.Miner;
		case ClassJobType.Botanist:
			return ClassJobType.Botanist;
		case ClassJobType.Fisher:
			return ClassJobType.Fisher;
		case ClassJobType.Arcanist:
		case ClassJobType.Summoner:
		case ClassJobType.Scholar:
			return ClassJobType.Arcanist;
		case ClassJobType.Rogue:
		case ClassJobType.Ninja:
			return ClassJobType.Rogue;
		default:
			[B][SIZE=4]throw new ArgumentOutOfRangeException("job");[/SIZE][/B]
	}
}

What this tells me is that when you were running this plugin, you were not in a CombatClass at some point, because if you were, then it would have returned the proper class and you wouldn't have gotten the exception. The error is easily fixed(and I will upload a new version of the plugin with the fix) by just returning the "job" parameter that was passed in as the default instead of throwing an exception.

It is an easy fix and it's one I will get done soonish, but let me re-iterate...please, please, please ALWAYS attach a full log when reporting bugs.

 

[Wheredidigo]

Would it be possible for a Level 11-15 fate change?

Yes, it's possible to add a Level 11-15 fate change, but tbh I'm not sure when I'll get around to it.

Also will it bring up a prompt screen asking about confirming which routine we'd like to use when it changes classes. Or does that preferred routine change that?

Setting the preferred routine "should" make it so the prompt screen doesn't show up anymore. I honestly haven't really done much testing on it, so if you set your routine and are still getting that prompt, please report it as a bug.(And as always, attach a full log along with it please.)

 

[Valpsjuk]

Sweet... this will surely come in handy when it's time to start levelling up my "alt" classes

 

[The Red Terror]

Yes, it's possible to add a Level 11-15 fate change, but tbh I'm not sure when I'll get around to it.


Setting the preferred routine "should" make it so the prompt screen doesn't show up anymore. I honestly haven't really done much testing on it, so if you set your routine and are still getting that prompt, please report it as a bug.(And as always, attach a full log along with it please.)

No worries. Just something that people may want later on is all.

So far I haven't gotten any prompts and this is an amazing plug-in that both you of created.

The only "issue" I received was when I already had my home point set in Coerthas Highlands and I started the bot in a different zone. The bot ported to Coerthas and then decided to idle at the aetheryte after it came back in game as "Already set as home point". I didn't get a chance to capture the log, but if you want me to recreate it just let me know.

 

[Cloud30000]

I modified the code to break out levels 1-9 and levels 10-14, as well as returning 'job' for the default case; I couldn't figure out how to resize the window, so the bottom of the FateBot Settings border is slightly cut off. Hopefully, you can use it to save a little leg work when you update your code.

View attachment DestinyV2 - fate levels 1-10 &10-15.zip

 

[throne]

Can I use this and patrol at the same time?

 

[Wheredidigo]

I modified the code to break out levels 1-9 and levels 10-14, as well as returning 'job' for the default case; I couldn't figure out how to resize the window, so the bottom of the FateBot Settings border is slightly cut off. Hopefully, you can use it to save a little leg work when you update your code.

View attachment 180366

You should really join the Skype Dev Chat we have going for RB.

Can I use this and patrol at the same time?

I honestly haven't tried using this with Patrol, so I don't know. I don't see why you wouldn't be able to, but since I haven't tested it, I don't want to give you a definitive answer. You are welcome to test it out and I'd love to have your feedback on how well they work together. Patrol is something that I'll be looking to fold into this Plugin at some point in the future. Just an FYI.

 

[Valpsjuk]

You should really join the Skype Dev Chat we have going for RB.


I honestly haven't tried using this with Patrol, so I don't know. I don't see why you wouldn't be able to, but since I haven't tested it, I don't want to give you a definitive answer. You are welcome to test it out and I'd love to have your feedback on how well they work together. Patrol is something that I'll be looking to fold into this Plugin at some point in the future. Just an FYI.

It worked fine with Patrol