Unexpected Container Detection

New in 1.5

Reacts when a container opens during a farming macro without an interaction that explains it.

Unexpected Container Detection watches for menus that open on their own during a farming macro. If a chest or other container GUI appears without a recent interaction that explains it, such as a visitor or the macro's own clicks, Polinex flags it as a possible check.

Unexpected Container Failsafe turns it on. Container Interaction Window sets how many seconds before the menu opened an interaction can still explain it, and Unexpected Container Strength picks Low, Normal or High strictness. Detections trigger your configured failsafe reactions and alerts, and /failsafe simulate container lets you test the response.

Failsafes react to what they can observe. They lower risk, they do not remove it, and no setup can guarantee an account stays unbanned.

Settings 3

Shown at their defaults
  • Unexpected Container Failsafe

    Starts a failsafe when a container opens without a recent interaction during a farming macro.

  • Container Interaction Window

    Seconds before a container opens that an interaction can explain it.

  • Unexpected Container Strength

    Sets how strict container ownership detection is.

Included with Polinex. See packages

All features