Skip to content
Projects

mizansherpur/loop-egg-harvest-stop

View on GitHub

mizansherpur/loop-egg-harvest-stop has 72 GitHub stars and 0 forks. GitHot measured 0 stars in 24 hours, 0 in 7 days, and +1 in 15 days. Last checked 2026-11-18 12:11 UTC. Last push 2026-11-18.

How these counts are measured

What you can do

  • 🔁 Continuous loop farming engine — configurable iteration cadence, adaptive delays, and drift correction so the rhythm never collapses.
  • 🛑 Instant stop hotkey — one binding halts every active loop, thread, and overlay in under a frame. No confirmation dialog. No "are you sure?"
  • 📦 Fully portable runtime — no system-wide installation, no registry writes, no background services. Extract, run, delete when done.
  • 🖥️ Responsive UI — the control panel reshapes itself for 4K monitors, laptops, tablets, and narrow side panels alike.

Measured star growth

in 24h
0
in 7 days
0
in 15 days
+1
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Automated Egg Collecting Farm Tool with Instant Stop Hotkey 2026

Productivity

README.md

Original

preview Download

🥚 Steal-an-Egg Auto Farm — Autonomous Loop Farming Utility for 2026

Platform Language Status License Version Portable Hotkey Multilingual Support

A looping automation companion for egg-collection style mini-games, built around a philosophy we like to call "set-it-and-forget-it stewardship." Where most automation utilities ask you to babysit a terminal, this one asks you to walk away — and trust that a single keystroke brings everything to a clean halt the moment you return.

Think of it less as a robot and more as a patient gardener who tends the same row of plots, over and over, silently, until you tap them on the shoulder.

This repository is an original, independent project. It is not affiliated with, endorsed by, or derived from any other auto-farm utility. It exists because the idea of "loop-based task repetition" deserves a thoughtful, well-documented, genuinely portable implementation.


📜 Table of Contents


🌱 Overview

Steal-an-Egg Auto Farm is a loop-based automation utility designed to repeatedly perform a defined sequence of actions — collect, reset, repeat — inside compatible egg-themed mini-games and idle-play environments. It does not require an installer, does not touch system registries, and does not leave a footprint behind when you close it.

The project was born from a simple observation: repetitive clicking is not a feature, it is a chore. And chores are exactly the kind of thing software should quietly absorb so that humans can do something more interesting.

Everything here is built around three pillars:

  1. Loop fidelity — the farming cycle stays consistent across thousands of iterations.
  2. Immediate control — a single keypress stops everything, instantly, every time.
  3. Portability — the same behavior on a workstation, a laptop, or a USB stick you carry in your pocket.

Download


💡 Why This Exists

There is an entire genre of small games where the core loop is pleasant but the repetition is not. Collecting virtual eggs, refreshing spawn points, waiting for cooldowns, re-entering a screen — individually these are trivial. Stacked together over an evening, they become a chore.

This project reframes that chore as an autonomous steward. You configure the sequence once. The steward walks the same path, again and again, with the tireless patience of a lighthouse keeper. When you want it to stop, you say the word — and it stops mid-step, no lingering, no orphaned processes, no threads left running in the dark.

The result is a utility that feels less like a script and more like a well-behaved assistant who knows exactly when to be quiet.


✨ Feature Highlights

  • 🔁 Continuous loop farming engine — configurable iteration cadence, adaptive delays, and drift correction so the rhythm never collapses.
  • 🛑 Instant stop hotkey — one binding halts every active loop, thread, and overlay in under a frame. No confirmation dialog. No "are you sure?"
  • 📦 Fully portable runtime — no system-wide installation, no registry writes, no background services. Extract, run, delete when done.
  • 🖥️ Responsive UI — the control panel reshapes itself for 4K monitors, laptops, tablets, and narrow side panels alike.
  • 🌍 Multilingual interface — 14 language packs shipped in the default build, with a translation key system for adding more.
  • 🕐 24/7 customer support — asynchronous ticket pipeline with a median first-response window under a few hours.
  • 🔧 Declarative config files — plain-text profiles you can read, diff, version, and share without reverse-engineering anything.
  • 🎯 Region-of-interest targeting — restrict the loop to a specific screen zone so other windows stay untouched.
  • 🧠 Adaptive timing — the engine measures how long each step actually takes and adjusts the next cycle accordingly.
  • 🧩 Modular action blocks — chain clicks, waits, keypresses, and condition checks into reusable sub-sequences.
  • 🪶 Featherweight footprint — idles well under 60 MB resident in typical use.
  • 🔐 No telemetry, no phone-home, no analytics — the utility is silent about you.

