Yasuko
Member
- Joined
- Oct 28, 2010
- Messages
- 314
Obsolete - This is only a "working" proof of concept
With that being said, here is a release of a currently working example.
This plugin is obsolete
While this plugin works as intended, and works the same way as using a codechunk in a profile, I would recommend people to just add codechunks for class switching when creating profiles. Many gathering profiles are now using it, which is great.. I much rather have a stand alone profile that doesnt rely on plugins. Below is an example.
Then in the area of the profile you are creating, where you want to change jobs, just do an IF statement to compare if you are said job or not, then do
I would recommend using a wait tag after changing class. **This example was taken from Sodimm's daily profiles.
Also would like to note that as with this plugin, it is recommended to start the bot as a DoM/DoW class before switching to a DoL/DoH class in the profile. We have noticed that when starting the bot as DoL/DoH .. it will cause unwanted behavior when trying to change classes later on in the profile. At the time this plugin was created, Kupo was the preferred routine to use, but I can verify that RebornCo will work just fine as well.
I will keep everything else here just in case anyone wants to see it and use as a reference for any projects they may be doing.. But I would no longer recommend using this plugin. It works great still, even on the updated versions of RB.
What does it do..
Classy was designed to add a tag to OrderBot profiles that allows you to select the class within the profile for the bot to use in certain conditions.
I was needing a way to create one profile for all my spiritbinding materials without monitoring the bot and switching classes/profiles manually. This is the solution I came up with.
Note: a clean install may be required. I have tested this on the newer version of RB, as well as the previous version and both seem to work just fine.
What it supports
Uses
This is the idea tag to use within a profile:
Place the If Statement in the Order for each section of your profile that you need to change your job at.
*Note: Group your Order statements together.. example If you are using Three orders to gather different ore, only change the job once at the beginning of the first Order.. once all three orders are done, change the class again to whichever decided.
Here is the full list to copy/paste when needed...
Download
View attachment Classy1_0_8.zip
View attachment Classy-IF_Statments.txt
With that being said, here is a release of a currently working example.
This plugin is obsolete
While this plugin works as intended, and works the same way as using a codechunk in a profile, I would recommend people to just add codechunks for class switching when creating profiles. Many gathering profiles are now using it, which is great.. I much rather have a stand alone profile that doesnt rely on plugins. Below is an example.
Code:
<CodeChunks>
<CodeChunk Name="MIN">
<![CDATA[ ff14bot.Managers.ChatManager.SendChat("/gs change 10");
]]>
</CodeChunk>
</CodeChunks>
Then in the area of the profile you are creating, where you want to change jobs, just do an IF statement to compare if you are said job or not, then do
Code:
<RunCode Name="MIN"/>
I would recommend using a wait tag after changing class. **This example was taken from Sodimm's daily profiles.
Also would like to note that as with this plugin, it is recommended to start the bot as a DoM/DoW class before switching to a DoL/DoH class in the profile. We have noticed that when starting the bot as DoL/DoH .. it will cause unwanted behavior when trying to change classes later on in the profile. At the time this plugin was created, Kupo was the preferred routine to use, but I can verify that RebornCo will work just fine as well.
I will keep everything else here just in case anyone wants to see it and use as a reference for any projects they may be doing.. But I would no longer recommend using this plugin. It works great still, even on the updated versions of RB.
What does it do..
Classy was designed to add a tag to OrderBot profiles that allows you to select the class within the profile for the bot to use in certain conditions.
I was needing a way to create one profile for all my spiritbinding materials without monitoring the bot and switching classes/profiles manually. This is the solution I came up with.
Installation..
Note: a clean install may be required. I have tested this on the newer version of RB, as well as the previous version and both seem to work just fine.
- Unzip Classy to your plugins folder in the root directory of your Rebornbuddy.
- Launch RB and select the plugins tab and enable Classy.
- Once Classy is enabled there will be a box that pops up asking you to select the gearslot that each cl
![gearlist.png](http://s27.postimg.org/3pxro6vlf/gearlist.png)
- Set your bindings then press "Save and Close"
Profile Information..
What it supports
- Classy was written with the idea to mostly gathered all unspoiled nodes each hour, as well as easily change specs for more indepth profiles
- Classes must be used with their Job names; eg: Bard Monk WhiteMage BlackMage Miner Botanist
- At the moment using the class names is not allowed. (it doesnt take long to get anything to 30 while botting, just run some 1-50 profiles)
Uses
This is the idea tag to use within a profile:
Code:
<If Condition="Core.Me.CurrentJob != ClassJobType.Miner">
<ChangeJob Type="Miner" />
</If>
Place the If Statement in the Order for each section of your profile that you need to change your job at.
*Note: Group your Order statements together.. example If you are using Three orders to gather different ore, only change the job once at the beginning of the first Order.. once all three orders are done, change the class again to whichever decided.
Here is the full list to copy/paste when needed...
Code:
<If Condition="Core.Me.CurrentJob != ClassJobType.Miner">
<ChangeJob Type="Miner" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.WhiteMage">
<ChangeJob Type="WhiteMage" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Warrior">
<ChangeJob Type="Warrior" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Summoner">
<ChangeJob Type="Summoner" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Scholar">
<ChangeJob Type="Scholar" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Paladin">
<ChangeJob Type="Paladin" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Ninja">
<ChangeJob Type="Ninja" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Monk">
<ChangeJob Type="Monk" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Dragoon">
<ChangeJob Type="Dragoon" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Bard">
<ChangeJob Type="Bard" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.BlackMage">
<ChangeJob Type="BlackMage" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Botanist">
<ChangeJob Type="Botanist" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Carpenter">
<ChangeJob Type="Carpenter" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Blacksmith">
<ChangeJob Type="Blacksmith" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Armorer">
<ChangeJob Type="Armorer" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Goldsmith">
<ChangeJob Type="Goldsmith" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Leatherworker">
<ChangeJob Type="Leatherworker" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Weaver">
<ChangeJob Type="Weaver" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Alchemist">
<ChangeJob Type="Alchemist" />
</If>
<If Condition="Core.Me.CurrentJob != ClassJobType.Culinarian">
<ChangeJob Type="Culinarian" />
</If>
Download
View attachment Classy1_0_8.zip
View attachment Classy-IF_Statments.txt
Last edited: