Shajirr
New member
Current action:
- has no control over the screenshot name or where its saved. Has no way to get this data to use in the macro later.
- displays screenshot-taking system UI, which can interfere with and break the script if it need to use UI interactions
- being able to specify save path + file name of the screenshot
- does not display any interface while taking the screenshot, so will not interfere with any scripts using UI interaction