Skip to content
This repository has been archived by the owner on Apr 20, 2024. It is now read-only.

Releases: Kyrluckechuck/TFT-Bot

v0.11.15.1

24 Mar 16:52
Compare
Choose a tag to compare

Description

Fixes an issue that could occur if the bot was started and League was not already running, but the bot needs to restart #248

Full Changelog: v0.11.14.20...v0.11.15.1

Release v0.11.14

22 Mar 15:32
9345cf9
Compare
Choose a tag to compare

Description

Updates the bot for Set 11, as well as updates a number of dependencies.

Please note that as Vanguard rolls out to your region, there is a higher likelyhood of bot detection since it has kernel-level access to scanning system resources.

What's Changed

Full Changelog: v0.11.13.19...v0.11.14.20

Release v0.11.13

08 Dec 13:54
f63efb1
Compare
Choose a tag to compare

Notes

While we've had these changes merged into the main branch for a while, doing a release so those who are only utilizing those have a working bot for Set 10!

What's Changed

New Contributors

Full Changelog: v0.11.12.18...v0.11.13.19

Release v0.11.12

13 Nov 02:09
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.11.11.17...v0.11.12.18

Release v0.11.11

29 Jul 15:26
8581e90
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.11.10.16...v0.11.11.17

Release v0.11.10-16

15 Jun 01:56
23f119c
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.11.10.15...v0.11.10.16

Release v0.11.10-15

14 May 19:22
43861d0
Compare
Choose a tag to compare

IMPORTANT NOTICE

Due to an increase in reports of users who have been banned, we have now added the following warning to the top of the README.md:

⚠️ WARNING
Users have been reporting an uptick in bans while utilizing TFT botting software. Users of this repo appear to have all been related to using the executable releases, and as such we are removing the uploaded executables from future releases. It is strongly advised against building them yourselves or using older releases, at this time.
We can not currently verify if there are source-code users being banned as well, and until we hear otherwise, would recommend users stick to running the python/source method only.
Checkpoints / times that users should update their local git copy will be noted with 'releases' in the same consistency as before, just without the executables attached.

The biggest thing to note here is that we have not had reports of users running the source version reporting this behaviour, so it's possible this is limited to the exe releases. As such we will stop releasing those going forward, but will mark checkpoints for users who are running this from source via releases, still (they just won't include executables and you will have to clone the repo).

Of course, we are not responsible for your account standing and if you are suspended/banned because of botting, that is something you are acknowledging by using this and can happen. If you are able, though, please do report such occurrences to help the rest of the community know when these ban waves happen.

What's Changed

Full Changelog: v0.11.9.14...v0.11.10.15

Release v0.11.9

29 Apr 16:33
70d08ce
Compare
Choose a tag to compare

Notes

This is the big (initial) OCR release (though if you've been running from the source it's been available for the last couple weeks).

It is still opt-in and not required, but will (likely) result in a much better experience overall.

Edit: Release executable removed.

What's Changed

Full Changelog: v0.11.8.13...v0.11.9.14

Release v0.11.8.13

18 Apr 03:11
Compare
Choose a tag to compare

Edit: Release executable removed.

What's Changed

Full Changelog: v0.11.7.12...v0.11.8.13

Release v0.11.7.12

15 Apr 04:44
Compare
Choose a tag to compare

Edit: Release executable removed.

What's Changed

Full Changelog: v0.11.6.10...v0.11.7.12