jaksuhn / automaton

Pandora's Box

automaton's Issues

[Feature Request] Parameters for autofollow command

In dungeons, a close autofollow distance is better to avoid getting party members stuck in terrain, but in combat, a longer distance (or disabling autofollow) is better to allow party members to evade AoEs using Bossmod's AI.

To facilitate toggling this, the following parameter functionality for the "autofollow" partychannel command would be helpful:

autofollow [number] -> Enables autofollow with current character as a target and sets follow distance for followers to [number] yalms
autofollow off -> Disables autofollow (can be re-enabled with "autofollow" without parameters as per current functionality)

Revert Update

Is there any way to revert the update to get the Retainer listings back?
TY

[Feature Request] Teleport to capital if you are not in the same server

Hello, it's possible to add option, when you click to chatbox to teleport in capital if you are not in the same server on announce for faloop hunt to switch server or if you are in the same server you got tp to location when click in the location like sonar option please ?

[Feature Request] Auto-Follow: Multi-seater mount support

Hi, thanks for this plugin! I use Automaton's Auto-Follow for leveling and controlling a light party composed of alt characters on separate accounts. It would help with transportation while leveling (and immersion) if they could automatically join me in my Regalia Type-G mount.

I propose to add an "auto-mount" option. If enabled, if a party member or the follow target deploys a multi-seater mount, the follower automatically moves toward them and rides pillion (/ridepillion ) By writing "automount" in party chat, the mount-owning party member could be commanded to deploy their mount.

Currently, this must be done manually by switching off autofollow (because it automatically dismounts the follower for some reason), deploying the mount, switching character, right-clicking, selecting "Ride pillion", and switching character again.

[Feature Request] Add a way to display the price changes for the "Auto Adjust Retainer Listings" option

Is your feature request related to a problem? Please describe.
Unless you set a limit for Max Price Reduction, you have to pay particularly close attention to the amount that a listing is reduced by.

Describe the solution you'd like
A basic (temporary) window that displays the name of the item and the amount that it has been reduced by. e.g:

-200gil Alchemist
-1gil Thavnairian Onion
-0gil Shale Brown Dye

Having the value in front might make it easier to see unwanted changes at a glance without additional formatting.

Describe alternatives you've considered
Existing alternative would be to set a reduction limit. Flat reduction limits aren't ideal imo since expensive single items like Thav Onions can fluctuate in pricing by several thousands while a 500 gil decrease for something like alchemist would be detrimental. Until percentage-based limiters for price reduction exist, the suggested display window would be a nice QoL addition.

[Feature Request] Sub-Option for Auto Leave on Duty

I would love a "Leave only after all the loot has been distributed" option for auto leave on duty end.

[Feature Request] Date with Destiny failure avoidance checks

When left to run for a time, the Date with Destiny function (the FATE bot) will eventually get stuck in one of three ways:

1. The player is stuck in the environment on the way to the next FATE because of deficiencies in vnavmesh pathfinding.
2. The player is pushed out of the FATE area by evading AOEs and the FATE stops progressing.
3. The player does not move to the next FATE because vnavmesh has ceased to function (this appears to happen after half a day or so). If one attempts to unload vnavmesh, the game hangs.

To address failure modes 1 and 2, I suggest a function that regularly checks if, as long as an an eligible FATE exists, the player is in it or is moving while underway to it. If the answer is no, the vnavmesh navigation command should be reissued, and if that does not fix the problem, another eligible FATE should be targeted, and the problematic FATE blacklisted after a few attempts.