Historical project

Tinkr

Tinkr was a macOS Lua unlocker for bots and rotations, but we could not verify that it still runs. Its former domain now shows NilName content.

macOSHistorical support

Historical price / status

Historical: EUR 20/month

View historical source

Historical discussion; current operation unverified

Historical records; offline reportsEdited by M1Sources checked

Overview

Tinkr provided Lua access on macOS for third-party WoW bots and combat rotations. [2][3][1][9][10]

More about this product

The surviving references place Tinkr in the historical category for now: the directory marks it offline, users reported its end in January 2026, and its former domain shows NilName content. A working current release remains unverified. [1][9][10]

Before you buy

  • The former Tinkr domain now promotes NilName, while the surviving integration and reseller pages leave the status of Tinkr itself unresolved.
  • Archived code and old sales pages can explain how Tinkr worked, but they cannot tell you whether anyone still operates the service.

Pricing and access

Historical Tinkr monthly cost

EUR 20 plus EUR 10 additional session (user-reported)Monthly, as described in July 2025 review

Historical Baneto/Tinkr setup

Required: Tinkr required macOS, with bots and profiles costing extra.

More on Historical Tinkr monthly cost

This is a historical price and leaves current license sales unverified.

[4]

A user review from July 2025 quotes EUR 20 plus EUR 10 per additional session, but that historical price is not a current provider offer.

Requirements

Scroll sideways to see all columns.

Game branchSystem / regionCoverage and limits
Classic (historical)Historical integrationmacOSNot verifiedOrca announced its return with Tinkr in a June 16, 2021 post, although the body dates the return to June 6. [2]
Retail, TBC and Season of Mastery (historical)Historical seller compatibilitymacOSNot verifiedBaneto's seller stated Tinkr support in 2022. A later edit discussing Windows does not change Tinkr's macOS platform. [3]
Cataclysm Classic; some Anniversary use (historical)User-reported 2025 usagemacOSNot verifiedThis record describes historical compatibility. [4]

Community and support

Old integration guides and discussions are still readable, but they do not lead to a verified current Tinkr support channel.

Support details

The surviving integrations and discussions provide historical context, while a current Tinkr support channel remains unverified.

A user reported unresolved GoHandsFree/Tinkr compatibility trouble in May 2024, without enough detail to establish its duration or who was responsible. [1]

Features and plugins (1)
  • Older integration guides describe using BadRotations with Tinkr. [source]

These details come from the linked published sources; we have not tested the software ourselves.

Privacy and security

Our description is based on the linked documentation; we have not tested Tinkr ourselves or found an independent comparison of its security or detection rates.

Update record

The surviving records describe older integrations and compatibility trouble. They leave update speed unmeasured and do not establish an active Tinkr update service.

Update log and evidence (2)

Current availability and patch turnaround both remain unresolved; no reliable timing figures were found.

Update speed has not been measured.

  1. 2021-06-16
    Orca's seller announced Tinkr integration, with the post's text giving June 6 as the return date.

    Integration, not Tinkr release speed

    [2]
  2. 2024-05-06
    A user described a prolonged compatibility problem between GoHandsFree and Tinkr.

    Third-party integration

    [1]
  • A directory entry, testimonial or automatic updater cannot supply the missing measurements of patch turnaround.
  • A public release history with version numbers was unavailable.
  • The documentation and third-party compatibility records are historical, with no current Tinkr update service established.

Ban reports and history

Users reporting bans disagree over whether Tinkr or the scripts running through it were responsible. Reports of closure and the changed website concern the service's availability, without establishing another detection.

About these reports

Several public posts describe Tinkr-related bans, but users repeatedly disagree about the role of Tinkr versus a framework running through it. The closure reports and changed website belong to the service history without establishing another detection.

The reviewed public records run from June 2021 through September 2026. Searches covered banwave, bans, detection, hacked, malware and breach, without finding a complete provider incident archive, a technical cause report or a verified security breach. Repeated quotations were treated as references to existing incidents.

What do the cause labels mean?
2024-01-16ban report

Initial mass-ban allegation narrowed by its author

Attributed public report; not independently verified

The opening post initially alleged a wave, then narrowed the claim: only HF had substantial reports, while the other products had one or two. [5]

