# EngineAI Mecha King (Robot Free Combat Tournament)

- Canonical: https://robot-fighting-championship.com/leagues/mecha-king
- Record family: leagues
- Stable ID: mecha-king
- Data snapshot: 2026-08-02T00:00:00Z
- Data source: fixture

## Direct answer

Mecha King is retained as the predecessor identity to EngineAI’s URKL programme. It is not counted as a second active EngineAI league.

## Classification

- **Record status**: Superseded predecessor
- **Entity kind**: predecessor-tournament
- **Field role**: predecessor
- **Competition class**: EngineAI predecessor combat programme
- **Control mode**: Autonomous
- **Hardware field**: T800

## History

EngineAI used the Mecha King naming before launching the URKL identity. The record preserves lineage without duplicating events or audience.

## Format

Public material establishes a robot free-combat programme; any rule continuity with URKL must be proven version by version.

## Broadcast

EngineAI-owned media may connect the two names, but Project H labels the relationship rather than merging their catalogues.

## Verification boundary

Operator continuity is confirmed. Separate league continuity, results and rules are not.

## Rules status

**Do not inherit URKL rules.** The predecessor record has no independently imported versioned rules and cannot inherit the later URKL contract.


## Evidence claims

No published records.

## Events

No published records.

## Fights

No published records.

## Robots

No published records.

## Teams

No published records.

## People

No published records.

## Rules

No published records.

## Relationships

- maker:engineai operates league:mecha-king — confidence medium
- league:mecha-king requires_platform platform:t800 — confidence medium

## Media

No published records.

## Primary sources

- [Operator — EngineAI](https://www.engineai.com.cn/): Operator identity and programme lineage.

## Citation boundary

Use the canonical HTML page for visible evidence state, context, corrections and source relationships. This Markdown representation is generated from the same published Project H record and contains no draft or private fields.