How Little Helper works
Little Helper: Wild Protocol is a pixel survival game with a robot companion at its centre. You land in the wilds, find a small broken machine, and repair it. From that point the game is about delegation: you gather branches and stone to keep yourself alive, and you teach the helper to gather, haul, craft and fight so you can push further into dangerous ground. It is not a farming sim and not a twin-stick shooter. Hunger drains, night falls, and the region you cannot survive alone is exactly the region the helper was built for.
Four regions open in sequence. A sunlit meadow holds the camp and the first resources. Dense woods hide timber, resin and wildlife. Rust-red pits carry iron, copper and coal behind narrow paths and falling rock. A derelict facility holds scrap, old batteries and control parts, guarded by machines that still think they have a job. Regions connect on foot through gates; there is no fast travel. Every region is generated from a seed, has guaranteed spawns for story-critical materials, and is checked for reachability so a bad roll cannot block the run.
Companion, goals and automation
The helper comes in four stages — infant, assistant, steward, full agent — each faster and able to carry more, with more tasks running at once. Three specialisations cover gathering, crafting and guarding, and the total number of specialisation points in a full run is five, so one playthrough cannot max everything. Instead of scripting every step you set an objective such as "keep 50 timber in storage, work the woods, normal priority, return to camp and recharge at night". The helper plans the route itself: find the node, fill its pack, deliver to storage, refuel the machine, wait for processing and collect the output, breaking components down to a craftable root up to four levels deep. When it fails it says why — "I don't know where copper is yet", "storage is full", "that machine is busy" — pauses, and moves on rather than grinding at a wall.
Automation is not free. The helper burns power and needs charging, it can be damaged and must be rescued, and every task you hand over is a task you are no longer doing yourself. That trade is the whole game, and the ending is the bill for it.
Survival rules
Health and hunger both start at 100, and hunger drains slowly all day. Death sends you back to camp with your equipment but drops part of your ordinary materials — and only one death cache exists on the map at a time, so an old cache merges into the new one instead of being lost forever. Day lasts five minutes, dusk one, night two, and the night is genuinely dark outside the pools of light from a campfire, torch or glow sac. Panels pause the world while you read them, and the simulation stops when the tab is hidden.
Controls
On desktop, WASD or the arrow keys move, the left mouse button attacks, E interacts with nodes, chests and relay towers, Space dodges, and T, I, M, B and Esc open the command panel, bag, map, compendium and pause screen. On a phone the left side is a virtual stick and the right side carries attack, interact and dodge, with every touch target at least 44 CSS pixels and clear of the safe area. Portrait and landscape both work.
How it differs from other survival games
There is no base-building sandbox with free rotation and no multiplayer. Progress is a six-chapter line with a fixed arena at the end, not an endless map. The automation is deliberately bounded: the helper works inside the areas you have discovered, cannot be sent through unexplored ground, and never permanently dies. And the boss at the end is not an ancient evil — it is your own helper, wearing the specialisations you chose and the work habits you taught it. The build is self-contained: no ads, no account, no download, and the pixel art and sound are generated in code.