w/wowunlockers
Menu

Historical project

UCS

United Combat Solutions

United Combat Solutions (UCS) ran KFM PvE and HandsFree PvP rotations on its own platform. It closed in May 2021, blaming a legal demand on a supplier.

WindowsDiscontinued in 2021

Status

Discontinued in 2021

View historical source

Historical community discussion; service discontinued

Historical recordsEdited by M1Sources checked

Overview

UCS stands for United Combat Solutions. It was a platform for combat rotations and scripts. KFM focused on PvE; HandsFree covered PvP and casual PvE. They had separate subscriptions and support arrangements. Community reportCommunity reportCommunity report

More about this product

UCS closed in May 2021. The provider said a legal demand to its kernel-technology supplier forced the shutdown. The surviving sales thread is an archive, not a current offer. Community reportCommunity report

Before you buy

  • Closed in May 2021. Old subscription terms and support promises are history.

Pricing and access

KFM, one class (historical)

EUR 40 / EUR 803 months / 1 year

Seller quote from September 2019 for the rotation offering.

More on KFM, one class (historical)

Not a current offer or a standalone unlocker price.

Community report

HandsFree on UCS (historical)

USD 483 months

Lowest seller-quoted price on 3 January 2021, paid in BTC on UCS without an additional platform subscription.

More on HandsFree on UCS (historical)

Payment method and platform affected the price. No current purchase is available.

Community report

The old prices are kept below as history.

Requirements

Scroll sideways to see all columns.

Game branchSystem / regionCoverage and limits
Retail: BFA and Shadowlands eraHistorical onlyWindows / historical kernel-based platformNo complete regional matrix preservedFebruary 2021 seller posts advertised 36 specializations across 12 classes. No current Retail support. Community report
ClassicHistorical onlyHistorical PC clientNot specifiedThe seller announced Classic rotation support in September 2019. Its kernel platform did not support VM/Hyper-V configurations in the quoted requirements. Community report
Hardware requirementsJanuary 2021 claimIntel 3rd generation or newer / AMD Ryzen, per sellerNot applicableThe seller gave this broad rule while responding to a Ryzen 3950X compatibility complaint. It was not a guarantee for every motherboard or configuration. Community report

Community and support

The original sales thread remains available. Support once ran through Discord with separate KFM and HandsFree arrangements; no current UCS support service exists.

Original UCS discussionProvider thread / Public historical record
Support details

The original sales thread is the useful archive. Support ran through Discord, with separate arrangements for KFM and HandsFree. No current UCS support service exists.

A January 2021 exchange said HandsFree support did not accept PvE bug reports; KFM was intended for that use. The routine you bought determined which support you could expect. Community report

On 5 February 2021, the seller promised replies within 24 hours during email maintenance. This was a promise for that period, not a measured long-term average. Community report

Features and plugins (1)

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

Privacy and security

No independent security or detection history. UCS is closed.

Comments and ratings

If you have used UCS, this is the place to share how it went. The ratings here come from readers and are separate from the site 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

Update record

The September 20, 2019 ban acknowledgment and September 26 fix announcement were six calendar days apart. That measures one incident response, not average patch speed or confirmed recovery. Compatibility complaints continued.

Update log and evidence (5)

September 2019 has a dated response timeline. It also shows why a release announcement is not the whole story: users still reported compatibility problems afterward.

The 20 September acknowledgment and 26 September release announcement were six calendar days apart. This measures one incident response, not average patch speed or verified restoration time.

  1. 2019-09-20
    Bans acknowledged; service suspendedCommunity report
  2. 2019-09-21
    Investigation extended; daily updates promisedCommunity report
  3. 2019-09-26
    Provider announced a fix

    Retail compatibility complaints followed on 26-27 September.

    Community report
  4. 2021-02-09
    Seller advertised Shadowlands rotation coverageCommunity report
  5. 2021-05
    Service closed

    Closure was being discussed by 27 May.

    Community reportCommunity report
  • Publication of a release does not establish that every game branch was restored.
  • Old support promises expired with the service.

Ban reports and history

The seller acknowledged September 2019 bans and later described January 2019 and September 2020 waves. Its surviving accounts differ in places; dates and qualifications are kept with each claim.

About these reports

UCS has a documented ban history. The seller acknowledged September 2019 cases and later described January 2019 and September 2020 waves. Those accounts need their dates and context because the seller's summaries do not always agree.

Original provider and customer posts are linked below. The provider supplied the January 2019 date retrospectively, without explaining how it relates to the later UCS launch. The May 2021 closure is a service event, not another detection.

What do the cause labels mean?
2019-01-05 (retrospective claim)Provider retrospective

