At a glance
Quick facts
- Health
- 6,250
- Experience
- 100
- Speed
- 256
- Race
- energy
- Attacks
- 0
- Loot entries
- 0
- Bestiary class
- Not classified
- Reference profile
- TFS 1.6
Reading the Rift Invader encounter
Before a player meets Rift Invader on the map, the source profile already sketches the encounter: 6,250 health, 100 experience, no attack entry in the primary monster file, and no single movement flag that tells the whole encounter story.
Rift Invader's elemental profile rewards deliberate spell and weapon choices. The clearest weakness lead is Holy, while Ice carries positive resistance in this source. Pull size, line of sight, neighboring creatures, and simultaneous attack timing still decide whether that theoretical edge survives contact with the spawn.
Rift Invader 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.
Rift Invader statistics and identity
Rift Invader is defined with 6,250 maximum health, 100 base experience, and speed 256 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.
| Statistic | Value | Interpretation |
|---|---|---|
| Maximum health | 6,250 | Configured health pool |
| Base experience | 100 | Award before external multipliers |
| Speed | 256 | Engine movement-speed input |
| Race | energy | Corpse and effect classification |
| Race ID | Not defined | Bestiary or protocol reference when present |
| Maximum configured attack bound | 0 | Largest absolute XML min/max value; not a guaranteed final hit |
Behavior, targeting, and movement
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 Holy in this profile. Positive element modifiers reduce incoming Ice damage before final health loss. 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 |
|---|---|
| Pushable | No |
| Canpushitems | No |
| Canpushcreatures | No |
| Staticattack | 90 |
| Targetdistance | Yes |
| Canwalkonenergy | No |
| Canwalkonfire | No |
| Canwalkonpoison | No |
Attack cycle and combat pressure
Rift Invader 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.
| Defense layer | Value | Meaning |
|---|---|---|
| Armor | 35 | Base defense profile |
| Ice | 10% | Resistance |
| Holy | -15% | Vulnerability |
| Paralyze | Immune | Condition or damage immunity |
| Invisible | Immune | Condition or damage immunity |
| Drunk | Immune | Condition or damage immunity |
Complete configured loot table
Rift Invader 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 Rift Invader 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.