Skip to content

Importing macros with the Focused Touch combo treats the Focused Touch as invalid #64

@rincebrain

Description

@rincebrain

Required Information

Class: GSM
Level: 90
Craftsmanship: 4021
Control: 3987
CP: 601
Recipe Name: Rutilated Quartz
Recipe Level: 90
Solver Seed: 93295

Expected Behaviour

Processing the combo as valid and feeding all the steps from it as input without needing to enable non-guaranteed actions

Actual Behaviour

When you watch the solver iterate, you can see it starts with the Focused Touch after the Observe deleted if you have non-guaranteed actions disabled, resulting in something like:

/ac "Observe" <wait.3>
/ac "Focused Touch" <wait.3>
/ac "Delicate Synthesis" <wait.3>
/ac "Observe" <wait.3>
/ac "Focused Touch" <wait.3>

turning into

/ac "Observe" <wait.3>
/ac "Delicate Synthesis" <wait.3>
/ac "Observe" <wait.3>

Which, naturally, rapidly gets thrown out as superfluous.

Steps To Reproduce

Just set up your 90 job, hit Guaranteed (By Level), make sure that Focused Touch isn't selected and Focused Touch combo is, then hit import macro and plug in something like the above, and observe that the solver throws out the Focused Touch, and then wildly departs from what it had before, as a result. (Which can be useful for trying a very different approach, but...)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions