Originally Posted by
jstemper
Why not just pm a reflection dev and ask them? For WalkToTileMM it makes more sense to have it accurately click a tile on the minimap. Just look at how it is used in the include... Blindwalk functions paired with WindPath (adds randomness). And WalkStraightPathMM (emphasis on StraightPath). Now for WalkToTileMS I do agree with you, it could use some randomness. But imo you are better off adding randomness via the TileToMS parameter offsets, instead of reflect.mouse.move. Nothing is stopping anyone from editing the include to their liking/preferences though...
I have no idea what you just said.
The point here is that walkToTileMS/walkToTileMM do not have a problem with clicking tiles. They have a problem in that the Tile is being clicked on at the same MOUSE COORDS.
Example of clicking a tile without randomization within the walkToTileMS function:
Code:
ClickTileMousePointsArray[
{X = 288, Y = 174},
{X = 288, Y = 174},
{X = 288, Y = 174},
{X = 288, Y = 174},
{X = 288, Y = 174},
{X = 288, Y = 174},
{X = 288, Y = 174},
{X = 288, Y = 174},
{X = 288, Y = 174},
{X = 288, Y = 174}]
Example of clicking a tile with randomization within the walkToTileMS function:
Code:
ClickTileMousePointsArray[
{X = 263, Y = 168},
{X = 295, Y = 175},
{X = 292, Y = 175},
{X = 287, Y = 175},
{X = 288, Y = 178},
{X = 289, Y = 169},
{X = 286, Y = 177},
{X = 283, Y = 172},
{X = 289, Y = 176},
{X = 287, Y = 171},
{X = 284, Y = 171},
Both instances, the tile is 100% accurately clicked. However, one instance (the first one) is clicking the tile with the same mouse coordinates each time. That's a big flag if you're simply using walkToTileMS/walkToTileMM