Equipment & Itemssource backed6 minute read

Forest floor

Forest floor is documented as map and world objects across 18 item identifiers in pinned TFS 1.6 data, with XML attributes, exact configured drops, and current official creature-library loot mentions traced separately.

Reference profileTFS 1.6 item-data reference
Reviewed
Evidence2 primary references

At a glance

Quick facts

Classification
Map and world objects
Identifiers
18 across 2 XML definitions
Item ID reference
20776-20781, 21113-21124
Defined attributes
0
TFS loot sources
0
Official loot mentions
0
Source profile
TFS 1.6

Forest floor in the hands of a player

Forest floor may occupy a single square in a backpack, but its source identity is wider: 18 identifiers beginning with 20776-20781, 2 XML definitions, and 0 declared attribute families.

Forest floor belongs to the scenery and machinery of the world. Placement, tile flags, movement permissions, decay, and scripted interaction give it meaning that a backpack tooltip cannot capture.

No indexed monster definition names Forest floor as direct corpse loot. The silence is useful because it narrows the next search to quests, NPC trades, map rewards, crafting, events, stores, and action scripts instead of encouraging an invented hunting route.

Forest floor identity and identifiers

Forest floor appears in the pinned item registry under 18 concrete identifier values. This page groups definitions that share the exact source name so readers can compare alternate graphics, transformation states, map variants, or legacy identifiers without treating each numeric ID as a different search topic. The identifiers are engine references, not proof that every Open Tibia server exposes every variant to players.

Forest floor source variants
Item ID or rangeArticleVariant attributes
20776-20781Not specifiedNo XML attributes on this variant
21113-21124Not specifiedNo XML attributes on this variant

Attributes and mechanical meaning

Forest floor is classified here as map and world objects from its name and declared XML attributes. This is primarily a world or map object, so placement, movement, use, and decay behavior depend on map flags and server scripts in addition to this XML entry. Exact behavior can be supplemented or overridden by the server binary, the OTB item registry, Lua actions, movement events, decay handlers, imbuement systems, or custom upgrade code.

Acquisition and recorded loot sources

No monster XML file in the pinned profile lists Forest floor as direct loot. That does not establish that the item is unobtainable. It may be awarded by a quest, NPC trade, map placement, reward chest, crafting system, action script, event, store, or custom content module. A server-specific guide should name one of those primary acquisition sources before presenting a method as verified.

Progression, use, and comparison

Evaluate Forest floor against alternatives in the same map and world objects class by comparing only attributes that the active server actually implements. For combat equipment, attack, defense, armor, elemental protection, skill modifiers, vocation restrictions, level requirements, charges, and weight can all change the practical result. For world objects and general items, the decisive behavior is more often an action, movement event, unique ID, or map placement that cannot be inferred from the display name alone.

  • Confirm the live item identifier before importing Forest floor into an editor, script, reward, or shop.
  • Compare XML attributes with the deployed OTB registry and any upgrade, tier, imbuement, or rarity layer.
  • Trace acquisition through monster files, NPC scripts, quest scripts, reward containers, and map placements.
  • Test equip, use, decay, trade, loss, and persistence behavior on the target server profile.

Reference boundary and change control

A correction to this entry should cite the exact deployed item definition, commit, server documentation, or reproducible live test. Screenshots can show appearance or a tooltip, but they do not independently prove hidden chance values, script branches, or database state. Keeping those evidence layers separate prevents a historical item ID or one server's custom value from being mislabeled as universal Forest floor behavior.

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.

forest floorTFS 1.6Map and world objects