Change event state not enabling events
LostLinguine opened this issue · comments
I have 4 events.. 1.) Aura 1
2.) Confirm attack buff. 3.) Aura 2. 4.) Confirm attack buff 2.. when what aura 1 is detected and attack buff is detected it'll disable aura 1 enable arua 2 then disable itself, aura 2 is supposed to enable the second attack buff event but it doesn't for some reason and I concluded that somehow event state can't change an events state when it's already disabled( I enabled the 2nd confirm attack buff and it detects fine but it can't be enabled for some reason and it's very annoying to deal with.
I can't explain how to reproduce it since it's a mystery to me as to why I can't enable an event and have it work normally
I expected it to work as normal( works fine on 2.0.2 but not on 2.3.6) it's supposed to buff an attack but since it's rng I need the clicker to know when a buff lands so it can consistently buff itself in a raid for automation but the confirmation event isn't working like it used to.
-The phone used: tcl ax2 A507DL
-Android 10
-smart clicker version 2.3.6
I am experiencing this as well. I have a set of conditions that enable/disable progressively. It seems iffy whether something is enabled or not, and oftentimes I find that the autoclicker seems to 'hang'. Unfortunately, the debug option is barebones and does not offer any insight on whether something was enabled/disabled. A verbose debug log would be amazing, and could provide information such as:
Event MyStart triggered Condition MyImage at position 100, 258
MyImage clicked at position 100, 258
Event ToggleMe enabled
Event ToggleMe triggered Condition MyPicture at position 382, 2882
MyPicture swiped from position 500, 2882 to 200, 2882
Event ToggleMe2 enabled
Event ToggleMe disabled
and so forth. I think that would provide deeper debug logs for anyone to determine what exactly is going on. Just food for thought, anyway. But this bug is definitely annoying.
Apparently disabling and then enabling events modifies the priority of the events, so that the order explicitly defined in the event list is no longer respected.
That's just a suspicion of mine, I'm not sure how to actually confirm beyond the preliminary tests.
Hi.
I'm currently reworking this feature to make it easier to use, i will take a look at the problem while i'm it.
Sorry for the inconvenience
I'm getting close to something final and functional, a little spoiler for you:
It feels way easier to control the scenario state with this UI
In cases of large scenarios, with many events that disable and enable each other, it is hard to debug and know which event changed the other. It would be nice to have an easy way to list which events affect the state of a specific event.
Hi, I just checked 3.0-beta04 to see if this issue has been addressed from 2.4.2, and it seems that I still can't enable/toggle a disabled event, despite the 'observer'/toggler detecting its condition and working with other actions (click, swipe, etc.).
A little update: I've confirmed that 2.0.2's event toggling is working as intended, so I tried upgrading to 2.3.6 which contains the detection algorithm rework. As expected, the 2.0.2 scenario didn't work 100% out of the box, but after some tweaking with tolerances, it was more or less back up and running. I might have just done something wrong when making the conditions or toggle orders in 3.0-beta04, but as stated above, a more verbose debug log would've really helped.