Bestiary & Monsterssource backed7 minute read

Butterfly

Butterfly is a TFS 1.6 creature profile with 2 health, 0 experience, 0 configured attacks, and 0 loot entries. Source definition: Yellow butterfly. This reference traces behavior, elements, immunities, summons, and configured drops.

Reference profileTFS 1.6 monster-data reference
Reviewed
Evidence4 primary references

At a glance

Quick facts

Health
2
Experience
0
Speed
320
Race
venom
Attacks
0
Loot entries
0
Bestiary class
Not classified
Reference profile
TFS 1.6
Source definition
Yellow butterfly

Reading the Butterfly encounter

A bestiary number becomes meaningful only when it changes a decision. Butterfly brings 2 health, 0 base experience, no attack entry in the primary monster file, and a preferred target distance of 6. The source file identifies this variant as Yellow 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 Yellow butterfly definition is the profile interpreted here.

Butterfly 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. These reward notes belong specifically to Yellow 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. Server owners can edit these values without changing the creature name.

Butterfly core statistics
StatisticValueInterpretation
Maximum health2Configured health pool
Base experience0Award before external multipliers
Speed320Engine movement-speed input
RacevenomCorpse and effect classification
Race IDNot definedBestiary or protocol reference when present
Maximum configured attack bound0Largest absolute XML min/max value; not a guaranteed final hit

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.

Butterfly behavior flags
FlagConfigured value
SummonableNo
AttackableYes
HostileNo
IllusionableNo
ConvinceableNo
PushableNo
CanpushitemsNo
CanpushcreaturesNo
Staticattack90
Targetdistance6
Runonhealth2
CanwalkonenergyNo
CanwalkonfireNo
CanwalkonpoisonNo

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

Butterfly 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 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.

Apply the guide

Find servers using this profile

Server names, protocol labels, and map labels do not guarantee matching mechanics. Use these filters to find candidates, then verify the listing, owner documentation, and deployed ruleset.

ButterflyTFS 1.6 monstersvenom