An Autotyper for ComputerCraft players who use servers that have HTTP Disabled!
To execute CCAutotyper you have several options but the basic structure is as follows:
java -jar ccautotyper.jar [file|url|paste|gui] <location> [-wait <val>] [-inDelay <val>]
If you don't want to use the Windows executable or bash script then you can open the gui using
java -jar ccautotyper.jar gui
and a basic example of command line execution would be
java -jar ccautotyper.jar paste <pastebin_code>
To make life easier for users who may find their code jumbled or have an emergency come up, CCAutotyper started using JNativeHooks to listen for keystrokes, allowing specification of keybindings without being in the the Java-based GUI.
Keybinding | Description |
---|---|
alt+P | Pause autotyping, this assumes you do not type anything yourself before un-pausing. Toggles Pause. |
alt+S | Stops autotyping, this will immediately terminate your autotyping session. |
Parameter | Description |
---|---|
file | The Location provided exists on the local filesystem |
url | The Location provided exists at a web location (must be downloaded) |
paste | The Location provided is the pastebin code leading to the patebin file |
gui | No Location is provided, simply open the GUI |
location | Location to the file you wish to autotype. As a Path (Relative or Absolute) for file; a Web URL for url; or pastebin code for paste |
[-wait] | Optional. Set the number of seconds the program should wait before typing. The parameter should be formatted as -wait t to wait t seconds. [Default: 10] |
[-inDelay] | Optional. Set the number of milliseconds to wait between key strokes. The parameter should be formatted as -inDelay t to wait t milliseconds [Default: 40] |
The Required Parameters must be in the order [file|url|paste|gui] <location>
but the optional parameters can be in any order as long as they are formatted correctly and come after the required parameters. i.e.
java -jar ccautotyper.jar [file|url|paste|gui] <location> [Optional Parameters...]
Contribution is encouraged and welcomed. Pull Requests must be properly formatted and must follow common Java idioms and conventions. If the PR is not satisfactory, not detailed or superfluous/poor/unreadable then it will be rejected promptly.
A proper response will be provided to any and all PRs upon closing or approval. Commit history should be clear and detailed while concise. Documentation is recommended.
All of this applies to wiki contributions as well.
Feel free to contact me personally at matthewcrocco@gmail.com or on github. Correspondence should be limited to comments and technical questions. Issues should be reported appropriately on the GitHub Issues page.
If an issue goes unresolved for an extended period of time then you may attempt personal correspondence.