You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The non indented lines are for ticks, while the indented lines are for subticks.
This way, we can support Mouse and Keyboard subticks, as well as Camera subticks while we are at it.
This also gets rid of the square bracket syntax.
We can also use the existing comparing system for ticks to also check for subticks and maybe add monitoring and control bytes for subtick commands.
And this system is upgradable, the old syntax can be converted into the new one.
The text was updated successfully, but these errors were encountered:
I was made aware that the keyaboard can perform subtick inputs as well, similar to the mouse.
This is only really useful in guiscreens when using the keyboard to switch hotbar positions.
This also fixes the issue of having to hold certain keys for an input to be registered in low tickrates for example.
Increase tasfile version to 2Make TASFile versions strings.New syntax
After thinking about this for a while, I should probably introduce a new syntax for proper subtick handling
Current
Subticks are stored in square brackets. (
[MOUSEMOVED,0,887,626]->[RC,0,1580,658]
etc...). This looks just very messyProposal
The non indented lines are for ticks, while the indented lines are for subticks.
This way, we can support Mouse and Keyboard subticks, as well as Camera subticks while we are at it.
This also gets rid of the square bracket syntax.
We can also use the existing comparing system for ticks to also check for subticks and maybe add monitoring and control bytes for subtick commands.
And this system is upgradable, the old syntax can be converted into the new one.
The text was updated successfully, but these errors were encountered: