Build, Flag, Glitch and Teleport Feeds

What each placement feed shows

Build Feed

Build Feed is the main construction history for the server. It posts the base actions that normally matter to owners: build, dismantle, destroy, place, dig in, dig out, mount, pack and fold. That means a gate being built, a wall being dismantled, a camo net being mounted, a tent being packed or a placed item being folded can all land in one readable Discord trail instead of staying buried inside raw ADM lines.

The post is built from the log entry, so it can show the player, action, object or structure part, time, and the location style the owner has enabled. It is useful for base disputes because it records the sequence of construction and teardown, not just the final state of the base.

Glitch Feed

Glitch Feed is not a second build feed and it is not an automatic cheat accusation. It is a filter that takes selected watched item groups out of Build Feed and sends them somewhere cleaner. When a log line is still a build or placement action, but the item looks like a generator, kit, tent, trap, barrel, fireplace or garden plot, Legion can move that post into the Glitch Feed channel.

That split matters because normal Build Feed stays useful for walls, gates, dismantles, packs and folds, while staff can keep one channel open for items that are commonly involved in stacking, clipping, exploit setups, suspicious traps or repeated placement spam. The owner decides which groups are watched, so a strict raid server can watch traps and kits while a casual server might only watch gardens or fireplaces.

Flag Feed

Flag Feed only cares about flags being raised or lowered. It keeps those records away from general building noise so the same signal can be used for different server rules. Some owners treat a lowered flag as a raid warning. Some use raised and lowered flags as Conquest progress. Others use it for faction war alerts, territory ownership, base claim audits or event notifications.

Because flag posts are isolated, a server can send them to a staff channel, public faction channel or Conquest channel without dragging every wall build and dismantle along with it.

Teleport Feed

Teleport Feed records configured teleporter movement. When a player uses a generated teleporter setup, the server log shows the move from one marker to another, and Legion turns that into a Discord post showing who moved and where the movement came from and went to.

It is mainly for owner-made travel systems: trader hubs, event rooms, safe-zone exits, arena portals, faction transport or admin-made map routes. It gives owners an audit trail for fast movement that would otherwise look like a player suddenly appeared somewhere else.

How Legion turns log lines into the right feed

DayZ writes building, placement, flag and teleport activity into the server log. Legion watches those log updates, recognises the type of line, then formats the useful parts for Discord: the player, action, item or structure, time and location output. Owners do not need to read raw log syntax to see that a player dismantled a wall, packed a tent, lowered a flag or used a teleporter.

After Legion recognises a build-style line, it checks the item name before posting. If the item belongs to an enabled Glitch Feed group, that record goes to Glitch Feed. If it is normal construction, it stays in Build Feed. Flag raised/lowered lines skip that build split and go to Flag Feed. Teleport lines go to Teleport Feed because they describe movement created by teleporter files, not normal walking, driving or combat movement.

This keeps each Discord channel useful. The build channel stays as the base timeline. The glitch channel becomes the item-watch channel. The flag channel becomes the territory or event signal. The teleport channel becomes the movement audit for custom travel systems.

Why owners split the placement feeds

Settings that control each part

Related Legion features