Instructions

1 Initial Setup

1.1 System Requirements

• Windows 10 or 11.
• On Mac or Linux, you can run Genesis using a virtual machine. All the resources you need are here.

1.2 Download

Genesis is free to download and free to run for one hour a day. You don't need a subscription to start — every account gets that hour, and it resets daily.

Download RiD-Installer.exe

Botting for longer than an hour a day is what a subscription buys: 6 hours a day on Light, 18 on Heavy, 72 on Ultimate. Your bots, calibrations and settings are the same either way — the only difference is how long you can run them for, and how many at once: one bot at a time on Free and Light, three on Heavy, six on Ultimate and ViP.

1.3 Install & Run

Run RiD-Installer.exe. Select the folder you'd like to install Genesis to, then click through the setup. At the end there's a checkbox to add a desktop shortcut — tick it if you want quick access. Once the installer finishes, launch RiD.exe from the install folder or your desktop shortcut.

1.4 Required GFX Settings

Genesis is graphics based, and ready-made Environments can be installed from the Environments tab (see 2.1). You can create Environments for other applications too. But for a ready-made Environment all you need to do is make sure you have the Required GFX Settings »

1.5 Minimizing (optional)

You can run Genesis minimized, using a Virtual Machine (VM). Here are instructions for setting up:

• Stokee RiD Guides — Create a Lightweight VM for Botting

2 Bot Creation

2.1 Environments

To get the best out of Genesis, you must first show it what the application's GUI looks like. We do this by setting up an 'Environment': what the buttons look like, where they are on screen, along with special GUI components like the compass, map and world view. Ready-made Environments are available to install, so most users never need to create one. The first time you open Genesis it takes you to the 'Environments' tab: just pick your Environment and press 'Install'.

Once installed, select your Environment from the drop-down menu at the top of the window.

When an Environment you have installed is updated, Genesis lets you know on the message bar at the top of the window. Your bots keep the version they have until you choose to update, and Genesis warns you first if the update would remove anything one of your bots uses.

Changes you make to an installed Environment are kept as your additions, apart from the Environment itself, so its updates never overwrite them; a set of them can be made into an add-on and published for other people to use. A bot of yours carries whichever of your additions and add-ons it uses — decided each time it is saved or started — and they go with it when it is shared, so whoever downloads it has nothing extra to install. Add-ons other people have published for an Environment are listed under it on the Environments tab; get one and it is offered to every bot you make. See Your Changes Stay Yours in the Environment Editor guide.

If you do need to build or adjust one — an application with no Environment, a variant that differs from the original, or a component the shipped Environment is missing — see the Environment Editor guide » To make a new one, pick '< new environment >' at the bottom of the drop-down.

2.2 Brief Overview

There are three simple steps toward creating a bespoke bot with Genesis, and no programming knowledge is required. From the 'My Bots' tab, press '+ New Bot', then: (1) name your bot, (2) set up navigation, and (3) calibrate.

Instead of calibrating, you can also press 'Build Manually' to build a bot by hand in the Machine GUI — and from there, 'Load from bot' on the General tab starts it as a copy of one of your other bots.

2.3 Navigation

Navigation is optional, and only matters if your Environment has a map and you want to move between locations. Stationary bots don't require a map. To create a map, press the 'Create Map' button, then simply walk around the area(s) you want to operate in. Alternatively you can use the 'Load Map' button to load a map from another Genesis bot on your local machine. (The map step only appears if your Environment has a map.)

After map creation, you will see a map of the area with the path you walked highlighted in cyan. Make sure the path is correct before you continue (if not, try again walking more slowly). It should look something like this:

A map is made before calibration, and once your bot is calibrated it can't be replaced — but it can be extended. Press 'Add to Map' on the General tab of the Machine GUI and walk the new area. This is also how a bot you built manually gets its first map.

2.4 Camera Settings (aka 'blue grid')

Prior to calibration you must set Camera Settings. You can also adjust camera settings post-calibration (with 'Update' in the 'Camera settings' section above the Start button), so you don't need to run the bot with the exact same camera settings you calibrated with. Each bot remembers its own, so if you run different bots at different zoom or pan you only set each one once. Camera settings simply allow the bot to coordinate between locations on the map and tiles in the 3D world. It doesn't need to be perfect, but wildly inaccurate Camera Settings will lead to errors, so don't skip this step. Click your character to center the grid on it (the grid turns from amber to blue), then adjust zoom and pan until the grid matches the tiles on screen.

Tip: if nearby tile centers aren't clear, drop a few items nearby to see more clearly.

2.5 Calibration

Genesis learns repetitive tasks, and your biometrics, by watching you perform them. This process is referred to as 'Calibration' and results in an editable blueprint of the task (see Machine GUI) that is unique to you at the biometric level. It is a good idea to read the Calibration Tips below first.