🧠 How the Loop Engine Thinks

Most auto-farm tools are glorified while (true) statements. This one is closer to a conductor with a metronome.

Each loop iteration passes through four internal stages:

  1. Perceive — the engine samples the current screen state within your defined region of interest.
  2. Decide — it matches the state against the active profile and picks the next action block.
  3. Act — the chosen block executes with sub-millisecond dispatch.
  4. Recover — the engine logs the delta between expected and actual duration, then nudges the next cycle to compensate.

This four-stage model is what keeps the loop stable over tens of thousands of iterations. Without stage four, small timing errors accumulate — a phenomenon affectionately called "loop drift" — until the automation is clicking into an empty screen. With stage four, drift stays bounded and the rhythm self-corrects.

The engine is also interruptible at every stage boundary, which is what makes the instant-stop hotkey feel truly instant rather than "instant after this iteration finishes."


🛑 The Instant-Stop Philosophy

If there is one design decision this project is proudest of, it is the refusal to compromise on the stop behavior.

Many automation utilities treat stopping as an afterthought — a flag checked between iterations. That means a rogue loop can keep clicking for seconds after you press stop. This project treats stopping as a first-class citizen, woven into the engine at the lowest level.

The instant-stop hotkey (default: a single dedicated key, rebindable) performs the following atomically:

  • Signals all active loops to abort at the next stage boundary.
  • Flushes any pending synthetic input events before they dispatch.
  • Closes the overlay layer.
  • Persists the current session log.
  • Returns focus to the previously active window.

The whole sequence completes in a time budget that users consistently describe as "immediate." There is no confirmation prompt because a confirmation prompt defeats the purpose of a panic key.


🏗️ Architecture at a Glance

The codebase is organized into layers, each with a single responsibility:

  • Core loop layer — the scheduler, drift corrector, and stage machine.
  • Action layer — individual action blocks (click, wait, keystroke, conditional, sub-routine).
  • Profile layer — declarative configuration loading and validation.
  • Overlay layer — the responsive control panel, status readouts, and log viewer.
  • I18n layer — language pack resolution and runtime string substitution.
  • Platform layer — thin abstractions over each operating system's input APIs.

Because each layer talks to the next through a narrow interface, the project can swap the overlay for a headless mode, or the input backend for a test double, without touching the loop logic. This is what makes the utility testable — a rare luxury in this corner of software.


💻 Cross-Platform Portability

Portability here does not mean "compiles on three platforms and works on one." It means the same profile file, copied from a Windows workstation to a macOS laptop to a Linux mini-PC, behaves identically.

Three principles enforce this:

  • No absolute paths in shipped defaults. Every reference is relative to the profile or the executable.
  • No platform-specific shortcuts in user-facing config. Timing values are expressed in milliseconds, not frames.
  • No hidden state in the filesystem. Everything the utility needs lives in the folder you extracted.

If you keep the utility on a removable drive, you can run it on any compatible machine by plugging the drive in. When you unplug it, nothing remains behind — no dotfiles, no cache directories, no leftover sockets.


🎨 Responsive UI & Adaptive Layouts

The control panel is not a fixed-size dialog. It is a fluid surface that rearranges itself based on available space:

  • On ultra-wide monitors, panels sit side by side, with the live log occupying the right third.
  • On standard laptops, the layout collapses into two columns.
  • On small screens or split-window setups, everything stacks vertically and the log becomes scrollable.
  • On narrow side panels, only the essential controls and a compact status bar remain visible.

Font scaling follows the OS accessibility settings, and every control has a keyboard-navigable equivalent so that the utility never becomes a mouse-only experience.


🌍 Multilingual Support

Fourteen language packs ship with the default build, and the string system is designed so that adding a fifteenth takes minutes rather than days.