Full report, cause and response

Affected scope: Tinkr named alongside several tools

  • The original post was made at 23:02, but its edit date is unknown. The revised account does not establish a Tinkr-wide wave.
Cause: UnknownExplain the labels

No reproducible technical evidence or provider-confirmed cause was available to settle the claim.

Unknown [5]
Provider response
No public response from the provider was found for this event.
What happened next
The outcome remains unknown.
Attribution
The edited claim mixes products and leaves a Tinkr-specific detection mechanism unknown.
Date precision
Report date; underlying incident date unknown

Sources [5]

2024-06-19ban report

Periodic Tinkr-stack bans mentioned with attribution uncertainty

Attributed public report; not independently verified

The directory author passed on hearsay while explicitly questioning whether Tinkr itself was responsible. [6]

Full report, cause and response

Affected scope: macOS users with third-party scripts

Cause: UnknownExplain the labels

The hearsay is unsupported by reproducible technical evidence or a provider-confirmed cause.

Unknown [6]
Provider response
No public response from the provider was found for this event.
What happened next
The outcome remains unknown.
Attribution
The report leaves both the responsible component and the enforcement mechanism unresolved.
Date precision
Report date; underlying incident date unknown

Sources [6]

2024-09-01framework ban report

Awful-on-Tinkr reports distinguished from unlocker detection

Attributed public report; not independently verified

One participant attributed the bans to Awful and specifically said the reports did not establish a Tinkr detection. [7]

Full report, cause and response

Affected scope: Awful framework used with Tinkr

  • This discussion and later recollections of Awful do not provide evidence of separate Tinkr waves.
Cause: UnknownExplain the labels

The competing attribution remains unresolved without reproducible technical evidence or a provider-confirmed cause.

Unknown [7]
Provider response
No public response from the provider was found for this event.
What happened next
The outcome remains unknown.
Attribution
A community participant attributed the bans to the attached framework, without independent confirmation.
Date precision
Discussion date; historical event date not established

Sources [7]

2025-05-26disputed historical report

Conflicting recollections of earlier Tinkr/Awful bans

Attributed public report; not independently verified

One user recalled repeated bans, while replies disputed the unlocker's role and another account was explicitly secondhand. [8]

Full report, cause and response

Affected scope: Tinkr plus Awful; unspecified earlier months

  • Replies from May 27-30 disagree about the explanation and do not date a separate new wave.
Cause: UnknownExplain the labels

These recollections supply neither reproducible technical evidence nor a cause confirmed by the provider.

Unknown [8]
Provider response
No public response from the provider was found for this event.
What happened next
The outcome remains unknown.
Attribution
The discussion does not settle whether the framework or unlocker was responsible.
Date precision
Report date; underlying incident date unknown

Sources [8]

2025-10-30ban report

Large ban-wave allegation

Attributed public report; not independently verified

After one user alleged a substantial wave, another reported unaffected use on November 5 and questioned whether Tinkr caused the bans. [9]

Full report, cause and response

Affected scope: Tinkr/macOS; branch and affected count unspecified

  • Post 1 alleges a wave and post 7 describes an unaffected account, leaving neither account as a definitive forensic finding.
Cause: UnknownExplain the labels

Neither participant supplied reproducible technical evidence or a provider-confirmed cause.

Unknown [9]
Provider response
No public response from the provider was found for this event.
What happened next
The outcome remains unknown.
Attribution
The reports leave the component and mechanism behind enforcement unknown.
Date precision
Report date; underlying incident date unknown

Sources [9]

2026-01-23service status report

Community reports Tinkr no longer viable

Attributed public report; not independently verified

A forum user described Tinkr as effectively finished, attributing its end to Blizzard's macOS enforcement. [9]

Full report, cause and response

Affected scope: Tinkr macOS

Cause: UnknownExplain the labels

The claimed cause remains unsupported by reproducible technical evidence or provider confirmation.

Unknown [9]
Provider response
No public response from the provider was found for this event.
What happened next
A later directory marks Tinkr offline, and the old website no longer presents the Tinkr product.
Attribution
This explanation comes from a user; an official shutdown notice was unavailable.
Date precision
Report date; underlying incident date unknown