A countdown will pop up. Once it reaches zero, perform 5–10 repetitions of the task, then click 'Finish!' Now wait a minute while Genesis creates a bespoke bot from your calibration data.

Once it is created, your bot is uploaded for sharing automatically, with your own biometrics stripped first — see Sharing your Bots. There is no re-calibrate button: to calibrate again, create a new bot.

2.6 Calibration Tips

• Your task should have a repetitive nature — do not deviate from the task during calibration.
• You MUST perform at least 5 full cycles of the task (or 5+ minutes if cycles are short).
• Excessively long calibrations have an increased chance of error.
• Anything in the 3D world you interact with (World Items) ought to have clear outlines.
• If you want to use Navigation (walk around) you must create a map of the area before calibration.
• It is recommended to navigate using the mini-map.
• If using the world view to navigate, try to click plain areas without foreground (so the bot doesn't think you are clicking an object).
• You may rotate the camera during calibration (left or right), but don't adjust pan (up or down) or zoom. And be consistent — use the same angle(s) on each cycle. For example: you want to turn east to click the bank, and west to click the furnace... then face east for all your bank clicks and west for all your furnace clicks, every cycle.
• A top-down camera pitch works best, and avoid extremes with zoom (too far or too close can both cause problems).

2.7 Running Your Bot

Select your bot on the 'My Bots' tab. Everything for the run is in the column on the right:

• Run for — how long to run, in minutes or completed cycles. Set minutes to -1 to run until you stop it (or until error).
• Camera settings — see 2.4.
• Advanced Options — your account login (so the break handler can log you back in), Fatigue (leave it on: it is what makes Genesis take breaks, rests and lapses of attention), Logout on Break and Thread Priority.
• Monitor this run with AI — see 6.1.
• Start runs the bot now. + Queue adds it to your plan instead, and Plans... opens the plan editor: bots and breaks in order, each for a range of time (60-90 minutes, say), saved to use again. A plan runs unattended, one step after another, and Start then reads ‘Start Plan’.

If Genesis spots something about a bot, or about how it has been run, that could give it away (very long days, for example), a warning triangle appears beside Start. Hover over it to read the warning, or click it to open the bot's Biometrics. For the most serious ones, the first press of Start shows a note and a second press goes ahead. The 'Biometrics' button on the bot's card compares your runs with your calibration, once the bot has run.

3 Bot Editing

3.1 The Machine GUI

Each bot you create with Genesis has its own 'Machine', which can be edited! Editing is done from the 'Machine GUI', which opens automatically immediately after calibration. The Machine GUI can also be reached by selecting your bot and pressing the 'Edit' button. Actions are represented by Orbs, and they are connected by Arrows which represent the action sequence — the order in which to perform actions. Drag the middle of an orb to move it, or drag from its outer ring to another orb to draw an arrow. Arrows are coloured by when they are taken, and small badges on an orb point out things worth a look — see 3.5.1 Reading the Graph, or hover over Key at the top-right of the Machine GUI.

3.2 Genesis at Runtime

The typical cycle of the bot at run-time is: (1) select action, (2) perform action, (3) confirm action (otherwise try again), (4) finish action, then repeat back to (1). You have control over this entire process through the Machine GUI. There is also an error-handling mode, where the bot will attempt to identify the appropriate action based on current status (this cannot be influenced by the user). Error handling only occurs when the regular cycle fails.

A bot can also be set to run once instead of repeating: from a start action, following the arrows, until it reaches an end (an action with no arrows leading away). This is useful for getting somewhere — walking to the bank, say — before the next bot in a queue starts. Set it under 'How it runs' on the Machine GUI's General tab.

3.2.1 — Work Within Genesis, Not Around It

Genesis is the expert on human-like play. Your bot says what to do and when; Genesis decides how. From your own recorded play it already supplies, every time:

• the pause before each next action, and the mouse movement, aim, click and typing rhythm;
• a retry when an action's Confirm conditions don't arrive;
• finding its place again from the screen when it gets lost;
• breaks, short rests and lapses of attention, drawn fresh every session (while Fatigue is on);
• variation from one run to the next.

So never build any of that out of actions and arrows — no wait actions between clicks to slow the bot down, no retry loops or counters, no 'start over' paths, no break actions, no random branches to look human. Each of these replaces your own recorded play with the fixed rhythm of a script, which is exactly what you don't want. Instead, each kind of change has its place:

3.3 Action Options

There are two options for 'Action Style': Action and Reaction. Actions will only be performed sequentially, whereas Reactions can occur at any time in the action sequence. Genesis will return to where it was in the action sequence after a Reaction is finished — unless there are arrows leading away from the Reaction orb, in which case Genesis will continue from those arrows instead.

Immediately after an action is performed, Genesis begins checking for the 'Action Confirm' conditions. If they are not found, it will make another attempt. If they are found, it proceeds until the 'Action Finish' conditions. With no Confirm conditions the action is assumed to have worked unless the click itself was seen to miss — fine where nothing on screen reliably changes within a few seconds of the click, but for an action that then waits for a Finish condition a Confirm is worth adding wherever a quick sign exists (the avatar sets off, a panel opens, an inventory count changes): without one, a misclick the bot did not notice idles out the whole 'Give up after' time before it tries again. If you have Finish conditions, there are three timing values: (1) 'Not before' — the next action never happens sooner than this after the click, (2) 'After the finish' — how long after the finish is seen the next action happens, and (3) 'Give up after' — if the finish has not been seen by then, the action is treated as failed and tried again. If you have no Finish conditions, the action finish is decided purely on timing — Genesis picks an appropriate duration using your min, typical and max values. Leave a timing box blank to use the timing from calibration.

Choose each condition by what it means. The ideal Confirm condition happens straight away after the click — for example a mining plugin’s status text switching to ‘ON’ as mining starts, a bank window opening, or your character setting off. The ideal Finish condition signals that the action is complete — that plugin text switching to ‘OFF’, the rock disappearing, or the ore arriving in your inventory when one click gives one ore. A Finish condition is especially valuable for actions that take a varying amount of time (mining, woodcutting, fishing, walking): without one the action is purely time based, so the bot waits out its drawn time when the game was quick and moves on too early when it was slow. The same condition can go on both lists when it is both quick and the end of the action — it then confirms and finishes the action at once, and calibration often sets it up that way. Take care with a count going up when one click can give several (a rock that keeps giving ore until it runs out): as a Finish it would end the action at the first one, so finish on the rock disappearing or a status turning off instead.

Timing measured at calibration is what makes the bot's pace read as yours, so leave it alone unless an action really needs it changed for a reason in the game — a click that fails because the next one comes too soon, say. 'Faster' is not such a reason, least of all on an action the bot repeats in a short loop (casting a spell on item after item), where the same gap is drawn thousands of times an hour. If you do change one, Genesis keeps the measurement and reshapes it to your numbers, marks the orb with a yellow clock, and offers Restore ('Measured timing changed') to put it back exactly as measured. A red clock means the timing is too fast or too exact to look like a person. And a pause after an action is that action's own timing — don't add a wait action after it.

Pause Exempt stops Genesis taking a break (or a rest, or a lapse of attention) straight after the action. It is for an action that fails if it is separated from the next one — selecting a spell before clicking what it is cast on, say — or an action that repeats itself, like dropping item after item. Don't use it to make a bot faster: if every action (or every action of a loop the bot goes round) is exempt, Genesis never takes a break at all, and the Machine GUI and Start both warn you in red.

World-Item clicks (NPCs or other objects in the world view) include an option for 'Compass Angle' (if there is a preferred viewing angle — the 8 options are N, E, S, W, NE, NW, SE, SW) and 'Hover-Text' (if colored text appears at the top of the world screen when you mouse over the world item). Hover-Text is optional; if you select a color for Hover-Text, the bot will not click unless it sees the selected color text after it moves the mouse to the target.

3.4 Conditions

Conditions are mostly (but not limited to) observations made on screen at runtime — some examples: inventory becomes full, you arrive at a location, an NPC appears on screen. Conditions are used in three scenarios: (1) Action Confirm, to determine if an action is successful or not, (2) Action Finish, to signal when to end an action and move on to the next, and (3) Arrow Conditions, used for action selection and decision-making based on what is on screen. You can edit all three types. The first two you edit from the action orb; Arrow Conditions you edit by clicking on the arrow itself. You can also create new arrows between orbs by dragging from the outer ring of the source orb to the destination orb. To delete an arrow, click the arrowhead in its middle to select it, then press Delete.

3.5 Decision Making

After an action finishes, Genesis selects the next action by examining the arrows available from the completed-action orb. Each arrow can be assigned conditions, all of which must be true for the arrow to be considered. Where multiple paths are available, the bot selects based on probabilities. Genesis will also consider 'Reaction' orb conditions, and will prioritize Reactions ahead of ordinary arrow pathways. Arrows with no conditions are a special case: they are lower priority, and will only be selected when no conditional pathways are available.

That makes an arrow with no conditions the action's default — the usual next step. Every action with arrows leading away should keep one: arrows are checked once, when the action finishes, so if every arrow has a condition and none of them holds, the bot is left with nothing to do and has to work out where it is from the screen.

Sometimes one action should lead to the same next action for more than one reason — bank when the inventory is full or when the timer runs out. Select the arrow and press + Another way (OR): each way has its own conditions, and the arrow is taken when any one of them holds. The arrow pane shows 'Way 1 of 2' with arrows to step between them. Before adding one, check whether a single condition already says it: 'free inventory space is 0' covers every way the inventory fills. An OR is for two genuinely different reasons to make the same decision. (An action's own Confirm and Finish lists are already 'any one of these' — just add more conditions to the list.)

A few more habits that keep a bot reliable:

• Prefer what the screen shows — a component, an inventory count, a world item, a map location — over counters and timers. A reading follows the game; a count does the same thing the same number of times every session.
• If an action should wait for something before deciding, that is a Finish condition on the action, not a condition on every arrow out of it. Nothing waits for an arrow's condition to come true.
• Don't add random branches or weights to look human — that variation is already there (3.2.1).

3.5.1 — Reading the Graph

The colour of an arrow tells you when it is taken:

• Green — the default: taken when no other arrow out of the action holds.
• Blue — taken only when its conditions hold.
• Blue with dark stripes — several ways (OR): taken when any one of them holds.
• Blue with green stripes — several ways, one of which has no condition, so it is also the default.
• White — the arrow you have selected.

When you select an action, the arrows leading away from it are drawn over the other orbs and a little brighter, so you can follow them on a crowded graph. Hovering over an arrow also says what kind it is, on the line along the bottom of the graph.

An orb is teal, and green while it is selected. Its outline says where the action's mouse movement and timing (its 'hand') came from:

• No outline — recorded from your own play when you calibrated.
• Green orb — the action you have selected.
• Amber outline — borrowed from another bot you calibrated yourself. Typical of an action you added by hand, or of a downloaded bot: Genesis lends it your own hand automatically.
• Red outline — nothing recorded to go on, so Genesis uses a generic hand. Calibrate a bot of your own and Genesis lends its hand to these actions instead (they turn amber).

Badges on the rim of an orb point out something about that action. Hover over the orb to read the reason on the bottom line:

• Orange fork — no default arrow: every arrow out of this action has a condition. Give one of them none.
• Yellow clock — the action's timing has been changed from what calibration measured.
• Red clock — the timing is too fast, or too exact, to look like a person.
• Linked rings — this action does the same job as another and could be one step with it. List view offers to join them (see 3.7.5).

The same key is in the app: hover over Key at the top-right of the Machine GUI, or click it to keep it open.

3.6 Special Conditions

3.6.1 — Control Flow Variables

Control Flow Variables are conditions that make your bot repeat a sequence of actions X times. There are two types of control flow conditions: (1) increment (increase) an integer value, and (2) check an integer value.

Say you want to cast a spell 4 times in a row then click a bank chest, and you already have these two actions set up. Set an arrow from the spell action back to itself with the condition 'Control Flow Variable: increment A', and an arrow from the spell action to the bank chest action with the condition 'Control Flow Variable: A = 4'. Each time the bot performs the spell it increases A, until A = 4, at which point it moves to the bank chest action and resets A back to zero. If you have multiple actions in your repeatable sequence it works the same way: put an 'increment A' at the first step (arrow) of the sequence, and the 'A = X' condition on the arrow that exits the loop, where X is the number of times you want to perform the loop.

An arrow that only increments a variable still counts as having no condition, so here it is also the spell action's default (green). Use a count when the number really is fixed by the task. Where the screen can say it instead — 'inventory full', 'no runes left' — use that: a count does the same thing after the same number of cycles every session. And never use counted loops to make pauses or breaks (a pause after exactly every 200th cast is a pattern, not a person); Genesis takes its own breaks.

3.6.2 — Timers

Similarly to control flow variables, there are two types of Timer conditions: (1) Start Timer, and (2) Timer = Finished. You need to set up both to get it functioning. First create a 'Start Timer' condition, give the timer a name and set three values: the minimum, average, and maximum value (in milliseconds). It's usually good practice to set your min and max around 10% below and above the average — so if your average was 100ms, then 90ms and 110ms would be a good min and max, depending on what you're aiming for.

Say you have an auto-fighter and want to modify it to drink a potion every 2 minutes: create a 'drink potion' action, and link it to the 'attack' action with two arrows, one going to and one going from the 'drink' action. Put the 'Start Timer' condition on the arrow that goes back from 'drink' → 'attack' (this starts/resets the timer after the drink action completes). Set the average time to 120000 milliseconds (2 minutes), with a suitable min and max. Now put the 'Timer Finished' condition on the arrow that goes from 'attack' → 'drink' (this tells the bot to check the timer after each attack completes — if the timer has expired, it moves to the 'drink' action).

Timers are for things the game itself puts on a clock, like a potion wearing off — not for pacing the bot between two actions (that is each action's own timing, 3.3). If you still want a pause of your own as well as Genesis's breaks, start it from a timer with a wide range, never from a count, and leave Fatigue on beside it.

3.7 Bot Editing Examples

1. Add things that did not occur during calibration — such as eating food below a certain health value.
2. Swap interface items — for example, update your Maple Fletcher to a Yew Fletcher.
3. Swap world items — for example, to fix a bot that's struggling to find world items.
4. Fix minor calibration errors — such as a condition not being picked up correctly.
5. Group similar items together into a single action.
6. Adjust where the bot clicks a world item — for a small item the bot keeps missing.

3.7.1 — Add Things that Did Not Occur at Calibration

First, look for an action that already does the job — never create a new action when an existing one can be edited to do what you want. Another kind of junk to drop goes on the drop action's items; a step that is too slow is that step's timing, not a wait after it. Add an action only for something genuinely new the player does.

Create new action(s) by clicking + Action at the top-left of the Machine GUI, set the action type, then link the new action to your machine with arrows. For example: you created an auto-fighter but didn't eat during calibration, and want it to eat food when below 50 hp. First (if it wasn't in your inventory during calibration) add the food item to 'Interface Items' on the right-hand side (if you don't have any to capture right now, pick '+ add an item to set up later...' from the action's item list, and capture it later — the bot won't start until you do). Create a new action, set it as 'left-click → food item'. Finally, drag two arrows to link your new action to the machine: one arrow from 'attack monster' to 'eat food' with the condition 'health < 50', and a second arrow from 'eat food' back to 'attack monster' with no conditions. And you are done!

Note: if you do not set a 'less-than' or 'greater-than' symbol when setting integer variables, it will default to 'equals'. An action you added yourself can be removed with 'Delete Action'.

3.7.2 — Edit Interface Items

This is one of the most common reasons to edit your bot — some tasks have a progression where the materials involved change over time. You can edit interface items directly from the right-hand side panel. Select the item you want to swap out, and either click 'Swap' (to use an item from another of your bots) or 'Scan' (to capture a new item from your screen, with the application open in the background — then click the item you want in the picture). Spells, prayers and menu options are items too, and are captured the same way.

3.7.3 — Edit World Items

Similar to swapping interface items: select the item you want to swap from the World Item panel on the right-hand side. Click 'Swap' (to use one from another of your bots) or 'Scan' (to create a new world item from the screen, with the application open in the background). With 'Define from one click' ticked (the default), a single click on your item is enough; untick it to draw the box around it yourself. Increasing color-strictness can speed up search time, and reducing shape-strictness is a good idea for animated world items that move around and need to be visible from multiple angles. Follow the instructions in the bot GUI.

Ideally you'll get a blue box only around your target(s). If you end up with false positives (blue boxes in unwanted areas), you can prevent them being targeted at run-time by limiting the search area — see 5.2.1 — Set Search Area.

3.7.4 — Fix Minor Calibration Errors

This should be increasingly rare, but if you notice the bot performing actions at the wrong times at runtime, it may be due to a misconfiguration at calibration. Go to your Machine GUI and look at the conditions on your arrows. If you see anything incorrect, delete/edit/add conditions to make sure your bot behaves the way you want.

3.7.5 — Group Similar World/Interface Items Together

Sometimes you have multiple items but want them handled the same way. For example: you are powermining, and during calibration you didn't pick up any gems — but you want the gems dropped just like the ores. You can do this by grouping gems and ores together. Or another example: an auto-fighter with 3 different types of NPC. The bot attempts to recognize groups automatically, but if it fails you could end up with two (or more) attack actions, which is not optimal. To repair this, unlink the additional 'attack' actions (by deleting arrows), leaving a single 'attack' action. Then select the 'attack' action, click 'Edit Items...', and tick the NPCs you want in the group. Once all 3 NPCs are grouped together, the 'attack' action treats all 3 NPCs equally — better than having separate actions.

What decides it is the job, not the item: is this the same interaction, for the same purpose, as an action the bot already has? 'Mine the iron rock' is one action however many rocks, angles or colours it has to recognise; burying a second kind of bones goes on the bury action. Eating food and burying bones both click an inventory item, but they are different jobs that the bot has to choose between — so each is its own action. A sequence is two actions too: withdraw the bowstrings, then the bows. One action with both items would click whichever it found first, every time.

Genesis looks for split jobs for you. Actions that click the same way, with the same effect, for the same reasons get a linked-rings badge on the graph and a 'one step with #n?' tag in List view. Click the tag to Make one step (Genesis keeps the action with your calibrated timing, moves the arrows over and takes a restore point first) or Keep them separate.

3.7.6 — Adjust Where the Bot Clicks a World Item

The bot aims each click at a world item from your own calibration clicks on it: where they landed, how spread out they were, and the item's outline. That is right for most items, and you should leave it alone unless there is a problem. The one case worth adjusting is a small world item — a thin stroke, a small rock, a highlight a few pixels across — where a few of your calibration clicks landed off the edge and the bot now misses more than you would. (A bot that knows it missed clicks again after a moment, just as you would, so an occasional miss is fine and expected.)

Select an action that clicks a world item and press Aim... (beside Edit Items...). The window shows the item's picture with its outline, your calibration clicks, and a cloud of dots — each one where a click of the bot's would land. Three things can be set:

• Centre — click the picture to move where the clicks are centred. It has to be on the item. 'Middle of the item' and 'Where you clicked' put it back to either of those.
• Spread — how far the clicks scatter, as a share of the item's size. The range is what real players measure at (12% to 40% of the item's half-size, usually about 20%); it can't be set tighter than that, because clicks that all land on one spot read as a machine.
• Click area — the part of the item the clicks are kept to, from half of it to the whole item. It is never allowed narrower than the spread needs, so the cloud can't be cut off into the hard edge the Biometrics 'Aim edge shape' check looks for.

'What would happen' under the picture says, in words, where the clicks would go and roughly what share would land off the item — an estimate, since Genesis adds its own small scatter to every click and nothing you set here makes the aim exact. Press Save to keep it: the aim is saved into the item, so every action that clicks that item uses it. Use the calibration forgets what you set and goes back to aiming from your calibration clicks.

3.7.7 — Choose Which Slots or Tiles a Step Takes, and in What Order

When you calibrate, Genesis records the order your own clicks took — the sweep you made through the inventory when dropping, or which spots of a resource you worked — and the bot follows it. Select an action that clicks an inventory slot or a world item and press Order... (beside Edit Items...) to see that order and change it. Click the slots or the map tiles in the order the bot should take them; click one again to take it out.

• Inventory and other item areas — the window shows the area's slots, numbered as the game numbers them (left to right, top to bottom). The slots you list are the only slots that step clicks, so it is also a way to say 'only the first two columns'. A listed slot that is empty is skipped.
• World items (rocks, trees, fishing spots) — the window shows the map zone with the step's search area shaded. An order you set yourself is also which ones: the step clicks only the tiles you list and leaves every other rock or tree of the kind alone. Five rocks nearby and you want three: list the three. The order from your calibration only favours its tiles; other rocks are still taken.

'Use the calibration' puts the recorded order back. If the window says the bot has no record of an area's slots, it has never clicked that area by slot — calibrate a click on it first. Your AI assistant can set the same order for you (6.3).

3.8 Version History

Genesis keeps restore points for each of your bots: one when it is calibrated, and one before each editing session or change from the AI assistant. Press 'Version History' in the Machine GUI to roll back to any of them — your current version is saved first, so a roll-back can be undone too. The same window also lets you start over: rebuild your bot from its calibration recording, or, for a downloaded bot, download the latest version.

4 Bot Sharing

4.1 Downloading Bots

Bot Sharing is done directly from the application. Just log in, select an Environment, then click the 'Share' tab. Bots available to you will be listed here, each with its average session length and how many people have downloaded it; you can search the list and change its order. Select a bot to see when it was last used, a preview of the bot structure, and a description written by its creator. If you already have a bot with the same name, Genesis asks before replacing it.

Someone may also send you a link to a bot. Open it, and Genesis offers you that bot the next time you're in the app.

A downloaded bot comes with any additions or add-ons its author made to the Environment and the bot uses, so there is nothing extra to install; the General tab of the Machine GUI says what it came with. To use those components in bots of your own, get the add-on from the Environments tab.

4.2 Sharing your Bots

The Bot Sharing list is curated automatically, to keep everything on the list relevant. To be eligible for sharing, a bot must be performing well, performing reliably, and have been used recently. Bots are shared by default: your bot is uploaded after calibration, and appears on the list once it qualifies.

There are two types of sharing: Public Sharing (your username is shared as well) and Anonymous Sharing (your username is kept secret). You can also opt out of sharing entirely if you are on an Ultimate or ViP subscription. For everyone else, if your bot qualifies, it goes into the Share pool.

To view or edit Share status, select one of your bots and use the 'Allow sharing' and 'Hide my name' checkboxes in its Sharing box, which also tells you whether the bot is on the Share list yet. Ultimate and ViP members can also choose who can download it, by botting rank (Members, Veterans, Heroes or Legends).

• Copy link — a link to your bot to paste anywhere. Whoever opens it can get the bot in Genesis, and if they buy Genesis, you are rewarded.
• Unpublished Environments — bots made in an Environment that has not been published yet are only visible to you, until it is.
• Your additions and add-ons — a bot that uses components from your own additions to the Environment, or from an add-on, carries them with it (the Sharing box says so when you hover over it). Whoever downloads the bot gets them inside it; the Environment's own components stay as they are for everyone.

4.3 How Biometrics Work for Shared Bots

Biometric details of the original calibration are stripped before uploading, so just the framework of the task remains. After downloading, Genesis looks at calibration sessions you have performed locally, and uses this data to set up an appropriate biometric profile (actions using it show amber in the Machine GUI). If no calibrations have been performed locally, a generic biometric profile is generated automatically. Genesis keeps the original creator's biometric data, and any other information about them, private. Your camera settings are never shared.

5 Troubleshooting

5.1 Cannot Find Environment

This happens when you have incompatible graphics settings. The only exception is if there's been an update to the application's graphics within the last few hours, but this is very rare — 99.99% of the time it's your graphics settings. The required graphics settings are here. If you are unsure which setting is off, contact us on Discord and we'll help you.

The window Genesis shows when it can't find your Environment also checks your Windows display settings (display scaling, multiple monitors and colour depth), and tells you if one of those is the cause.

5.2 Trouble Clicking World Items

One of the most common points of failure with Genesis is finding world items. But in the vast majority of cases, this is easily resolved. Work through these in order:

5.2.1 — Set Search Area

The bot focuses on certain areas of the screen when it searches. To check it's looking in the right place: go to the Machine GUI and select any World Item to see the area it will be searched for, on the map. You can edit the area — left-click-drag to expand it, or right-click to delete it. Also ensure the blue grid is set correctly, otherwise search areas will not work as intended.

5.2.2 — Update the World Item Profile

At calibration the bot automatically creates a world item profile, but you can also do this manually. If you're having problems, try updating the world item profile — see Edit World Items.

5.2.3 — Highlight World Items

If your application can highlight objects (some have this as a setting or a plugin), turn it on for the world items your bot clicks. Highlighting world items will guarantee success, as well as improve speed and reliability.

5.2.4 — Reduce Zoom

Even when using highlights, you may still have problems if you are zoomed in way too much. The vision system filters out background pixels — and if you are zoomed in like a complete psycho, the bot may mistake your huge world item for background pixels. I know some people do this to reduce misclicks, but misclicks are important for the bot to appear humanlike, and Genesis is designed to recover from them. So don't worry — use a normal level of zoom.

5.2.5 — Adjust the Aim

If the bot finds the item but its clicks land off it — usually a very small item — you can move the centre of its clicks and set how far they scatter and which part of the item they are kept to, within the limits that still look like a hand. See 3.7.6 — Adjust Where the Bot Clicks a World Item. Your AI assistant can do the same from a picture of the item (6.3).

5.3 Crashing Early (without completing a cycle)

If your bot struggles to complete a full cycle of the task, something substantial is wrong with your calibration. The following steps should help you figure out what.

5.3.1 — Check the Map is Valid

It is vital to have a single zone image per area of the world. If your bot just walks around (without teleporting or changing floors via a ladder), you should have ONE zone image. If you go up a ladder once, you should have two separate zone images: one for downstairs and one for upstairs. If your map is fragmented (e.g. you have two zone images for the downstairs area, so downstairs is essentially in two pieces), that's a problem. A faulty map will cause your bot to fail, and there's no point calibrating without first having a valid map. To fix it, create a new bot and make the map again while walking more slowly (a bot's map can't be replaced once it is calibrated). If you still can't get it working, notify us on Discord and we'll look into it.

5.3.2 — Check Calibration Data

You can play back everything the bot saw you do at calibration — useful to make sure the bot read your actions properly. If the bot misread any clicks during calibration it can lead to miscalibration, and you'll be able to see exactly what's wrong here. Go to the Machine GUI and click the 'Calibration Data' button, then watch the replay of your calibration. Be on the lookout for three things:

• (A) World Item misreadings. Check the bot recognized the correct world item on each click. If not, you may be able to fix it by editing your bot (such as grouping similar items together) or re-calibrating.
• (B) Misreadings on GUI clicks. This could indicate the application's graphics have updated recently, or the button/menu you are clicking hasn't been added to the Environment yet (in which case you could add it yourself, or report it to us). If it is sometimes recognized but sometimes not, you may be clicking so fast the bot failed to recognize what you were clicking — slow down your clicks a little and re-calibrate.
• (C) Map misreadings. Assuming your map is valid (as described in 5.3.1), misreadings on a valid map aren't something you can fix yourself — report it to us.

5.4 Crashing After a While

If your bot works for at least one whole cycle, then your bot structure, World Items, and Map are all probably fine — one particular step has failed eventually. When your bot quits it displays recent activity, along with any problems (highlighted in red) before it terminated. Check the Activity Report; you should be able to figure out the problem from there, but let us know if you need any help.

The report also carries an Open AI assistant button — the assistant can read the bot's own trace of the run and tell you which step failed and why. See 6.5.

If your bot stopped with a message saying another bot started on your account, you were running more bots at once than your subscription allows (see 1.2). The newest bot always starts, and the oldest one stops to make room.

6 AI Assistant (Genesis Plus)

Genesis Plus is a subscription that allows an AI assistant to work with Genesis. You can edit bots and environments just by typing instructions on your keyboard, and, if you switch it on, it can step in when a live botting session is about to fail. It includes the connector and 500 AI credits a month (up to 100 a day; a question costs 1, or 15 on the more capable Advanced model); 'Genesis Plus – Connector only' is the connector without the credits.

6.1 Two Routes

Both routes do similar things, but only the integrated AI agent can intervene in live botting sessions.

• Integrated AI — type a question directly in Genesis and the answer comes back there. Nothing to set up. Each question costs one credit, and Genesis Plus refills them every month (you get some credits for free to try it out, and top-up credits never expire).
• The Connector — connect your own AI assistant (for example Claude, ChatGPT, Le Chat or Perplexity — anything that supports MCP connectors). Does not consume any Genesis Plus credits. There is a 7-day free trial, after which it is part of Genesis Plus. Requires setting up; instructions below...

To let the integrated AI step in during a run, tick Monitor this run with AI above the Start button. If the bot gets stuck, it reads the session log and a screenshot of the moment it got stuck, then tries a fix (a restore point is saved first), or tells you why the run ended. It costs 1 credit each time it steps in — at most 3 per session, 9 per run — and everything it does is written to your session log.

6.2 Setting Up the Connector

Only needed for the second route, and only once for each assistant. You need your RiD username and password, and the connector address:

https://www.robotzindisguise.com/mcp/Copy

We call the connector Genesis below. You can name it anything — just use your name wherever these steps say Genesis.

Open the steps for your assistant. Every one ends the same way: a RiD page opens saying it wants to connect to your RiD account — sign in there and press Allow. Your password goes to RiD only; the assistant never sees it.

Questions you ask there use your assistant's own subscription, not RiD credits. The connector has a 7-day free trial, which starts the first time your assistant reads something from your account (not when you add it), and is then part of Genesis Plus.

Then, in Genesis:

1. Open the bot in the Machine GUI (or its Activity Report), press Open AI assistant and choose Use my own AI assistant.
2. Press Send to my assistant. It only sees bots you have sent, as you last sent them, so send again after editing. Session logs upload by themselves after every run.
3. Ask your assistant in your own words and name the bot, e.g. “Use Genesis to look at my bot [bot name] and tell me why its last run stopped.”
4. If it suggests changes, press Check for suggestions in Genesis and review them (6.4).

6.3 Where to Find It in Genesis

• Machine GUI — a Genesis Plus panel on the right-hand side, showing your credits, with an Open AI assistant button. This is the main one: the bot is open, so everything is in reach.
• My Bots tab — a line above the Start button, which appears only when suggestions are waiting for you. No line means nothing is waiting. Suggestions are reviewed in the Machine GUI.
• Activity Report — the report a finished run leaves behind carries the same panel, which is usually what you want at the moment something has gone wrong.
• Environment Editor — for teaching Genesis to read an application's interface rather than for bots; see the Environment Editor guide.

Inside the window there is one text box and, depending on your route, either an Ask button, or Send to my assistant and Check for suggestions. You can also attach a picture of the game You can also attach a picture of your screen — optional, but needed if you want the assistant to add a new world item. The assistantmdash; optional, but needed if you want the assistant to add a new world item or a new inventory, bank or spellbook item. A screenshot taken in the bot editor (or a picture loaded there from a file) keeps only the game world and the item areas on screen; everything else, the chat included, is blacked out before it is sent, so open the inventory first if that is what you are asking about. Your own assistant can also ask for one: Genesis then asks you, in the bot editor, whether to send it. The assistant can also adjust where the bot clicks a world item (the centre, spread and click area of 3.7.6), within the same human limits: it is refused anything tighter, and the suggestion shows you the same picture of where the clicks would land before you apply it. It can also set which slots or map tiles a step takes and in what order (3.7.7) — for a world item that is also which rocks or trees it works, so a suggestion like that is one to read carefully.

6.4 Reviewing Suggestions

Nothing the assistant suggests is applied until you say so. Suggestions are shown together in one window, each with what it will change: choose Apply or Decline on each (or leave it for later), then press Confirm. If a change turns out badly, roll it back with Version History.

6.5 Asking Why a Run Went Wrong

When your bot stops, open its Activity Report, press Open AI assistant and ask. The assistant reads the bot's own trace of the run, so it can tell you which step failed first and why — and suggest a fix for you to review.