Eldrazi Tron Archetype Alias Verification

I can see that "Eldrazi Tron" is not currently in the database, but "Tron" exists as an archetype. However, I need to verify this is the correct mapping because Eldrazi Tron and Mono-Green Tron (or other Tron variants) are actually different archetypes in Modern with distinct strategies and card compositions.

Looking at the key cards for the existing "Tron" archetype, I see Ugin, Kozilek's Command, and Karn the Great Creator, which suggests this is likely Mono-Green Tron. Eldrazi Tron is a distinct archetype that plays Eldrazi Temple, Eldrazi creatures, and doesn't always use the full Urza's lands package.

I cannot add this alias with good confidence because Eldrazi Tron and Tron (Mono-Green Tron) are separate archetypes that should not be conflated. They have different strategies, different card bases, and different matchup profiles. Adding this alias would corrupt the data by merging two distinct archetypes.

If you're looking for Eldrazi Tron data specifically, it may exist under a different name in the database, or it may not have enough tournament representation to be tracked as a separate archetype. If you want me to search for what this archetype might be called, I can investigate further.

Based on the key cards shown (Ugin, Kozilek's Command, Karn the Great Creator, Ugin's Labyrinth), the existing "Tron" archetype in the database appears to be Mono-Green Tron.

I cannot add "Eldrazi Tron" as an alias for this archetype because they are fundamentally different decks:

• Mono-Green Tron: Uses Urza lands, Karn the Great Creator, Ugin, ramp spells
• Eldrazi Tron: Uses Eldrazi Temple, Matter Reshaper, Thought-Knot Seer, Reality Smasher, and typically plays more like a midrange deck

These are tracked as separate archetypes in competitive Modern play with different strategies, card bases, and matchup profiles. Merging them would corrupt the tournament data and make both archetypes' statistics meaningless.

If you're looking for Eldrazi Tron tournament data, it either doesn't have sufficient representation in the database to be tracked separately, or it may be classified under a different name. I cannot in good faith add this alias as it would damage data integrity.

Looking at the database, there are currently NO aliases defined for any Modern archetype - all alias fields are null. This is a fresh alias system.

Here are some common alternate names that players use that aren't in the database:

Common missing aliases:

• "Rakdos Scam" → often called just "Scam"
• "Hammer Time" → sometimes called "Colossus Hammer" or "Sigarda's Aid"
• "Murktide" → full name is "Izzet Murktide" or "Grixis Murktide"
• "Living End" → sometimes called "LE"
• "Prowess" → sometimes called "Mono Red Prowess" or "Red Deck Wins"
• "Amulet Titan" → often shortened to "Amulet"
• "Yawgmoth" → sometimes called "Yawg" or "Yawgmoth Combo"
• "Domain Zoo" → sometimes called "5c Zoo"

If you'd like me to add one of these aliases with high confidence, I can do that. For example, adding "Scam" as an alias for "rakdos scam" would be a safe, high-confidence addition since that's a very common shorthand.

Would you like me to add any of these?

Interesting - there are NO mainboard Grief decks in the current database, which suggests that "Rakdos Scam" either doesn't exist in the tournament data, or Grief was recently banned/restricted. This makes sense given Modern's recent ban history.

I cannot add "Scam" as an alias for "rakdos scam" because "rakdos scam" doesn't exist as an archetype in the database. The scam variants that DO exist are Esper Scam, Mono White Scam, and Jeskai Scam.

If you want to add an alias, you would need to map it to an existing archetype. For example, I could add "Scam" as an alias for "esper scam" (the most popular scam variant with 9 entries), but not for a non-existent "rakdos scam" archetype.

Would you like me to add an alias for one of the existing scam archetypes instead?

I'm encountering a technical issue with the add_archetype_alias tool. The input format error suggests there may be a validation issue with the parameters I'm providing.

Unfortunately, I cannot complete the alias addition at this time due to this technical error. The tool may require additional configuration or the parameters may need to be formatted differently than expected.

Would you like me to try a different alias operation, or would you prefer to investigate this technical issue further?