Why these scripts beat the daily rewrites
+1 Poor To Rich is an incremental simulator from XL C0MMUNITY. The loop is begging and walking for Cash, glow-ups that visibly transform your character, Rich Level milestones that mint Wins, and a rebirth tree that recycles Wins into a permanent multiplier. The grind is the whole point — and the moment a Roblox simulator gets a grind, the third-party aggregators light up with auto-farm builds. Most of those listings are duplicates of the same two or three loaders dressed up under different hub names, with stale loader URLs and copy-pasted "NEW OP NO KEY" titles that have not been a working description of any of these scripts since 2024.
The list on this page is the curated subset. Every entry below was pulled from a third-party listing sweep that ran in the last 24 hours, the loader URL was probed for a live HTTP 200 before publish, and the title was rewritten so it leads with the hub name rather than the game name. Patched and dead builds drop off the working table the same hour we detect them. If you came here from a search result and the entry above carries a green Working badge, that badge was true within the last few hours, not last year.
How to run a script in +1 Poor To Rich
Same flow every executor, four steps:
- Install an executor. Solara, Delta, Krnl, Hydrogen, and CodeX are the names you will see in the Executors column on each entry. Install the one you already own; do not pay for a new one to try a free script.
- Launch +1 Poor To Rich from the Roblox app and let your character spawn at the starting begging spot. Some loaders fail in the lobby — wait until the HUD shows the Cash counter.
- Attach the executor to Roblox, paste the snippet from one of the entries above into the executor's script box. The Copy button on each card lifts the snippet exactly as it needs to be pasted.
- Press Execute. Most builds open their menu on first run; key-system builds open a gateway prompt first. Follow the gateway flow once per key window, then return to the menu and toggle the auto-farm modules you want.
If the menu does not appear within five seconds, try a freshly-opened server. Long-running servers sometimes cache stale module state that breaks first-run loaders.
What auto-farm and rebirth-loop means in +1 Poor To Rich
The terminology on this page is specific to incremental simulators and to this game's loop in particular.
- Auto-farm Wins. The script walks the character in a tight pattern around the highest-density begging spot, collects the step-based Cash, and converts at the Rich Level conversion thresholds. The Wins counter ticks up automatically.
- Auto-train. A subset of auto-farm that focuses on raw Cash output rather than Wins milestone hunting. Useful in the first 30 minutes of a fresh run when glow-up tiers are cheap and the Cash-per-step rate is the bottleneck.
- Auto-rebirth. Once the Wins counter crosses a configurable threshold, the script spends the Wins on the rebirth tree and resets the run. The permanent multiplier compounds across rebirths.
- Glow-up auto-buy. Some builds will purchase glow-up tiers as soon as Cash crosses the next gate. This is the difference between a slow Cash-stockpile run and a constantly-progressing run.
- Mobile build. The loader UI is sized for touch and the executor lookups in the snippet include the mobile-only
requestfunction names. Delta, CodeX, and Seliware are the most common mobile-friendly executors.
The compatibility markers on the comparison table grep the Features lines literally — if an entry says "Mobile UI build" the table shows a mobile mark, if it says "Key system" the table shows a key mark.
When scripts get patched
+1 Poor To Rich is in its early growth window. The game was published on 2026-04-12, has crossed 3.4 million visits, and is still receiving updates roughly every 10 to 14 days according to the changelog pinned in the Roblox game description. Every patch is a potential script-killer in incremental simulators, because the developer usually adjusts Cash-per-step rates, Wins thresholds, or glow-up gating between updates.
What that means for the entries on this page:
- Working scripts have been verified at least once in the last seven days against the current game build.
- Patched is the flag we apply within the hour of detecting that a loader 404s, that the script throws on attach, or that two of the patched-detection signals fire.
- Dead is the flag when the upstream loader has been deleted entirely by the author.
The page re-runs the listing sweep automatically. When a fresh build for a hub already on this page shows up in the upstream sweep with the same hub name and a newer date, the existing entry is updated in place rather than duplicated. That keeps the list from inflating into a 30-row mess every patch cycle.
Risk and ban policy
Running any script in +1 Poor To Rich violates Roblox Terms of Service and the game's own fair-play rules. The realistic outcomes:
- Account-level moderation — Roblox's detection systems have been making increasingly accurate calls in 2026 against repeated executor behaviour, especially on accounts with no payment history. A clean main account that suddenly farms Wins for eight hours is more visible than a fresh throwaway running for an hour.
- In-game soft bans. Some Roblox games kick or shadow-ban accounts that hit suspiciously-high progression curves. +1 Poor To Rich's rebirth counter is the metric most likely to trigger an anti-cheat heuristic, because organic players climb the rebirth ladder unevenly while auto-rebirth builds climb it linearly.
- Loader content risk. The loader URLs above all resolve cleanly today, but they all run obfuscated or semi-obfuscated Lua on your executor process. That code can in principle do anything the executor permits, including reading clipboard, dumping cookies if your executor exposes them, or calling out to a Discord webhook. The mitigation is simple: throwaway Roblox account, no in-app payment method linked, executor sandboxed if your build supports it.
What we will and will not do as an editorial team:
- We will rebuild loader URLs to point at the canonical upstream (GitHub raw, Pastebin raw, gist) rather than at any aggregator wrapper that could rot or rebrand.
- We will not host loader bodies on bloxyblox.com or rebrand any script as a bloxyblox property. Every snippet on this page points to a third-party upstream, and the View source link on each card resolves to the actual host.
- We will flag patched and dead entries within the hour of detection.
- We will not keep dead loaders on the working table to pad the list. If three days pass and nothing has reappeared, the entry moves to the dead section.
If a script on this page does not resolve for you, hit the report widget on the card. Two independent reports within 60 minutes flip the entry to patched automatically.
Recent changes
- 2026-05-24 — First publish. Three working entries added (Inertia Hub, 25MS Hub, Auto-Wins Loop) after the upstream listing sweep. One candidate rejected for returning a hard 404 from its aggregator wrapper.
+1 Poor To Rich scripts FAQ
Is the +1 Poor To Rich script safe?
There is no truly safe script on Roblox. The loaders on this page resolve, the upstream hosts are public, and the editorial team has rejected anything that 404s. That removes the obvious junk. What it does not remove is the residual risk of running obfuscated Lua on an executor process — always use a throwaway account, never sign into a Roblox account with a linked payment method while an executor is attached.
Do these scripts work on mobile?
Yes, on builds explicitly tagged Mobile build in the entry features. Inertia Hub, 25MS Hub, and most touch-friendly executors (Delta, CodeX, Seliware) handle the mobile path. The Auto-Wins Loop entry is single-file and not packaged with a mobile UI — it runs but the menu may be hard to interact with on a phone.
Best free +1 Poor To Rich script with no key?
The Auto-Wins Loop entry is the no-key option on this page today. Inertia Hub and 25MS Hub both gate execution behind a key system that runs through the upstream's own gateway flow.
Why did my +1 Poor To Rich script stop working?
The most common reasons, in order: a patch from XL C0MMUNITY moved the Cash-per-step coefficients (the loop module needs an update from the author); the upstream loader was deleted; the executor pushed an update that broke its request shim; or you are in a long-running server with stale module state. Hop a fresh server and try again before reporting.
Which executor should I use for +1 Poor To Rich?
Solara, CodeX, and Delta are the most commonly listed in the Tested badges from the upstream listings. Krnl and Hydrogen both work but show up less often in tester comments. Pick the one you already own.
Can I get banned for running a +1 Poor To Rich script?
Yes. The realistic risk band is account-level moderation if the script runs unattended for many hours on the same account. Throwaway accounts mitigate this. There is no script we list that can guarantee you will not be flagged.
Will my Wins from a script persist if I switch back to manual play?
Yes. Wins and rebirth progress write to your Roblox player data the moment they unlock. Switching the executor off after a long farm leaves the accumulated state in place. The risk in that flow is that the asymmetry between your farm rate and a fresh organic player's rate is exactly the signal anti-cheat looks for.
How often does this page update?
The listing sweep runs every four hours. Working badges refresh during that sweep. Patched and dead flags can fire faster if a report comes in via the on-card widget.
What if a script has a key system?
Follow the upstream's own gateway flow. Almost all key systems in 2026 use a linkvertise-style or ezkeys-style gateway that hands out a 24-hour key. Paste the key into the script when it prompts. The key is bound to your HWID, not your Roblox account.
Can I run two of these scripts at once?
No. Both loaders attach to game:GetService("Players").LocalPlayer and both try to control your character. Running two will cause one or both to misbehave or crash. Pick a single entry per session.
About this page
Author: BloxCodes Hub editorial team. Methodology: third-party listing sweep every four hours, loader-URL HTTP probing on every new candidate, hard-404 rejection, manual editorial title rewrite, and weekly re-verification of every working entry. Last full editorial review: 2026-05-24.
The compatibility table, executor list, and feature markers on each entry above are generated from the entry payloads in the database — they are not separately hand-edited. If a fact on this page becomes wrong after a +1 Poor To Rich update, the update note will appear in the Recent changes section first.