Astrologian 5.0 Discussion

[Seraphor]

I also hate draw and play being two separate buttons so much that i made a macro to unify them again
/ac "play"
/wait 0.01
/ac "draw"
/macroicon "draw"

It's functionally the same as it used to be this way. If you try and draw another card while you have one drawn with this macro, it will use the drawn card first before trying to draw another.

Wait macros only work in integers and rounds up, so you're waiting a whole second, not 0.01s

We actually have the same number of buttons for cards, you can just put Play where you used to have Spread, and think of it as automatically Spreading your card.

[Averax]

Wait macros only work in integers and rounds up, so you're waiting a whole second, not 0.01s

We actually have the same number of buttons for cards, you can just put Play where you used to have Spread, and think of it as automatically Spreading your card.

I've tested this, and no, it's as snappy as if i were drawing like normal. First i tested it with a 0.5. and then i went down to 0.01 and there was a noticeable difference.

It could be rounding up to 0.1. But wait macros can do decimal points. People need to be able to macro things to work with the GCD after all.

[Seraphor]

I've tested this, and no, it's as snappy as if i were drawing like normal. First i tested it with a 0.5. and then i went down to 0.01 and there was a noticeable difference.

It could be rounding up to 0.1. But wait macros can do decimal points. People need to be able to macro things to work with the GCD after all.

No, this is a well known limitation of Macros. They can't do decimals, that's precisely why you can't string GCDs together, because you can't 'Wait 2.5s, it's 3s minimum.

It could be that your 0.01 doesn't round up, but registers as 0 because it only takes the first decimal place and rounds up.

https://www.youtube.com/watch?v=qshNKeDENlk

[Averax]

No, this is a well known limitation of Macros. They can't do decimals, that's precisely why you can't string GCDs together, because you can't 'Wait 2.5s, it's 3s minimum.

It could be that your 0.01 doesn't round up, but registers as 0 because it only takes the first decimal place and rounds up.

https://www.youtube.com/watch?v=qshNKeDENlk

Either way, i tried not having /wait in the macro (i don't know if that would be the same as having a /wait 0 or not) , but it wouldn't work without it, and it's definitely not taking a whole second.

Edit: logged in and changed my macro to a flat 0, so yeah it was rounding down to 0. Anyway, is great macro, would recommend for ASTs who miss the draw/play on the same button.

Edit 2: i tried removing the /wait from the macro all together for giggles and it's working now??? and it wasn't yesterday??? okay, game...