Results 1 to 8 of 8

Thread: Macro Settings

Hybrid View

  1. #1
    Player
    Liam_Harper's Avatar
    Join Date
    Feb 2018
    Posts
    3,470
    Character
    Liam Harper
    World
    Zodiark
    Main Class
    White Mage Lv 90
    Quote Originally Posted by Seraphor View Post
    Macro's can't do IF functions, at that point they begin to compute and actually play the game for you, and you could create so many broken macro's with just an IF function alone that would break the game in so many ways. You'd essentially be condoning botting.
    To be fair, I'm not sure how the option to simply auto-quit a macro in the case of a failed action would cause automated gameplay. The macro would only abandon on failure and nothing more. Do you have an example of how this would equal botting?

    Another thing I'd really like to see with macros is the option to have them queueable but only for single action macros. Things such as raise, shirk, asylum on target, mouseover heals and so on. Not allowing macros to queue is perfectly reasonable to prevent automated combat strings, but entirely unnecessary for single QoL buttons.
    (0)

  2. #2
    Player Seraphor's Avatar
    Join Date
    Feb 2018
    Posts
    4,620
    Character
    Seraphor Vhinasch
    World
    Zodiark
    Main Class
    Gunbreaker Lv 100
    Quote Originally Posted by Liam_Harper View Post
    To be fair, I'm not sure how the option to simply auto-quit a macro in the case of a failed action would cause automated gameplay. The macro would only abandon on failure and nothing more. Do you have an example of how this would equal botting?

    Another thing I'd really like to see with macros is the option to have them queueable but only for single action macros. Things such as raise, shirk, asylum on target, mouseover heals and so on. Not allowing macros to queue is perfectly reasonable to prevent automated combat strings, but entirely unnecessary for single QoL buttons.
    If it was specifically to END if something fails, no, that wouldn't be a problem.
    But what does it recognise as failure? With crafting, and talking about lag spikes skipping steps, that's not a clear cut 'failure' that the game could automatically recognise, it's a subjective condition. It's merely a string of actions that didn't execute in the order you wanted them to. Which is why it would require an IF function.
    You would have to design the condition that IF [this] THEN [that]. e.g. IF /ac "Waste not" = false THEN /ac "Waste not"

    But this IF THEN capability could be used for many, many more things than simply adjusting your crafting macro, and could allow you to do all sorts of things you shouldn't be able to do, and blur the line between Macro's and Bots.
    (0)
    Last edited by Seraphor; 10-08-2020 at 01:57 AM.