Two Structural Conflicts in Wurt's Moon Mutated Merm System

[corn072]

The skill tree expansion for Wurt introduced an intriguing concept through the Moon Mutated Merms—enhanced companions that offer increased combat potential and unique aesthetics. However, in actual gameplay, this system reveals two fundamental design inconsistencies that disrupt player agency and long-term strategic planning.

This post aims to analyze those two structural flaws:

- Loyalty Reset and the Breakdown of Persistent Companion Fantasy
- Irreversible Mutations and Loss of Player Control

 

1. Loyalty Reset and the Breakdown of Persistent Companion Fantasy
Moon Mutated Merms act like permanent companions once transformed: they follow the player indefinitely and do not require food to maintain loyalty. This gives the impression of a long-term ally designed for sustained play.

However, a critical system-level inconsistency arises during transformation:

- When a regular Merm is mutated, its existing loyalty timer is reset to zero.
- If the mutation ends—such as when the player disconnects or changes shard (e.g., cave ↔ forest)—the Merm reverts to a non-mutated state without any remaining loyalty, and instantly ceases to be a follower.

This effectively nullifies any time or resource investment the player made in recruiting and maintaining that Merm.

The result is a fundamental conflict: the mutation is designed to enhance a companion,
yet it simultaneously destroys the very loyalty system that defines that companion relationship.

This undermines the core identity of Wurt as a character who builds a lasting kingdom of Merms. A system that offers powerful allies at the cost of erasing the foundational bond between player and companion becomes counterintuitive, and ultimately self-defeating.

 

2. Irreversible Mutations and Loss of Player Control
Moon Mutated Merms also come with a passive combat ability: they reflect area-of-effect damage when struck. While situationally useful, this ability is completely uncontrollable by the player.

Problems arise in group combat or densely populated areas:

- The AoE counterattack can unintentionally aggro neutral mobs or damage friendly units.
- This disrupts coordination and makes the companion a strategic liability in certain scenarios.

More importantly, there is no in-game method to disable or reverse the mutation. The only way to "de-mutate" a Merm is:

- To disconnect or transition to a different shard (caves/forest), which removes the follower entirely.

To regain the Merm as a regular follower, players must re-feed it manually after mutation and loyalty both reset.

This is not just inconvenient—it represents a loss of meaningful control.
A powerful feature that cannot be toggled or dismissed becomes a hazard, not a tool.

In design terms, this is a case where ability automation overrides player intent. Without the option to strategically enable or disable such features, the system offers power at the cost of autonomy.

 

Wurt’s Moon Mutated Merm system is imaginative and impactful, but also structurally flawed in two important ways:

- Mutations reset loyalty, and once they expire, the Merm loses its follower status instantly—undermining long-term planning and character consistency.
- The mutation effect cannot be reversed or controlled, creating risk without giving the player tools to manage it.

These issues go beyond balance; they reflect a deeper disconnect between system mechanics and player experience. Going forward, offering players direct control over their companions' enhanced states—both in terms of persistence and behavior—would make this system feel more complete and coherent.

[Gashzer]

Both problems are solved with communal kelp feeder and brilliant mudslinger.

Communal kelp feeder makes regaining merm loyalty simple, barely an inconvenience.

Brilliant mudslinger allows you to regain mutation of the now befriended merms at no extra cost after mudslinger has been crafted.  Swapping to Wilson allows crafting of pure brilliance without rifts needing to be active.

Sounds like we have plenty of control for merms already.

 

Edited May 21, 2025 by Gashzer

[corn072]

2 hours ago, Gashzer said:

Both problems are solved with communal kelp feeder and brilliant mudslinger.

Communal kelp feeder makes regaining merm loyalty simple, barely an inconvenience.

Brilliant mudslinger allows you to regain mutation of the now befriended merms at no extra cost after mudslinger has been crafted.  Swapping to Wilson allows crafting of pure brilliance without rifts needing to be active.

Sounds like we have plenty of control for merms already.

 

Thank you for the insight. The Communal Kelp Feeder and Brilliant Mudslinger do offer some mitigation for the issues related to mutation and loyalty in the current system.
However, in actual gameplay, these tools fall short of providing true control over Merm companions due to several important limitations.

1. Communal Kelp Feeder

• This is a stationary structure, meaning it becomes ineffective during shard transitions (e.g., caves ↔ surface) or unexpected disconnects.

• More critically, a recurring bug has resurfaced where unfollowed Merms fail to return home, making loyalty recovery through the feeder unreliable or even impossible in many cases.

• As a result, players are effectively forced to place the feeder near Merm houses and only log out within that area to ensure functionality.
  This is less a convenience and more a conditional workaround imposed by the system's constraints.

2. Brilliant Mudslinger

• While it allows mutation to be re-applied without consuming resources, it comes with an 8-minute cooldown.

• Consequently, players are pressured into not exiting the game until the cooldown is complete if they want to use the Mudslinger immediately upon their next login—a subtle but clear form of time-based behavioral restriction.

In summary, while both tools help alleviate the symptoms, they do not offer a genuine form of control.
The original point remains: players need persistent, deliberate control over Merm mutation and loyalty, not systems that rely on rigid workarounds and passive timers.