At a glance
Quick facts
- Health
- 1,300
- Experience
- 900
- Speed
- 200
- Race
- venom
- Attacks
- 5
- Loot entries
- 13
- Bestiary class
- Vermin
- Reference profile
- TFS 1.6
- Official profile observed
- 2026-08-02
Reading the Brimstone Bug encounter
Brimstone Bug tells its story in pressure and reward: 1,300 health to overcome, 900 base experience to earn, and 5 configured attack entries and a largest raw XML bound of 310 to read before the first pull.
Brimstone Bug's clearest weakness lead is Fire, Ice, Holy, Energy, and Physical. 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.
gold coin has the strongest configured loot roll on Brimstone Bug's TFS table at 50.00%, with up to 100 per successful entry. Profit, however, is a long conversation between kill speed, supply cost, route density, market demand, and the server's loot multiplier.
Brimstone Bug statistics and identity
Brimstone Bug is defined with 1,300 maximum health, 900 base experience, and speed 200 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 1,300 hitpoints and 900, so differences remain visible instead of being silently merged.
| Statistic | Value | Interpretation |
|---|---|---|
| Maximum health | 1,300 | Configured health pool |
| Base experience | 900 | Award before external multipliers |
| Speed | 200 | Engine movement-speed input |
| Race | venom | Corpse and effect classification |
| Race ID | 674 | Bestiary or protocol reference when present |
| Maximum configured attack bound | 310 | Largest absolute XML min/max value; not a guaranteed final hit |
| Official-library hitpoints | 1,300 | Current official profile |
| Official-library experience | 900 | Current official profile |
Behavior, targeting, and movement
Brimstone Bug is configured as hostile and can enter combat without player initiation. Its target-distance setting favors adjacent engagement, although configured beams, waves, or ranged attacks can still reach farther. Negative element modifiers identify increased incoming damage from Fire, Ice, Holy, Energy, Physical in this profile. 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.
| Flag | Configured value |
|---|---|
| Summonable | No |
| Attackable | Yes |
| Hostile | Yes |
| Illusionable | No |
| Convinceable | No |
| Pushable | No |
| Canpushitems | Yes |
| Canpushcreatures | No |
| Targetdistance | Yes |
| Staticattack | 90 |
| Runonhealth | No |
| Canwalkonenergy | No |
| Canwalkonfire | No |
Attack cycle and combat pressure
Brimstone Bug has 5 attack entries in its XML definition. Chance is evaluated within the listed interval by the engine; min and max values are source-level damage inputs and can be changed by scripts, armor rules, resistance, PvP modifiers, conditions, or custom combat callbacks. Range, radius, beam length, spread, target flags, and visual effects reveal the intended shape but do not replace a live positioning test.
| Attack | Chance and interval | Raw damage range | Range or area | Effects |
|---|---|---|---|---|
| Melee | Every 2 seconds | 0-213 | Adjacent or script-defined | No extra XML effect attribute |
| Speed | 20% per 2 seconds | 0-0 | 7 | Shoot Effect: death; Area Effect: mortarea |
| Earth | 5% per 2 seconds | 140-310 | 6 | Area Effect: smallplants |
| Manadrain | 10% per 2 seconds | 130-200 | 6 | Area Effect: greenspark |
| Earth | 15% per 2 seconds | 80-120 | 8 | Area Effect: yellowbubble |
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.
| Defense layer | Value | Meaning |
|---|---|---|
| Armor | 25 | Base defense profile |
| Fire | -10% | Vulnerability |
| Ice | -10% | Vulnerability |
| Holy | -10% | Vulnerability |
| Energy | -10% | Vulnerability |
| Physical | -5% | Vulnerability |
| Lifedrain | Immune | Condition or damage immunity |
| Death | Immune | Condition or damage immunity |
| Earth | Immune | Condition or damage immunity |
| Invisible | Immune | Condition or damage immunity |
| Energy | Weak | Current official library category; no percentage published |
| Fire | Weak | Current official library category; no percentage published |
| Holy | Weak | Current official library category; no percentage published |
| Ice | Weak | Current official library category; no percentage published |
| Physical | Weak | Current official library category; no percentage published |
| Death | Immune | Current official library category |
| Earth | Immune | Current official library category |
Complete configured loot table
Brimstone Bug contains 13 flattened loot entries. Base chance is shown against the TFS 100,000-point scale, where 100,000 means 100% before external loot multipliers. Count maximum is the upper stack bound when a successful roll creates a stackable item. Nested container contents are preserved as individual rows in the source data.
| Item | Item ID | Base chance | Maximum count |
|---|---|---|---|
| gold coin | Script-defined | 50.00% | 100 |
| gold coin | Script-defined | 50.00% | 100 |
| small emerald | Script-defined | 2.70% | 4 |
| stealth ring | Script-defined | 0.892% | 1 |
| platinum amulet | Script-defined | 0.110% | 1 |
| magic sulphur | Script-defined | 1.64% | 1 |
| strong health potion | Script-defined | 9.00% | 1 |
| strong mana potion | Script-defined | 9.03% | 1 |
| poisonous slime | Script-defined | 50.00% | 1 |
| lump of earth | Script-defined | 20.00% | 1 |
| sulphurous stone | Script-defined | 14.97% | 1 |
| brimstone fangs | Script-defined | 5.71% | 1 |
| brimstone shell | Script-defined | 10.00% | 1 |
| Item | Official evidence | Probability |
|---|---|---|
| brimstone shells | Named loot | No exact chance published |
| gold coins | Named loot | No exact chance published |
| lumps of earth | Named loot | No exact chance published |
| poisonous slime | Named loot | No exact chance published |
| sulphurous stones | Named loot | No exact chance published |
Hunting plan and server verification
A safe hunting recommendation for Brimstone Bug 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.