flying?

If you are using EnableFlight, it should do all the death handling.

Edit: and it knows how to return to the Hinterlands.

 

What levels did you do in Dravinian Hinterlands? I tried with a black mage at 57 and a summoner at 58/59 and they died alot and got stuck pretty often. CWH gets me about 500k xp/hour which isn't bad and very rarely gets stuck.

 

I'm trying to get a modified version of ChainIt.cs to to work in CHW and with EXfateBot. For some reason it ignores any chains. Is this due to RB or ExFateBot?

Code:

using System;
using System.Linq;
using System.Windows.Media;
using ff14bot.AClasses;
using ff14bot.BotBases;
using ff14bot.Helpers;
using ff14bot.Managers;

namespace ChainIt
{
    public class ChainIt : BotPlugin
    {
        public override string Author { get { return "Heinzskies"; } }
        public override Version Version { get { return new Version(0, 0, 1); } }
        public override string Name { get { return "ChainIt"; } }
        public override string Description { get { return "Allow you to do chain quest without going back."; } }

        public override bool WantButton
        {
            get { return false; }
        }

        public new bool Equals(BotPlugin other)
        {
            throw new NotImplementedException();
        }

        bool _lastFateChainActive = false;
        FateIdleAction _userAction = FateIdleAction.Nothing;

        public override void OnPulse()
        {
              uint[] chain1 = { 791, 792 };
              handleFateschain(chain1);
              uint[] chain2 = { 809, 810 };
              handleFateschain(chain2);
			/* uint[] chain3 = { 811, 812 };
              handleFateschain(chain3); */
         }

        public void handleFateschain(uint[] fatesChain)
        {


            foreach (var fateChain in from fateChain in fatesChain let fateSearch = FateManager.ActiveFates.Count(fate => fate.Id == fateChain) where fateSearch != 0 select fateChain)
            {
                ActiveChain();
                if (fatesChain.Last() == fateChain)
                {
                    _lastFateChainActive = true;
                }
                    
                FatebotSettings.Instance.ThisFateOnly = FateManager.GetFateById(fateChain).Name;
            }


            if (FateManager.ActiveFates.Count(fate => fate.Id == fatesChain.Last()) == 0 && _lastFateChainActive)
            {
                _lastFateChainActive = false;
                FatebotSettings.Instance.ThisFateOnly = "";
                FatebotSettings.Instance.IdleAction = _userAction;
            }
        }

        private void ActiveChain()
        {
            if (FatebotSettings.Instance.IdleAction != FateIdleAction.Nothing)
            {
                _userAction = FatebotSettings.Instance.IdleAction;
            }
            FatebotSettings.Instance.IdleAction = FateIdleAction.Nothing;
        }

        public override void OnInitialize()
        {
        }

        public override void OnShutdown()
        {
            throw new NotImplementedException();
        }

        public override void OnEnabled()
        {
            Logging.Write(Colors.SkyBlue, "[ChainIt] v" + Version + " Enabled");
        }

        public override void OnDisabled()
        {
        }
    }
}

 

It would be pretty complicated to get this to work with ExFatebot how it currently is.

2 options.

1. Make ExFatebot use the original fatebot settings (it isn't actually much of a change) and this would make it also compatible with Destiny.
2. Implement a pub/sub plugin to hook both projects to so they can talk to each other (very complicated).

 

If we look at what is easiest. What will be the consequences if we going for the first option? Do we loose any core functionality? Are we not already using the RB fate bot settings today, but with a different re-naming FatebotSettings.json - > (ExFateBotSettings.json).

This is the best plugin Fatebot and surpasses everything when it comes to leveling 50-60.

Thanks in advanced ExMatt, you are truly great on what you are doing.

 

I was going to be using more functionality, which is why I used a new settings type, but in the end, I didn't add any functionality, so going back to the other settings would likely be quick and easy. I am already not really working on the project and likely won't get back to it till after Mastahg releases the new fatebot he had been working on.

 

If you are able to push out such an update on your SVN I would be grateful.

Then I promise to create a ChainIt.cs file that will work in the CHW and share it on the forum for others to use in combination with ExFateBot.

This will be the fastest way to level between 50 -->60.

 

Someone should just make chain it have a ui to add simple id <-> id connections and possibly special hotspot associated. It can be done I just dont' like building UI stuff.

 

Made an update, should be using original fatebot settings now. If someone could test with destiny also that would be interesting to know.

 

Thanks alot ExMatt. It's great to have easy access to the settings gui again.

For now I'm testing the chain routine now. Some have worked and some have not. It can be an error from my side and the way i have created different independent chains. I will continue to test it to make sure it's working properly. So far i discovered three independent chains, and I will continue to add if i find more.

Ps. Are you referring to the paid version of Destiny or is there another version on this forum i might be able to test for you?

 

The biggest issue i see this creating is that I think all of the chains are boss fates, so that would be bad for classes like nin etc that likely can't solo them. Either way, sounds good.

 

I leveling a monk as we speak and can solo all the bosses @+56 with my Chocobo healing and slightly modified Ultima for more defensive spells. However, this not possible in the early to mid 50's. The chain can be activated to get extra xp when you are getting above this threshold or when the Zone is heavily populated with other fate farmers.

 

Tested with Destiny and it stays in the same zone.

 

I just want to clarify for anyone that the current paid version of Destiny is locked to being used with FateBot only. If enough people REALLY want it, I could make it compatible with ExFateBot. What I worry about is the unknowns that will happen by making it compatible because all of the testing I have done has been with strictly FateBot itself. The other thing I don't like is opening it up to a BotBase which has already been left behind since ExMatt has stated that he's not really working on the project anymore.

 

Sadly chainIt does not work.

It does what it is supposed to do and identify and isolate "thisFateOnly" part of a chain, but still engage other fates in or out of combat and ignores the value.

 

Thanks blade. I can probably fix that. I think i didn't put in that part of the function because i wasn't using the UI and all fates that required that value was usually for animus stuff and i assume they would just use fate bot. I will add that back in for you when I get the chance.

Edit: Try again. I dont' have time to test anything, but this should work assuming chain it is setting the fate name before it tries to select the next fate.

 

That sounds very interesting

Let me test it out and report back.


Edit: Thanks ExMatt, It's working perfect. It will identify and isolate the fate chain and ignore any other fate nearby or along the way.

 

Perhaps this is a buyer beware situation? Not sure what the demand is like, but I'd certainly play around with this. Mostly cause i love the patrol on destiny.

 

Anyone get flight to work after the patch?

 

https://www.thebuddyforum.com/rebornbuddy-forum/rebornbuddy-profiles/231198-exbuddy-offsets.html