Language packs are plain key-value files. Missing keys fall back gracefully to English rather than rendering as empty labels, so a partial translation is still usable. Right-to-left layouts are supported natively by the responsive UI layer, not retrofitted with hacks.

If you would like to contribute a language pack, the contributing guide walks through the key naming convention and includes a validation script that catches missing or malformed entries before submission.


🕐 24/7 Customer Support

Support is handled through an asynchronous ticket pipeline that operates around the clock. Because contributors are distributed across time zones, there is almost always someone awake and watching the queue. Median first-response time sits in the low single-digit hours, and critical issues are triaged ahead of feature requests.

Support covers:

  • Profile configuration questions.
  • Compatibility issues with specific screen resolutions or DPI settings.
  • Hotkey conflicts with other software.
  • Feature requests and bug reports, tracked publicly.

The support channel is documented in the issue templates so that new users find it without hunting.


⚙️ Configuration Model

Profiles are human-readable and human-editable. A minimal profile describes:

  • The screen region the loop should observe.
  • The ordered list of action blocks.
  • The stop conditions (iteration count, elapsed time, or manual).
  • Timing tolerances for the drift corrector.

Because profiles are plain text, they can be committed to version control, shared between friends, and reviewed in a diff view like any other artifact. There is no opaque binary blob, no encoded settings database, and no encrypted store. What you see in the file is exactly what the engine runs.


🚀 Performance & Resource Footprint

Scenario CPU (avg) Memory (avg) Notes
Idle, overlay open < 1% ~48 MB No active loop
Active loop, 1 iteration/sec 1–3% ~52 MB Typical workload
Active loop, 5 iterations/sec 4–7% ~58 MB Aggressive cadence
Headless mode < 1% ~22 MB Overlay disabled

These figures come from a mid-range 2024 laptop and vary with hardware, screen resolution, and profile complexity. The engine is single-threaded by design; parallelism was deliberately avoided because a predictable scheduler beats a fast one.


🔎 SEO-Friendly Naming & Discovery

Every public surface of this project — repository name, release titles, issue labels, and documentation headings — is written to be discoverable without being spammy. Search terms like egg auto farm utility, portable loop automation tool, instant stop hotkey farming assistant, and cross-platform idle game automation appear naturally in context, because those are genuinely the things this project does.

The goal is not to trick search engines. The goal is that a person searching for exactly this kind of utility finds a well-documented, honest project instead of a broken mirror.


🗺️ Roadmap for 2026

  • Q1 2026 — Profile marketplace index (read-only, community-curated).
  • Q2 2026 — Visual profile editor with drag-and-drop action blocks.
  • Q3 2026 — Plugin API for third-party action blocks.
  • Q4 2026 — Expanded language pack coverage and community translation dashboard.

Roadmap items are proposals, not promises. Priorities shift with community feedback.


🤝 Community & Contribution

Contributions are welcomed in the form of bug reports, language packs, documentation improvements, and action block proposals. Before opening a pull request, please read the contributing guide, which covers:

  • Code style and formatting expectations.
  • The profile schema versioning policy.
  • The language pack validation workflow.
  • The review and merge cadence.

Small, focused pull requests move through review faster than large sweeping ones. If you are unsure whether an idea fits, open a discussion first — it saves everyone time.


⚠️ Disclaimer

This project is provided for educational and personal-automation purposes only. It is intended to demonstrate loop scheduling, input dispatch, and cross-platform portability techniques.

Users are solely responsible for ensuring their use of this utility complies with the terms of service of any game, application, or platform they interact with. The maintainers do not encourage, facilitate, or condone the violation of any third-party agreement.

The software is provided as-is, without warranty of any kind, express or implied. The authors accept no liability for any consequence arising from its use, including but not limited to account restrictions imposed by third parties.

This repository is an independent work. Any resemblance to other projects in name or purpose is coincidental, and no code has been shared between them.


📄 License

This project is released under the MIT License.

You are permitted to use, copy, modify, merge, publish, distribute, sublicense, and sell copies of the software, subject to the conditions of the license. The full text is available here:

MIT License

Copyright (c) 2026 — Steal-an-Egg Auto Farm contributors.


⬇️ Download

Download