Sugar Cube

Reading the Sugar Cube encounter

On paper, Sugar Cube is 28 health and 19 experience. In a corridor, those numbers gain teeth through an attack cycle that the public library does not expose, no single movement flag that tells the whole encounter story, and the terrain around the spawn.

Sugar Cube's clearest weakness lead is Energy and Fire. 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.

Sugar Cube'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.

Sugar Cube statistics and identity

Sugar Cube is listed by the current official creature library with 28 hitpoints and 19 experience. The public library provides categorical strengths, weaknesses, status behavior, and named loot, but it does not publish movement speed, raw attack intervals, exact damage bounds, defense rolls, armor, spawn positions, or respawn intervals.

Behavior, targeting, and movement

The current official library publishes Sugar Cube as a 28 hitpoint creature worth 19 experience. Its published weakness categories are Energy, Fire. Its published strength categories are Earth, Ice. It is listed as resistant to paralysis. It is listed as able to perceive invisible creatures. The public library does not expose attack intervals, raw damage bounds, movement speed, target-change chance, spawn density, or respawn interval, so those values must come from a server-specific primary source.

Attack cycle and combat pressure

The official Sugar Cube library profile does not publish an exact attack cycle, raw minimum and maximum damage, range, area geometry, condition timing, or targeting logic. Those fields are intentionally marked as unpublished rather than estimated from anecdotes or another server's implementation.

Defense, elements, and immunities

The current official library identifies strong, weak, immune, and healing damage categories for Sugar Cube but does not publish exact percentages. Those qualitative labels are preserved exactly as categories. Converting "strong" or "weak" into a made-up numeric modifier would create false precision, so percentage math requires a separate verified game or server source.

Complete configured loot table

The current official library names 1 possible Sugar Cube 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 Sugar Cube 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. Obtain attack-cycle and spawn data from the target server, then test the encounter under controlled conditions. Present a level recommendation only with that profile and evidence attached.

• Confirm current health, experience, strength, weakness, immunity, and loot labels against the official creature profile.
• 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.