The Humanizer sits between your scripts and the game. An order a script issues is queued and released after a delay drawn from a model of human order timing. Your own clicks pass through untouched.
Timing. The delay is sampled, never fixed. The model was learned from the order streams of 1,491 recorded matches; each delay depends on the gap before the previous order and on whether the last orders came in a quick run. The speed setting shifts the whole distribution:
- deliberate ×0.85
- corpus ×1.00, the default
- brisk ×1.35
- fast ×1.70
- instant ×2.60, faster than anyone in the data, and marked so in the menu
Click scatter. A point order lands a little off its exact target, 18 units at base.
Part B, off by default, moves the cursor to each queued click along a path learned the same way, and hands it back to your mouse once the queue is empty. It can draw that path, the link back to your mouse and a cursor speed graph.
Late orders. An order held more than 1000 ms past its own delay is dropped instead of fired late. The margin is a slider.
On screen there is one status line at the bottom centre: the speed setting, orders pending and the current delay.
Menu: Humanizer › General, Behavior, Part B.
The delay-model picker lists the models in the install instead of the game folder, where it found none.
还没有评价。
该作者的其他作品
ground
作者 hunnycGround height and high-ground level at any point of the dota map.
"requires": { "ground": "^1.0" }local ground = require("lib/ground")Beta Tester Config
作者 hunnycBeta 0.10.54 preset: combo on F, last hit on B, every other bind moved off dota's own keys, hp cards and minimap marks on.
lane_geom
作者 hunnycA lane as a polyline: the point on it nearest to a creep, the heading there, and a walk of N units along it.
"requires": { "lane_geom": "^1.0" }local lane_geom = require("lib/lane_geom")