search

Jaksuhn / Automaton

BSD 3-Clause "New" or "Revised" License
21 stars 26 forks source link

[Bug Report] Auto Fate Grinder Does Not Work #24

Closed Starjadian closed 4 months ago

Starjadian commented 4 months ago

Describe the bug The Auto Fate Grinder Does Not Work

To Reproduce Steps to reproduce the behavior:

  1. Teleport to zone where you want to auto farm the FATE
  2. Enable Auto Fate Grinder
  3. Choose The Fate You Want
  4. Your character mounts up and then jumps in the air to travel
  5. "unable to execute command' pops up and your character just sits there
anti0ch commented 4 months ago

To clarify further on this error:

I think this is the problem: System.InvalidOperationException: Address for FateManager.GetFateById is null.

This arises both during the automated 'Path to Next FATE' option, as well as the 'Pathfind to ' button on the Fate Tracker UI.

The error that shows in the log when the 'Pathfind to ' option is selected is as follows:


15:48:37.016 | ERR | [WindowSystem] Error during Draw(): Fate Tracker##Automaton
    System.InvalidOperationException: Address for FateManager.GetFateById is null. The resolver was either uninitialized or failed to resolve address with signature E8 ?? ?? ?? ?? 48 85 C0 74 2D 80 78 1A 00.
       at Automaton.Features.DateWithDestiny.GetRandomPointInFate(UInt16 fateID) in /home/runner/work/Automaton/Automaton/Automaton/Features/DateWithDestiny.cs:line 371
       at Automaton.UI.FateTrackerUI.Draw() in /home/runner/work/Automaton/Automaton/Automaton/UI/FateTrackerUI.cs:line 62
       at Dalamud.Interface.Windowing.Window.DrawInternal(DalamudConfiguration configuration) in C:\goatsoft\companysecrets\dalamud\\Interface\Windowing\Window.cs:line 346

and the similar error 

15:46:02.344 | ERR | Exception during raise of "Void <InvokeSafely>b__0()"
    System.InvalidOperationException: Address for FateManager.GetFateById is null. The resolver was either uninitialized or failed to resolve address with signature E8 ?? ?? ?? ?? 48 85 C0 74 2D 80 78 1A 00.
       at Automaton.Features.DateWithDestiny.<GetFateMob>b__37_0(IGameObject x) in /home/runner/work/Automaton/Automaton/Automaton/Features/DateWithDestiny.cs:line 335
       at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
       at System.Linq.OrderedEnumerable`1.TryGetFirst(Boolean& found)
       at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable`1 source, Boolean& found)
       at Automaton.Features.DateWithDestiny.GetFateMob() in /home/runner/work/Automaton/Automaton/Automaton/Features/DateWithDestiny.cs:line 334
       at Automaton.Features.DateWithDestiny.OnUpdate(IFramework framework) in /home/runner/work/Automaton/Automaton/Automaton/Features/DateWithDestiny.cs:line 225
       at Dalamud.Utility.EventHandlerExtensions.HandleInvoke(Action act) in C:\goatsoft\companysecrets\dalamud\\Utility\EventHandlerExtensions.cs:line 124

arises constantly when the Fate Tracker is actively trying to run the fates.

Karaha-Baruha commented 4 months ago

This is due to a change in the FFXIV client with the latest patch which has been fixed by Dalamud devs but not pushed to stable yet. If you do /xldev in game and branch switch to staging, it will work for now. When an update is pushed to stable, it will work there as well.

Starjadian commented 4 months ago

This is due to a change in the FFXIV client with the latest patch which has been fixed by Dalamud devs but not pushed to stable yet. If you do /xldev in game and branch switch to staging, it will work for now. When an update is pushed to stable, it will work there as well.

Thank You