Sources [9]

2026-09-12domain status observation

Former domain displays another product

Direct public-page observation

The former homepage now displays NilName content and an exit-scam accusation, while the documentation index is parked. [10][11]

Full report, cause and response

Affected scope: tinkr.site and docs.tinkr.site

  • Who controls the domain and why its content changed remain unknown. The accusation on the page cannot be established simply by observing that it exists.
Cause: UnknownExplain the labels

The website change has no established explanation supported by reproducible technical evidence or provider confirmation.

Unknown [10][11]
Provider response
No public response from the provider was found for this event.
What happened next
The former domain should no longer be treated as a Tinkr purchase route.
Attribution
The available evidence establishes none of the suggested explanations: domain takeover, migration, scam or breach.
Date precision
Observation date, not transition date

Sources [10][11]

Comments and ratings

If you have used Tinkr, this is the place to share how it went. The ratings here come from readers and are separate from the editorial ranking.

Loading ratings...
Log in to comment

You can join without an email address; we generate a nickname and a Login Key for you to keep.

Latest comments

References

  1. [1] Unofficial directory and May 6 compatibility complainttamedbeast; hihihouse / elitepvpers / community directory and original reply / Published: 2024-05-05 / Checked: 2026-09-12
    Source notes: Unofficial directory and May 6 compatibility complaint

    The editable opening post belongs to a directory shared by other products. Compatibility post 4 is dated 2024-05-06.

  2. [2] Orca return with Tinkr, post 360orca- / elitepvpers / original integration seller post / Published: 2021-06-16 / Checked: 2026-09-12
    Source notes: Orca return with Tinkr, post 360

    The post is dated June 16, while the seller's text gives June 6 as the return date.

  3. [3] Baneto supported branches, page 16BamboBaneto / elitepvpers / integration seller post / Published: 2022-05 / Checked: 2026-09-12
    Source notes: Baneto supported branches, page 16

    The phrase 'one year since wave' leaves the Tinkr incident's exact date unknown, so it was not converted into a dated event.

  4. [4] Farm bot review, historical costswardel / elitepvpers / user review / Published: 2025-07-17 / Checked: 2026-09-12
  5. [5] Pixel and Unlocker Rotations BAN WAVE, edited openingjflanden / elitepvpers / original user report / Published: 2024-01-16 / Checked: 2026-09-12
  6. [6] Directory replies 62-64tamedbeast / elitepvpers / community hearsay / Published: 2024-06-19 / Checked: 2026-09-12
    Source notes: Directory replies 62-64

    The AMP page at https://www.elitepvpers.com/forum/amp.php?page=5&t=5226096 presents the same discussion.

  7. [7] Pixel rotation recommendationtamedbeast / elitepvpers / community interpretation / Published: 2024-09 / Checked: 2026-09-12
    Source notes: Pixel rotation recommendation

    This is a discussion from the time, without a date for the underlying Awful event.

  8. [8] Considering a Mac mini, posts 3-8tomolitic; ndoepken27; Shunrai; deststraw; Killrilaf3 / elitepvpers / conflicting user reports / Published: 2025-05-26 / Checked: 2026-09-12
    Source notes: Considering a Mac mini, posts 3-8

    Follow-ups continue through May 30 and contain historical recollections rather than six separate events.

  9. [9] Tinkr Hit Hard - Have We Reached The End?cmurda26; Littledagger; her0mal / elitepvpers / original user reports / Published: 2025-10-30 / Checked: 2026-09-12
    Source notes: Tinkr Hit Hard - Have We Reached The End?

    The counterreport is dated November 5 2025, while the service-status claim is dated January 23 2026.

  10. [10] Former Tinkr homepageCurrent domain operator unverified / direct domain observation / Checked: 2026-09-12
    Source notes: Former Tinkr homepage

    The page now uses NilName branding, and its accusation remains unverified.

  11. [11] Former Tinkr docs indexCurrent domain operator unverified / indexed domain observation / Checked: 2026-09-12
    Source notes: Former Tinkr docs index

    The search index suggests the domain may be for sale, while direct DNS failed and the historical /Lua/ cached result is stale.

  12. [12] integration maintainergithub.com / integration maintainer
Back to the directory