air
Member
- Joined
- Feb 24, 2015
- Messages
- 146
1. Reading ban reports, i found many correlations to Kicks profile levelling in Hyjal, then people got ban.
2. So i start search log from guy in this thread https://www.thebuddyforum.com/honorbuddy-forum/ban-section-ban-reports/216874-72h-suspension-unapproved-third-party-software-email-inside.html
This string is from log file(points defined also in [Fly][N - Quest] Hyjal 80-82 [Kick].xml):
Flying to Type: QuestTurnIn from <5655.492, -2907.27, 1611.291>
Moving to kill poi from <5657.066, -2818.185, 1524.303>
Flying to Type: QuestTurnIn from <5608.841, -2885.874, 1527.077>
Flying to Type: QuestTurnIn from <5660.605, -2823.647, 1524.528>
Flying to 'Turnin Quest' (<5705.028, -3150.027, 1593.088>)
Goal: Moving to <5704.213, -3139.344, 1588.215> [Ref: "MoveTo" @line 765]
Flying to 'Nordrassil doorway' (<5581.133, -3609.819, 1570.599>)
Flying to 'Wolf's Run' (<5641.554, -2445.48, 1527.105>)
Flying to 'get 36 Twilight Supplies' (<5552.961, -2663.447, 1489.709>)
3. So, if on server side we can log where, in which points player dismounted(for example) or stopped, we can track player movements.
Then, if "player" visit this predefined points in some time frame, with 99% confidence we can determine it is a bot. Because no human can visit same points
4. Conclusion: bot need randomization in movements between hardcoded points. this can be done by adding some small random +- correction to coordinates.
2. So i start search log from guy in this thread https://www.thebuddyforum.com/honorbuddy-forum/ban-section-ban-reports/216874-72h-suspension-unapproved-third-party-software-email-inside.html
This string is from log file(points defined also in [Fly][N - Quest] Hyjal 80-82 [Kick].xml):
Flying to Type: QuestTurnIn from <5655.492, -2907.27, 1611.291>
Moving to kill poi from <5657.066, -2818.185, 1524.303>
Flying to Type: QuestTurnIn from <5608.841, -2885.874, 1527.077>
Flying to Type: QuestTurnIn from <5660.605, -2823.647, 1524.528>
Flying to 'Turnin Quest' (<5705.028, -3150.027, 1593.088>)
Goal: Moving to <5704.213, -3139.344, 1588.215> [Ref: "MoveTo" @line 765]
Flying to 'Nordrassil doorway' (<5581.133, -3609.819, 1570.599>)
Flying to 'Wolf's Run' (<5641.554, -2445.48, 1527.105>)
Flying to 'get 36 Twilight Supplies' (<5552.961, -2663.447, 1489.709>)
3. So, if on server side we can log where, in which points player dismounted(for example) or stopped, we can track player movements.
Then, if "player" visit this predefined points in some time frame, with 99% confidence we can determine it is a bot. Because no human can visit same points

4. Conclusion: bot need randomization in movements between hardcoded points. this can be done by adding some small random +- correction to coordinates.