Cause this. Weath meant you'll get rightly banned for it. What human would click with the same time interval inbetween for thousands of clicks. There doesn't have to be client modification detected to serve a ban in cases where a chronic pattern that is so unhuman has been analysed - they have enough evidence there. That is why "reflection" methods aren't 100% banproof. Script behaviour is still a good factor in detection.
Yes it will get banned. These are two different aspects of detection.
1. Jagex can (immediately?) flag a player's account if they log in through any modified client
2. If no third-party software is detected, pattern recognition will be next
The guy using the fan mechanism to click alch for him is getting banned because the time between clicks is hardly variable, and this is a developed pattern that can be detected by analysing latency to their servers.
Seems it may be returning State.CHOP as that is your default case in your getState() , instead of returning State.WALK_TO_CHOP at the bank (not detecting condition your player in bank area?) Try putting text logs in your states to debug
log("blah");