Yes the code is almost the same but this what you missed out:
go:"[SET_TEST_0_max_70_ge][ACTIVE_TEST_0_on][RAMP_CUSTOM_10_50_60_60_15_8_12_0_50_50_-10_2_0][VALUE_CUSTOM_LINE_bottom_TEST_on]"{"style":"HimCustom"}
bottom:"[HOLD_CUSTOM]"{"style":"HimCustom"}
bottom-out became bottom. (and you can use any other word)
bottom-out can be changed into bottom_out, if you want. (and you can use any other words)
but bottom-out, has a "-" and the trigger [VALUE_CUSTOM_LINE_xxx_TEST_on] does not like "-" as previously said.
So just do not use them. ;)
And I started to use automoveV1, way before learning custom automation. And it has its amount of problem and I never understood why they occur (so no workaround).
I think custom automation v7.0 is the most solid for what I do, and I have workaround for everything I need (except long cutscene).
Ah, I see! I thought I read something in the notes about not using "_" in the custom line name, which is why I avoided it. But I will try that out! Thank you! I am also running into some weird issues with AutoMove right now. Everything I wrote worked fine last night, but now it just doesn't want to work this morning, even though nothing has changed... Man, this stuff can be frustrating!
EDIT: I tried your line and it worked! :D Thanks so much! Guess I am back to using CustomAutomation haha. I also appreciate the tip about remembering to turn off the ACTIVE_TEST. If you don't mind, I might PM you in the future if I run into any other quirky issues. I'm sure you have some answers that can only come from experience!
Last edited: