Dead input... again... oh and prevent autoattacks

[Veiva]

Ok, so it's kind of an extension of my previous topic about dead clicks.

 

This time, it's the action bar. If I rapidly switch the action bar, equip say two weapons and a piece of armor, and activate the 95 prayer for the relevant combat style, sometimes one or more of these actions will not go through--but only if I'm in combat and using just the action bar (I think?). It can't be the interface refreshing, AFAIK, because I can stand at a bank and every command goes through no matter how fast I am. It only happens in combat.

 

edit: It may only happen in combat while at the TD cave. I just spammed abilities and switching on the dummies and it didn't happen once???

 

Is this Runescape's dumb action-per-tick mechanic? Because there's no way in hell I can use void or otherwise optimize my kills at Tormented Demons with these bullshit input issues. Someone claimed they achieved 210+ KPH but as it stands I can't even begin to manage following his advice because the input on RuneScape is so asinine.

 

Also, is there a way to prevent autoattacks when switching weaposn via the action bar? Autoattacks almost upset me as much as the dead key input stuff during combat. There's a reason I'm using abilities!!!

[Veiva]

Ok, I found a fix for this issue but it's impossible to implement with Jagex's draconian-but-'fair' 1 input to 1 action rule.

 

Basically, you can only equip armour (and maybe other actions) until the last 1/6 of a tick (generally I figure this number would be your ping rate). If you perform more actions after this value, the input may get dropped.

 

My idea would be to queue my key presses until the beginning of the next tick. E.g., I press A to switch to Mage action bar, and then press -=X to equip off-hand mage weapon, void mage helm, and use the Torment prayer (my main hand weapon I click on in the inventory before I press -=X, and it is always equipped, thus not subject to this issue). Normally, if I do this too close to the end of a tick, equipping one or more the items will fail. I never had the action bar fail to switch or the prayer, so I think these actions are queued differently by the game, but I digress.

 

If I delay the key presses to the beginning of the next tick, then my input would never fail. So in this imaginary keybind-thing, I would have the keys bound to equip my gear delayed until the next tick. I know when the tick elapses in my case because I always use prayers, and whenever my prayer points go down I know a tick has started.

 

However, there's no point in any of this because as far as I can tell delaying key input is against the rules (after all, that's what basic macros do w/e).

 

In the end, this may be just an issue I have on every computer I've tried (lolchances), but it's bullshit regardless. Jagex should really fix their input system (for example, I know equipping multiple items from the inventory not going through is not just an issue I'm facing).

[Arceus]

I guess that makes sense - I mean Jagex's servers cannot execute the commands toward the end of the same tick if the message to complete those actions can't get there fast enough from your computer. It's disappointing that they don't just carry over to the next tick instead though.

[Hedgehog]

Ok, I found a fix for this issue but it's impossible to implement with Jagex's draconian-but-'fair' 1 input to 1 action rule.

 

Basically, you can only equip armour (and maybe other actions) until the last 1/6 of a tick (generally I figure this number would be your ping rate). If you perform more actions after this value, the input may get dropped.

 

My idea would be to queue my key presses until the beginning of the next tick. E.g., I press A to switch to Mage action bar, and then press -=X to equip off-hand mage weapon, void mage helm, and use the Torment prayer (my main hand weapon I click on in the inventory before I press -=X, and it is always equipped, thus not subject to this issue). Normally, if I do this too close to the end of a tick, equipping one or more the items will fail. I never had the action bar fail to switch or the prayer, so I think these actions are queued differently by the game, but I digress.

 

If I delay the key presses to the beginning of the next tick, then my input would never fail. So in this imaginary keybind-thing, I would have the keys bound to equip my gear delayed until the next tick. I know when the tick elapses in my case because I always use prayers, and whenever my prayer points go down I know a tick has started.

 

However, there's no point in any of this because as far as I can tell delaying key input is against the rules (after all, that's what basic macros do w/e).

 

In the end, this may be just an issue I have on every computer I've tried (lolchances), but it's bullshit regardless. Jagex should really fix their input system (for example, I know equipping multiple items from the inventory not going through is not just an issue I'm facing).

That makes sense, I guess. The input doesn't reach the server until the next tick, then it gets rejected because the timestamp is too far behind the clock. I can't really blame them, though, because it'd be really easy to abuse if they didn't check for that.

 

As far as solutions go, you could set up 2 metronomes at 100 bpm, one synced with the game clock and the other 100ms early, then avoid doing anything between metronome clicks.

[Veiva]

 

Ok, I found a fix for this issue but it's impossible to implement with Jagex's draconian-but-'fair' 1 input to 1 action rule.

 

Basically, you can only equip armour (and maybe other actions) until the last 1/6 of a tick (generally I figure this number would be your ping rate). If you perform more actions after this value, the input may get dropped.

 

My idea would be to queue my key presses until the beginning of the next tick. E.g., I press A to switch to Mage action bar, and then press -=X to equip off-hand mage weapon, void mage helm, and use the Torment prayer (my main hand weapon I click on in the inventory before I press -=X, and it is always equipped, thus not subject to this issue). Normally, if I do this too close to the end of a tick, equipping one or more the items will fail. I never had the action bar fail to switch or the prayer, so I think these actions are queued differently by the game, but I digress.

 

If I delay the key presses to the beginning of the next tick, then my input would never fail. So in this imaginary keybind-thing, I would have the keys bound to equip my gear delayed until the next tick. I know when the tick elapses in my case because I always use prayers, and whenever my prayer points go down I know a tick has started.

 

However, there's no point in any of this because as far as I can tell delaying key input is against the rules (after all, that's what basic macros do w/e).

 

In the end, this may be just an issue I have on every computer I've tried (lolchances), but it's bullshit regardless. Jagex should really fix their input system (for example, I know equipping multiple items from the inventory not going through is not just an issue I'm facing).

That makes sense, I guess. The input doesn't reach the server until the next tick, then it gets rejected because the timestamp is too far behind the clock. I can't really blame them, though, because it'd be really easy to abuse if they didn't check for that.

 

As far as solutions go, you could set up 2 metronomes at 100 bpm, one synced with the game clock and the other 100ms early, then avoid doing anything between metronome clicks.

 

I'm probably going to do something like that. I can accurately count ticks by polling for image difference in the prayer points. Going to probably have to rely on an image or color or something of that sort rather than sound since I like listening to music while killing them... but that's just implementation details.

[Hedgehog]

If you use a cannon, you can use that to track ticks too. I'm not sure if you can bring a cannon there, but I vaguely remember doing it once.

[Veiva]

If you use a cannon, you can use that to track ticks too. I'm not sure if you can bring a cannon there, but I vaguely remember doing it once.

Cannon can't be used at TDs, at least not anymore.