Butterfly

Reading the Butterfly encounter

On paper, Butterfly is 2 health and 0 experience. In a corridor, those numbers gain teeth through no attack entry in the primary monster file, a preferred target distance of 6, and the terrain around the spawn. The source file identifies this variant as Blue butterfly.

Butterfly'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. The Blue butterfly definition is the profile interpreted here.

Butterfly's official profile names nothing among its possible loot without publishing a probability. That is enough to identify a reward, but not enough to promise profit or calculate an expected return. These reward notes belong specifically to Blue butterfly.

Butterfly statistics and identity

Butterfly is defined with 2 maximum health, 0 base experience, and speed 320 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. The current official library separately reports 2 hitpoints and 0, so differences remain visible instead of being silently merged.

Behavior, targeting, and movement

Its target-distance setting is 6, so positioning and line-of-sight control matter more than they do against a purely adjacent attacker. It begins trying to flee below 2 health, which can lengthen the final portion of a kill if paths remain open. 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

Butterfly 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

The current official library names 1 possible Butterfly loot item but does not publish exact drop probabilities or stack ranges. The names are useful acquisition evidence; they must not be converted into fabricated percentages. An Open Tibia implementation can use a different list or deliver rewards outside the corpse.

Hunting plan and server verification

A safe hunting recommendation for Butterfly 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.