RedEye - OSRS Client

RedEye — Development Update & New Tester Openings
Recent results, current capabilities, and what’s next.​

Hello everyone,
I wanted to check back in with an update on RedEye and announce that I’m opening up additional tester spots.
I’ve been dealing with a fever over the past couple of days, so development has been a little slower than usual, but updates are still progressing. The client and backend have been performing well in testing, and the recent results have given me more confidence in where the project is heading.
Recent Testing Results

• Fight Caves: 8 fire capes earned with zero failures so far.
• Barrows: Fully functional in current testing.
• Sailing: 80% functional in current testing.
• Mahogany Homes: Fully functional in current testing.
• Emir’s Arena: Approximately 80% functional, currently able to reach Mithril rank. Further improvements are still needed.
• Vorkath: 2 successful kills from 2 recent attempts. The encounter is now working, with continued testing focused on smaller timing issues and edge cases.

These scripts are also practical tests of the backend itself. Each encounter exercises different combinations of movement, targeting, prayers, equipment changes, interfaces, and timing.
More Than Individual Scripts
The main goal behind RedEye is to build a capable, reusable backend and scripting API, rather than a collection of scripts that each need their own workarounds for basic actions.
The client and API already support a broad range of core systems, including:

• Navigation and travel: Global pathfinding, collision-aware local movement, world-object interactions, item teleports, and movement within instanced encounters.
• Game interactions: NPCs, objects, ground items, inventory, equipment, dialogue options, and in-game interfaces.
• Banking and supplies: Bank access, automatic bank PIN handling, deposits and withdrawals, inventory checks, and Grand Exchange purchasing and collection for restocking.
• Combat controls: Targeting, equipment and ammunition changes, prayer management, spellcasting and autocast, food, and potion use.
• Live game-state access: Player and NPC state, animations, projectiles, ground effects, skills, and quest-state information that scripts can use to respond to changing conditions.
• Client management: A dedicated launcher, account and character settings, script controls, and diagnostic logging to help identify and reproduce issues.

Based on the results so far, I’m confident that the API provides the foundation to support almost any scenario in the game, with focused additions where unusual mechanics require them.
That is broad API capability—not a claim that every boss, quest, or activity already has a finished script. Individual content still needs its own logic and testing.

Current Development Priorities
My next priorities are 1-tick prayer support and cleaning up the backend to remove unnecessary action and walking delays. I’m also continuing to refine equipment-switching speed and the transitions between movement and combat.
The focus is on making these improvements available through the shared backend and API wherever they belong, so other scripts can benefit without having to reinvent the same functionality.
Scripts should focus on what they need to do. The backend should handle executing those actions reliably and efficiently.

Additional Tester Openings
With the progress made so far, I’m comfortable expanding the tester group. However, I’m still being careful about who receives access and will continue selecting testers individually.
I’m looking for people who can test consistently, communicate reliably, and provide useful feedback—including clear bug reports and helping verify fixes.
Interested in testing? Reply to this thread. A brief introduction and the content you would be interested in testing would be helpful.

I’ll contact selected applicants directly. If you don’t receive a message, you haven’t been selected for this round. Replying expresses interest but does not guarantee access.
Thank you to everyone who has followed the project and contributed feedback so far. There is still work to do, but RedEye is making steady progress, and I’m looking forward to putting it through a wider range of testing.

 

Sup, been in the botting scene for 10+ years, have made some simple plugins/scripts so well aware to read logs etc so willing to test some stuff if needed, I have quite a lot of different accounts so can try majority off the content

 

I will no longer be accepting new testers. Multiple users have shown interest and have said multiple times they will be ready this day or that day and then never respond. So with all these contradicting results it will be staying a closed private project between me and my one reliable tester.

It's a bit sad that a project that is not asking for any money can't get any proper support or testers. My client is already performing multiple mini games, all quest, f2p, p2p, and ironman support. I have completed over 500 vorkath kills fully automated, fight caves completed 10 times with no failures and it was all being provided with the client. I even have something new that completely changes the meaning of early game testing to eliminate any failures before it's experienced in an official world and risk a ban.

But as this is wrapping up for public testing use just know it's still being actively developed behind the scenes and one day will be released.

 

ill check it out if you want genuinely just msg me your cord or w/e