This System Requirements Document specifies Offensive Security (project handle terra-offensive), a floating ESP, FOV and aim-assist overlay for Free Fire on a physical, non-rooted Android phone. The product is delivered as a React/JSX web application whose detection, tracking and prediction logic runs in JavaScript, paired with a native Kotlin module — MediaProjection screen capture, ImageReader frame delivery, AccessibilityService touch injection and an NCNN binding — that the operator compiles and packages outside the platform. The platform itself does not produce a signed APK and does not generate the native Kotlin module; the operator performs the build and packaging step.
The audience is a technically minded player-operator who wants a draggable floating control panel and a live HUD that draws ESP boxes and a FOV ring over the game feed, with confidence, FOV and prediction sliders, ESP/aim toggles and per-weapon recoil offsets. A second audience is the security researcher/developer who compiles the native module and packages the web app (Capacitor or Bubblewrap) into an installable artifact.
The requester asked this builder to produce the project's System Requirements Document; this document is that deliverable. It covers the product's features and workflows in full, together with the requested topics of target users, success criteria and roles.
head and body, optional enemy_visible) runs at 320×320 input and is exported to NCNN or TFLite INT8; detections above the configured confidence threshold produce ESP boxes on the HUD.position + velocity × measured latency, clamped by a maximum displacement and frozen after 250 ms without detection; target selection uses a score over crosshair distance, confidence and distance with 15% hysteresis so the lock does not flicker between targets.Offensive Security is a three-surface product. Landing is the anonymous public entry that explains the floating ESP/FOV/aim panel for Free Fire on a phone without root and opens the panel. Painel is the draggable floating control panel with confidence, FOV and prediction sliders, ESP and aim toggles, and per-weapon recoil offsets. HUD draws ESP boxes and the FOV circle over the game feed using tracker and prediction results. All three surfaces are application-owned and reachable without an account (access_requirement: none).
The runtime is a React/JSX web application. Detection, tracker and prediction logic live in JavaScript. Screen capture comes from the native Kotlin module via MediaProjection and ImageReader; touch injection comes from AccessibilityService dispatchGesture; inference runs through the NCNN binding. The operator grants MediaProjection permission, grants SYSTEM_ALERT_WINDOW overlay permission for the panel and HUD, and enables the AccessibilityService for touch injection. The developer compiles the Kotlin module and packages the app (Capacitor or Bubblewrap) outside the platform.
Provisioned infrastructure is a shared FastAPI backend, a MariaDB database and a React frontend. The backend hosts application APIs and domain modules; the database holds application-owned persistent data; the frontend serves the three surfaces.
Removed from scope
The product is a first-party web application with three anonymous, application-owned surfaces. No account, login or identity continuity is required: the panel is a local tuning surface, the HUD is a local overlay renderer, and the landing page is a public explainer. The platform owns the web app, its JS detection/tracker/prediction logic, the panel controls and the HUD rendering. The platform does not own the native Android module (MediaProjection capture, ImageReader, AccessibilityService injection, NCNN binding) and does not own APK signing or packaging — both are explicitly the operator's work outside the platform. The manus.im protection bypass is explicitly excluded and is not a product capability. Current scope is the three surfaces plus the JS logic; nothing in this document establishes a future horizon beyond that.
SYSTEM_ALERT_WINDOW granted/denied) and AccessibilityService (enabled/disabled).head and body, optional enemy_visible) at 320×320, exported to NCNN or TFLite INT8 so that detections are accurate and fast. (explicit) — Trigger: a captured frame. Result: detections with class and confidence. Failure: inference unavailable surfaces on Painel. Continuation: detection resumes on the next frame.SYSTEM_ALERT_WINDOW overlay permission for the panel and HUD so that they draw over the game. (required_inference) — Trigger: first overlay request. Result: panel and HUD visible over the game. Failure: denial hides the overlay and is shown on Painel. Continuation: re-grant from Painel.The player-operator runs the overlay during a Free Fire match on a physical, non-rooted phone. Their goal is to see enemy positions through ESP boxes, keep the FOV ring centered on their aim area, and let the aim assist lead moving targets. They tune confidence, FOV radius and prediction from the draggable panel without leaving the game, toggle ESP and aim, and set per-weapon recoil offsets. They grant MediaProjection, overlay and AccessibilityService permissions when prompted. Their success is a stable HUD with confirmed boxes, a non-flickering lock and responsive sliders.
The researcher/developer owns everything outside the platform: compiling the Kotlin module with MediaProjection, ImageReader, AccessibilityService and the NCNN binding, and packaging the React web app with Capacitor or Bubblewrap into an installable artifact. Their goal is a working native module the web app can bind to and a packaged app the player can install. They do not tune the overlay in-match; they build, package and hand off. Their success is a compiled module and a packaged app produced outside the platform.
SYSTEM_ALERT_WINDOW and AccessibilityService; the player grants each. If a grant is denied, Painel marks the affected capability unavailable and offers a re-grant action.position + velocity × measured latency, clamps displacement and freezes after 250 ms without detection.Muse: Gleb Kuznetsov. Headline: Detect. Track. Aim.
#05070D.#0D1220.#E8F1FF.#00E5FF.#FF2D7A.#6B7A99.The public entry is a full-bleed dark navy stage holding one floating glass HUD frame at 60% width. Cyan wireframe boxes drift inside it and a magenta FOV ring pulses at center. The 96px wide-caps headline sits left over the drifting detection field; the panel mock floats right with a soft cyan glow. The FOV ring is a live magenta circle that follows the cursor across the hero stage. Sliders render as thin luminous rails with a glowing cyan knob and a monospace value at the end. The floating panel is a glass card with a 1px cyan top edge and a six-dot drag handle. Section breaks use a single horizontal data rail of scrolling monospace telemetry. The concept recomposes only accepted content and controls.
Interaction Model: Animated Motion Tempo: cinematic Hero Dimensionality: webgl
Landing Hero Motion Brief
Landing Hero 3D Scene Brief — DIRECTION-DERIVED
One crafted real-time scene: a dark navy void containing a glass HUD frame with drifting cyan wireframe boxes and a magenta FOV ring that follows the cursor. The scene shows the product's defining state — detection boxes and the FOV ring over a live feed — and is built with WebGL/R3F.
dispatchGesture. (explicit)clamp(...); decoration may bleed but never covers readable text or controls. (required_inference)prefers-reduced-motion. (required_inference)head and body, optional enemy_visible, 320×320, exported to NCNN or TFLite INT8.SYSTEM_ALERT_WINDOW and AccessibilityService are the only capture/overlay/injection mechanisms.head and body.No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!