= Creating AFK Methods = ''Note: This editor guide applies to AFK bossing, ''''not'''' slayer or low-effort methods.'' ​ == Get your priorities straight == AFK methods must: # Be safe (rare chance of death) # Be consistent (every hour is similar) # Be easy to follow (no questions needed in [https://discord.com/channels/534508796639182860/656898197561802760 PvM help (external Discord)]) ​ AFK methods may: # Encourage maximum KPH # Require minimum gear # Have low upkeep costs ​ == Building an AFK setup == ''Note: This section only applies to AFK bossing - not AFK slayer.'' ​ There are a couple of things to note: ⬥ Abilities should ideally be fired in the exact same order every kill ⬥ Some bosses take longer than others to start a fight ​ You can improve '''consistency''' by reducing RNG: ⬥ Removing critical strike boosters, e.g., biting4 / kalgpouch / reaverring ⬥ Disable pocket slot books scriptureofful / scriptureofamascut ​ You can make kill times '''slower''' by: ⬥ downgrading prayers, e.g., malevolence → turmoil → nothing ⬥ removing extra-DPS gear/items, e.g., nodonspikeharness / primalabyssalarmourspikes ⬥ downgrading gear, e.g., vestmentsofhavochood → masterworkhelm → bandoshelm ⬥ downgrading spells / ammo ​ You can make kill times '''faster''' by doing the opposite, plus: ⬥ adding poison, e.g., cinderbanes / weppoison ⬥ adding a DPS familiar, e.g., ripperpouch ​ Sometimes during testing, two people have different results. Try this first to identify the differences (tag '''@Editing Staff''' if you can't figure it out or get into a disagreement and need support): ⬥ Share screenshots of your buff bar, worn equipment, perks and familiar window ​ == Breaking the bar: an example of AFK method writing == Sometimes, our bar "breaks" during testing and we need to adjust - let's walk through an example together and how we might solve it: ⬥ The first ability is berserk (which has a 1-minute cooldown) ⬥ You kill the boss at 28s, then wait another 27s for the next boss to respawn ("fastest" instance) ⬥ The arena spawns the 2nd boss at 55s... and your berserk is still on cooldown... oops! ​ At this point we should note - some bosses take longer than others to start the fight, so this might not be an issue. But let's assume for this example that the boss would have started attacking you immediately at the start of the fight. ​ You have two options: remove berserk or try to slow down the kill by a few seconds. Let's do the latter! ​ There are several ways to slow down a fight, and you can try any combination of these to find the sweet spot: ⬥ If you are far off the mark, adjust the ability bar ​ In our above berserk example: ⬥ We're pretty close, so won't update the ability bar yet ⬥ We will downgrade prayer from malevolence → turmoil ⬥ We will remove the nodonspikeharness ⬥ We will switch from championring to rod ​ Et voila! We are now up to consistent 30s kill times. == Source and attribution == Source: [https://pvme.io/pvme-guides/editor-resources/editor-references/creating-afk-methods/ Creating AFK Methods], by PvME contributors. Licence: [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA 4.0]. Do not silently relicense. Captured 2026-11-10T14:23:41Z. Source HTML SHA-256: 105d537a94263106b52ec46ff4cea3b156a89a20fb9bb89b7182613e9e0ac3b6. Changes: Navigation and typography adapted. Original sanitized source HTML and its text hash are retained separately. Source channel and message references are repaired using the pinned guide repository and public directory/identity evidence; navigation wording is adapted for the web. Every change is recorded in the reference repair ledger. Unverified destinations and contributor names remain explicitly unavailable. Legitimate external community and attribution links are preserved and labeled. Original media is embedded from providers; media rights are separate from guide-text rights. Layout converted to basic wikitext. Rich structures require manual review. Game-version accuracy is unverified; consult the current upstream guide.