Mimic

Reading the Mimic encounter

Before a player meets Mimic on the map, the source profile already sketches the encounter: 30 health, 0 experience, no attack entry in the primary monster file, and a preferred target distance of 5.

Mimic's clearest weakness lead is no published elemental weakness. With no additional positive elemental modifier recorded here, the practical hunt still turns on positioning, supply depth, neighboring creatures, and the target server's scripts rather than on one attractive damage label.

Mimic offers no direct corpse-loot entry in the available profile. If an encounter still awards something, the answer must be sought in a chest, action script, event controller, participation system, or another server-specific mechanism.

Mimic statistics and identity

Mimic is defined with 30 maximum health, 0 base experience, and speed 170 in TFS 1.6. The displayed experience is the creature definition's base value before stages, stamina, party sharing, boosts, prey, server rates, or event multipliers. Server owners can edit these values without changing the creature name.

Behavior, targeting, and movement

Mimic is configured as hostile and can enter combat without player initiation. Its target-distance setting is 5, so positioning and line-of-sight control matter more than they do against a purely adjacent attacker. Target-change chance, static-attack preference, push permissions, pathfinding, field walking, summons, and scripted abilities collectively determine behavior. The flags below are direct configuration values; they should be read together instead of treating one flag as a complete artificial-intelligence description.

Attack cycle and combat pressure

Mimic has no attack entry in this XML definition. It may be non-combatant, invulnerable scenery, a scripted encounter object, or a creature whose behavior is delegated elsewhere. Do not invent a damage profile when the primary definition does not provide one.

Defense, elements, and immunities

The defense profile separates base defense and armor from elemental percentages and explicit immunities. In TFS 1.6, a positive monster element percentage reduces incoming damage of that element, while a negative percentage increases it. Current official strength and weakness labels are shown as categories without inventing a percentage. Custom servers can change those values, bypass them in scripts, or add encounter phases.

Complete configured loot table

Mimic has no loot entry in the available primary profile. A reward may still be delivered by a boss chest, storage action, event script, achievement, quest, participation system, or custom corpse callback, but this source does not support claiming a direct corpse drop.

Hunting plan and server verification

A safe hunting recommendation for Mimic must combine the available profile with spawn density, neighboring creatures, terrain, access, vocation, skills, equipment, supplies, latency, death penalty, and the target server's rates. No universal level bracket can be authenticated from a creature-library or monster XML record alone. Use the largest configured attack bounds as stress-test inputs, account for simultaneous attacks and summons, then verify the actual spawn. Present a level recommendation only with that profile and evidence attached.

• Confirm health, experience, attack intervals, and elemental modifiers against the deployed monster file.
• Inspect the map spawn file for count, radius, placement, and respawn interval; those values are not stored in this monster definition.
• Test line of sight, diagonal movement, field walking, target switching, fleeing, summons, and push behavior.
• Record corpse loot over a statistically meaningful sample before evaluating a customized loot rate.
• Publish the server profile and review date with any route, level range, profit estimate, or supply recommendation.