Soulrift Auto Attack / Auto Kill Boss

This page documents one Soulrift injector: auto attack, auto skill, and auto kill boss, with a listing note that you need one teammate or the boss can bug. It is keyless and marked mobile-ready on the listing we mirrored. It is not an helix_works feature. Parent: scripts hub. The other circulating GUI is combat GUI (inf money, key system).

What it claims to do

Instead of you pressing M1 and Z/X/C (controls), the script fires attacks and skills and tries to finish the boss. That sounds like a skip for beat bosses. The teammate requirement is the catch: Soulrift encounters are built for up to eight players, but this particular loader is documented as unstable if you are alone. A bugged boss can stall quests including Awakening and Burning Soul.

If your goal is Clockwork or Scar, a bugged instance is worse than a slow legal clear. Quest roster.

Loadstring

loadstring(game:HttpGet("https://api.jnkie.com/api/v1/luascripts/public/565de60697cde86eae41efdf88eec43c66fe632e01b2d88e99da1f9cf2a31c3b/download"))()

Paste only in a client you already chose to use. We will not name or teach executors. If the HTTP endpoint dies, the script is dead; we will not replace it with a random GitHub alt.

How this interacts with the rest of the game

• Difficulty slider: auto-kill on a high tick still needs the instance to function. Boss difficulty.
• Shuffle Mode: random encounters plus auto-kill plus a required teammate is extra entropy. Shuffle Mode.
• VIP: a multiplier on legal income. This script is not VIP. Gamepasses.
• Codes: still none. Codes hub.
• Accessories / shop: auto-kill does not teach you which slot to fill. When you stop using it, you will still need getting started habits.

Ban and malware notes

Any executor can be a credential stealer. Prefer not to run this on an account with limiteds, gift cards, or a long badge history. helix_works can patch detection without a blog post (patch notes).

Auto-kill in an eight-player public server also griefs people who wanted to play. They queued for a boss fighter, not a AFK farm. Use a private friend group if you insist, and still expect bans.

Legal alternative loop

1. One teammate who actually plays Reviva or Clockwork — team comps.
2. Lowest tick until Dash is automatic.
3. Souls and XP milestones.
4. Unlock planner for Reviva/Sunder.

That loop is slower and keeps the account. This script page exists because searchers will find a loader anyway; they should see the teammate warning in the same place as the loadstring.

If a new auto-farm appears with a different URL, it gets its own page only after we confirm the place ID matches Soulrift — not a similarly named “Rift” game.

When the teammate clause bites

If you fire auto-kill in an empty instance, the listing already told you the boss can desync. That is not a “skill issue,” it is the advertised failure mode. A desynced Greater Heights or Burning Soul night wastes more time than playing Reviva legally. Public auto-kill also trains other players to report you. If you still run it, do it with a consenting friend who understands they might get nothing from the quest chest.

Mobile-ready on a listing does not mean undetected. Phone executors get the same bans. If the auto-kill GUI covers Dash, you cannot take over when the teammate leaves. Practice the legal binds anyway so a crash does not leave you helpless in a public eight-player instance.