RugPlay Manager has reached a stable state — v2.0.2 is here! #2
DidCodeHere
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone,
Wanted to take a moment to share that RugPlay Manager has officially reached what I'd consider a stable, reliable state. It's been a journey getting here and v2.0.2 wraps up a lot of the work that needed to happen before I could confidently say that.
What changed between v2.0.1 and v2.0.2?
The short version: sentinels actually work properly now.
v2.0.1 was the first public stable release and it shipped with a solid feature set, but the sentinel system had some real problems under the hood. If you've been using it, you might have noticed things like sentinels triggering immediately after a re-buy, duplicate rows piling up, or sells just silently failing. Those are all fixed now.
Here's what v2.0.2 addresses:
Sentinel reliability — The trigger logic has been completely rewritten into a unified evaluation system. There's now a 120-second grace period after sentinel creation to prevent instant triggers from stale entry prices. Error handling is smarter too — rate limits, zero-balance coins, and pool-limit errors are all handled differently instead of being treated the same. Triggered and duplicate sentinels get cleaned up automatically.
Research-backed defaults — I ran ~189,000 backtests across 875 coins testing 216 different stop-loss/take-profit/trailing-stop configurations. The results are compiled directly into the binary. The new defaults (SL -30%, TP 500%, trailing stop off) come from that data, not guesswork. There's a whole About page that breaks down the findings if you're curious.
Sentinel UX — Search, sort, filter tabs, coin icons, transaction tooltips on hover. Managing 60+ sentinels is actually usable now.
Portfolio integration — Coins with active sentinels show a shield icon in your portfolio. Hover it to see the config, click it to jump straight to that sentinel.
Reset to defaults — One click to reset sentinel or DipBuyer settings back to the research-backed balanced config.
Can I still use v2.0.1?
You can, but I wouldn't recommend it. The sentinel trigger logic in v2.0.1 has known issues — duplicates, instant triggers, and silent sell failures that have all been resolved in v2.0.2. If you're running sentinels at all, you should update.
Downloads
Grab the latest from the releases page. Windows (NSIS + MSI) and Linux (deb + AppImage) are both available.
Stay updated
If you want to know when new versions drop, hit the Watch button at the top of the repo (you can filter to just releases if you don't want all the noise). And if you find the project useful, a Star goes a long way.
Full changelog is in CHANGELOG.md if you want the full details.
Thanks for checking this out.
Beta Was this translation helpful? Give feedback.
All reactions