afollow fallback, settings persistence#1
Conversation
cjmanca
commented
May 21, 2025
cjmanca
commented
- Add /afollow as a fallback for when no nav path can be found.
- Option for minimum distance to activate /afollow (so it doesn't try to do it from across the zone)
- Now saves most settings to a config file
- Added several options to the Chase TLO which should respond similarly to AdvPath's TLO, so you can just find/replace AdvPath/afollow to Chase in existing macros.
- Add /afollow as a fallback for when no nav path can be found. - Option for minimum distance to activate /afollow (so it doesn't try to do it from across the zone) - Now saves most settings to a config file - Added several options to the Chase TLO which should respond similarly to AdvPath's TLO, so you can just find/replace AdvPath/afollow to Chase in existing macros.
| end | ||
|
|
||
| local tlomembers = { | ||
| Active = function() return 'bool', true end, |
There was a problem hiding this comment.
should this true be not PAUSED?
There was a problem hiding this comment.
all these extra members that amount to nearly identical information seems like a lot of bloat just to match afollow
There was a problem hiding this comment.
According to the afollow information, "Active" always returns true as long as the plugin is loaded, hence why it's just "true" here.
| local PREFIX = '\aw[\agCHASE\aw] \ay' | ||
| local Settings = { CHASE = '', ROLE = 'none', DISTANCE = 30, STOP_DISTANCE = 10, open_gui = true, MAX_AFOLLOW_DISTANCE = 100 } | ||
|
|
||
| local RUNNING = false |
There was a problem hiding this comment.
the differentiation between running and paused seems odd to me, does it add much to not just have 1 value?
There was a problem hiding this comment.
I agree, I mainly added it for feature parity with afollow. As I was adding/using it, it seemed pointless to have both myself, and I'm not sure why afollow did that either.
There was a problem hiding this comment.
My only thought would be that it was intended to make it easier on macro writers, since pause is usually intended to be temporary. So pause to cast a spell, and after just unpause if paused with no extra logic needed. But they're essentially the same thing.
2 participants
