@phoenixI had notified the dev (not through the proper channels though unfortunately) and am hoping this issue was fixed for 2.0. I'm about to find out.