Seller later describes a targeted January 2019 wave

Acknowledged in later provider posts

The seller called 5 January 2019 its last targeted wave, then repeated January 2019 in a January 2021 reply. Community reportCommunity report

Full report, cause and response

Affected scope: UCS or its earlier technology; exact edition and affected population unclear.

  • The original public UCS sales thread began in September 2019. These later remarks do not explain the predecessor relationship.
  • The same thread acknowledges September 2019 bans at the time. The word only in a later summary does not erase that acknowledgment.
Cause: UnknownExplain the labels

The report does not identify the technical cause.

No demonstrated mechanism Community reportCommunity report
What happened next
We found no original January announcement, affected build or technical investigation.
Date precision
Date supplied by the seller on 25 December 2020; not independently reconstructed.

Sources Community reportCommunity report

2019-09-19 to 2019-09-26Provider acknowledged bans

Bans, a service shutdown and a claimed fix

Provider acknowledgment; cause not independently verified

Customers reported bans on 19 September. The following morning, UnitedSolutions confirmed several cases and suspended the service. Community reportCommunity report

Full report, cause and response

Affected scope: UCS users; reports mention KFM, but the full branch and module split is unknown.

  • The seller said fewer than 10% were affected. No independent total user count or account list supports that percentage.
  • The 21 September update extended the investigation.
Cause: UnknownExplain the labels

The seller described security changes but gave too little evidence to establish a specific monitored bypass, leaked build or detection signal.

No demonstrated mechanism Community report
Provider response
On 26 September the seller announced changes to kernel protection, process identification and startup checks, and said it had fixed the cause.
What happened next
Users still reported unsupported Retail clients on 26-27 September. The release announcement proves neither complete restoration nor future safety.
Date precision
Reports on 19 September; acknowledgment on 20 September; claimed fix on 26 September.

Sources Community reportCommunity report

2019-10-05 (report date)Individual report

A later user report cannot be dated as a new wave

Uncorroborated account report

swoop1 reported a two-year ban after using UCS. The post does not establish whether it followed September exposure or a different incident. Community report

Full report, cause and response

Affected scope: One poster; build, branch and use dates missing.

Cause: UnknownExplain the labels

The report does not identify the technical cause.

No demonstrated mechanism Community report
What happened next
Kept as a follow-up account. It does not confirm a separate detection.

Sources Community report

2020-09 (retrospective claim)Provider retrospective

Seller attributes a wave to public add-ons

Provider acknowledgment; attribution unverified

UnitedSolutions said September 2020 bans involved public add-ons such as BadRotations, rather than a UCS-specific targeted detection. Community reportCommunity report

Full report, cause and response

Affected scope: Provider claimed multiple platforms using public add-ons were affected.

  • The seller says all relevant platforms were affected. This has not been measured across platforms.
Cause: Unknown; provider blamed public add-onsExplain the labels

Naming an add-on does not show whether detection used file identification, client observation or another signal.

Provider attribution only Community reportCommunity report
What happened next
No exact build, exposure period or independently verified cause was supplied.
Date precision
Month given in December 2020 and January 2021 provider replies.

Sources Community reportCommunity report

2021-01-29 (report date)Individual report

User acknowledges a ban without an incident date

Self-report; timing unresolved

shnarea187 said they had been banned while using UCS. The reply does not date the ban, so it cannot establish a January 2021 wave. Community report

Full report, cause and response

Affected scope: One account of UCS use; no branch or build supplied.

Cause: UnknownExplain the labels

The report does not identify the technical cause.

No demonstrated mechanism Community report

Sources Community report

2021-05; reported by 27 MayService closure

Service shutdown and mixed refund reports

Provider notice and customer follow-up

The provider said a legal demand to its kernel supplier forced the service to stop. Community reportCommunity report

Full report, cause and response

Affected scope: UCS sales, development and support.

  • On 27-28 May some customers reported successful full or partial refunds through PayPal. Others using BTC reported trouble recovering payments.
  • The posts show different customer outcomes. They neither prove fraud nor authenticate the legal demand.
Cause: Legal demand / service shutdownExplain the labels

The provider says a legal demand led to the loss of its technology supplier. That describes a shutdown cause, not a game-detection method.

Provider explanation; underlying letter not independently inspected Community reportCommunity report
Provider response
The original thread now carries the shutdown notice.
What happened next
We found no current supported UCS service. The edited first post retains its creation date, but that does not put the closure in September 2019.
Date precision
The edited first post has no reliable shutdown timestamp. Dated replies establish closure by 27 May.

Sources Community reportCommunity report

Sources used

Back to the directory