Of course! It's fantastic to meet another Mekton Zeta enthusiast. You've hit on something very specific and very true: the game is a masterpiece of
concept and
toolkit design, but it can stumble in actual
execution at the table. You've purchased the best part first—Mekton Zeta Plus is the crown jewel of the system.
Let's break down the common criticisms, analyze their root causes, and develop concrete solutions. Your instinct that the system is amazing for anime adventures is 100% correct; it just needs a little tuning to get there.
The Core Issues: Why Player Experience Can Be "Lackluster"
The problems aren't with the core concepts (like the awesome lifepath charts you mentioned) but with the mechanical weight and pacing during play.
1. The Grind of Mektons vs. Mektons (The "HP Sponge" Problem)
- The Problem: This is the #1 complaint. Mektons have massive amounts of Armor (AR) and Structure Points (SP). Weapons do relatively low damage (Kills) in comparison. A standard Mekton assault rifle might do 2d10+5 Kills (avg. 16 damage) against a target with AR 15 and SP 60. You're scratching off 1 SP per hit. This turns mecha combat into a protracted, boring grind of "I shoot. I hit. I do 1 point of damage." It completely kills the dynamic, cinematic feel of anime combat.
- The Root Cause: The damage scales linearly, while durability scales exponentially during construction. A slightly bigger mech isn't slightly tougher; it's vastly, disproportionately tougher.
2. The "One Roll" Problem for Pilots
- The Problem: A pilot's turn in a Mekton often boils down to a single skill check: Mecha Combat. They roll to hit. If they succeed, they roll damage. That's it. Compared to a ground-scale character who might be using Stealth, Electronics, Conversation, and various combat skills, the pilot's gameplay loop is extremely narrow.
- The Root Cause: The rules focus heavily on the machine's capabilities, not the pilot's actions within the machine. Anime is full of pilots doing crazy things—"Pushing the reactor to 120%!", "Bypassing the safety limiters!", "Analyzing the enemy's attack pattern!"—but the core rules don't have strong, codified subsystems for this.
3. The "Gearhead" Barrier
- The Problem: Mekton Zeta Plus is a brilliant vehicle construction system, but it's complex. This often means one player (the GM, or a dedicated "gearhead" player) spends hours building mecha while others are left out. This can create a power imbalance and disengage players who aren't as interested in the math.
- The Root Cause: The construction system is a detailed engineering simulator. Playing the game shouldn't require an engineering degree.
4. Action Economy and Stun
- The Problem: The Stun system, while intended to emulate mechs being shaken up by hits, can often lead to a death spiral. Once a Mekton is Stunned, it loses its next action. A focused enemy team can keep a player Stunned and unable to act for multiple rounds, which is incredibly frustrating.
- The Root Cause: Losing a turn is one of the biggest penalties in any RPG. In a system where turns can already feel samey, losing yours entirely feels terrible.
The Solutions: Tuning the System for Anime Action
Here’s how we can fix these issues. Think of these as official "house rules" or a "Mekton Zeta 2.0" patch.
Solution #1: Fix the Combat Grind (The Golden Rule)
This is the most important fix. You have two excellent options:
- Option A: The Mike Pondsmith Method (From the Designer Himself)
In later interviews and discussions, Mike Pondsmith suggested a simple, elegant fix: Halve all SP values (round up) on all Mektons, both player and enemy. A mech with 60 SP becomes 30 SP. That assault rifle now does meaningful damage. Combat becomes deadly and fast, encouraging maneuver and tactics over just trading blows.
- Option B: The "Shields Down" Method (My Preferred Hybrid)
This creates a more dramatic ebb and flow to battles.
Ignore AR for the first point of SP damage. A hit that beats the target's evasion always does at least 1 point of SP damage, even if it doesn't exceed AR. This represents shields flaring, armor scorching, and superficial damage.
If the damage roll exceeds the target's AR, it does double its normal SP damage. This represents a solid breach, a critical hit, or a shot to a weak point.
Example: Your assault rifle (2d10+5, avg. 16) shoots a target with AR 15.
If you roll a 16 (just barely beating AR), you do 1 point of SP damage.
If you roll a 17+ (beating AR), you do 2 points of SP damage.
This makes every hit meaningful and rewards high damage rolls immensely, cutting combat time in half while adding a exciting risk/reward layer.
Solution #2: Make the Pilot Matter
Create a list of "Pilot Actions" that players can choose from instead of just a basic attack. These should use various skills.
- All-Out Attack: Use your Mecha Combat skill. Roll damage twice and take the better result. You suffer a -2 to your Evasion until your next turn.
- Aimed Shot: Use your Awareness or Targeting skill. Make a called shot to a specific location (arm, weapon, sensor head) at a penalty, but with a dramatic effect on a success (disarm, destroy weapon, blind).
- Overload Systems: Use your Electronics skill. Push your mech beyond its limits. You might get +2 to your next damage roll, but you have to make a Systems Reliability check or suffer a temporary malfunction (e.g., weapons offline for 1 round, movement halved).
- Analyze Enemy: Use your Tactics skill. Make a contested roll against the enemy pilot's Tactics or Mecha Combat. On a success, you learn one of their core stats (AR, primary weapon damage, SP of a location) and the next ally to attack them gets a +1 bonus.
This gives pilots a meaningful choice every turn that reflects their character's strengths.
Solution #3: Democratize Mecha Creation
- Use Templates: For your first game, don't let players build from scratch. Give them a selection of pre-built "Templates" (The Fast Scout, The Heavy Bruiser, The Artillery Sniper, The Command Unit). Let them customize them with 2-3 options (e.g., swap a missile pod for a beam rifle, add extra armor at the cost of speed). This is incredibly anime—pilots are often assigned a machine and make personal tweaks.
- Session Zero Build: If you do a build-from-scratch game, make it a group activity in Session Zero. Frame it as "The team is assigned to test the new XM-07 prototypes. Work with the engineers to design your specialized unit." This makes it a collaborative, social event rather than a solo math homework assignment.
Solution #4: Tweak Stun
Change the Stun effect from "lose your next action" to
"you are at a -4 penalty to all actions on your next turn." This is still a severe setback but doesn't completely remove player agency. It feels less punishing and more like struggling with a damaged machine.
Putting It All Together: Your Game Plan
- Get Mekton Zeta. It has all the core rules for skills, drama, and ground-scale action that complete the picture.
- Implement the "Shields Down" damage rule (Solution #1B) as your primary combat fix. It's the most dramatic and fun.
- Create a "Pilot Action Menu" handout for your players based on Solution #2. Start with 3-4 options and expand as you play.
- Start with pre-built mecha or run a group build session. Use the amazing Mekton Zeta Plus to design cool enemies and NPC mecha, which is where it truly shines for the GM.
- Embrace the Random Charts! You're right, they are genius. Use them not just for characters, but to generate mission ideas, rival pilots, and corporate drama.
Mekton Zeta is a fantastic engine. It just needs the "anime action" dial turned up to 11. With these tweaks, you'll be well on your way to running the crazy, trope-filled, dramatic mecha game you're envisioning. Good luck, and have a blast.