0hp: Old School RuneScape

OSRS Menu Entry Swapper on mobile: how to use MES 2.0 and set your left-click

2026-09-23T00:00:00Z

Old School RuneScape has a Menu Entry Swapper, the game's tool for reordering or hiding the options in its right-click menu. The game's news post of 3 September 2026 says MES 2.0, a ground-up rewrite, is live on mobile and in the game's own client from client version 240.6. The top entry is what a tap or left-click does.

MES is the short name for it, and the post uses both. The post says the feature was added a couple of years ago to give players more control: setting the order options appear in, hiding options, and generally letting people tune the menu to suit them.

One thing worth saying early. This piece is Old School RuneScape only. The post it is built on is Old School RuneScape's own, so nothing here is a claim about RuneScape, the version that kept moving forward when this one was preserved separately. That game has its own page.

Our reading is that the last line is the one worth holding on to, and that it is not new: the post describes selecting the top entry as how the game picks what a left-click does, and puts no version on that. Everything below is about moving the entry you want into that top slot, and getting the ones you keep misclicking out of the way.

The post's own instructions, in its order, and then the controls.

Long-press, or right-click, to open the menu.
If you play with a keyboard, do not hold shift, unless you want to edit the secondary set of swaps. There are two layers of customisation now, standard and secondary, and the secondary one needs a keyboard and opens with shift.
Press the 'edit' button in the top-right corner of the menu. That collapses the menu per object, so you can edit each one on its own.
Go to the menu you want to reorder.
Use the controls below.

Control	What it does, in the post's words
Up arrow	Bring entry to top of menu
Down arrow	Shift entry down by one space
Eye	Hide/show entry
Star	Promote sub-entry to top-level menu
Reset	Move all the entries under this object back to default

The post flags one line under that list as important: the top entry in the menu becomes the primary entry used when you tap or left-click.

How do I change what left-click does?

Bring the option you want to the top of that object's menu with the up arrow. That is the whole thing.

There is a second setting worth knowing about, and the post spells out why. By default the menu opens with its very top edge under your pointer. A setting called 'Minimenu start position' changes that so one of the entries sits under your pointer instead. The post says this works well alongside reordering, because it lets you set both a left-click option and an easy right-click option.

Two more settings are named. You can change how long a long press has to be before touch input opens the menu, and the post notes that shorter times let you act faster but need more precision. You can also change the spacing of the menu entries, which the post suggests if you find the menu too small.

How do I hide an option I keep clicking by accident?

Same edit mode, different button. Open the menu, press 'edit', go to the object you want, then press the eye on the entry. The post lists that control as hide/show entry, so it turns the entry off and can turn it back on.

The post says hiding options was one of the reasons the feature was added a couple of years ago, alongside setting the order entries appear in and letting people tune the menu to suit them. Our reading is that this is the control to reach for when you never want to see an option again, rather than pushing it down the list with the down arrow.

What about walk-here?

Walk-here, which is the menu option that just moves your character to the spot you clicked, comes up in four places in the post.

Three of those four are here; the fourth is in the technical section further down.

Entries can now be re-ordered around walk-here more reliably. The post lists that as one of the rewrite's improvements. Some customisations involving walk-here will not carry over from the old system, so those are ones you set up again. And walk-here turns up in the known issues: on priority swapping the post names walk-here being prioritised over Attack in player versus player, meaning the parts of the game where players fight each other rather than the game.

Does it work on mobile?

Yes. The post says MES 2.0 is available on mobile and in the game's own client from version 240.6 and up. Some of this is mobile-specific, and the last line applies everywhere:

Tall menus scroll with a swipe now, rather than making you grab the scroll bar.
Mouse behaviour on mobile should be slightly more consistent with desktop behaviour.
The secondary layer of swaps needs a keyboard, which the post says includes mobile players who run a keyboard setup.
Your entry swap settings are saved per device, so they will not carry over between devices.

Our reading is that this is the one that will catch people out. Set your phone up the way you like it and your computer is still on its own settings.

Five things the post says, before you go looking for a bug.

If tapping used to give you the wrong thing, that was the bug. The post's change log says it fixed a bug in the menu entry swapper that made 'Examine' and other unexpected entries happen on tap or left-click. Examine is the menu option that just tells you what something is. Our reading is that if this was your problem, the fix is the update itself.
You may not have it yet. MES 2.0 comes as part of client version 240.6. If your app has not updated itself, the post says you may need to update it by hand through the app store, and that the roll-out takes a little time across all devices.
Third-party clients are not part of this. The post says the changes will not affect third-party clients, which are separate programs made by other people that also run the game. It says they are unaffected, and our reading is that this is not the same as saying the feature is unavailable in them.
Some of your old setup may need redoing. The post says most previous menu customisations will carry over, and that some customisations involving walk-here, which is the menu option that just moves your character to the spot you clicked, will not. Those you set up again.
Drag-and-drop is gone on purpose. Entries are no longer dragged; the arrow controls replace them. The post calls that a decision to simplify the system so the team could focus on making it do more and work more reliably.

The post also carries a Known Issues box, which it says is a new format it is trialling. Six issues are listed, each with a status word and a date. Our reading is that three of them are about the swapper itself:

Issue, as the post names it	Status	Dated
Cannot Open The Swapper	Issue Raised	3 September
PoH Fairy Ring Issues	Issue Raised	3 September
Priority Swapping	Issue Raised	3 September

On the swapper failing to appear, the post says some players have raised that in certain instances the swapper options fail to appear. On player-owned houses, which are buildings each player customises and fills with useful rooms, it says some players have raised that their fairy ring, which is one of the game's teleport networks, either cannot rearrange options or activates the wrong option. On priority swapping it says some players have raised that setting certain priority options are making other options a priority in different interfaces. It names one case: walk-here being prioritised over Attack in player versus player, where players fight each other rather than the game.

The other three issues in the box sit on the same page, and our reading is that the post does not connect them to MES 2.0. They are the chatbox, the Total Level text appearing in the top-left of the screen rather than over the appropriate skill, and a tablet issue where the Special Attack button needs a long press. Total level is the game's running total of all your skill levels. The Special Attack button is the on-screen button that switches on the special attack of the weapon you are holding. The chatbox entry is three separate reports in one. The post says some players cannot scroll it with a finger. It says it has also seen reports of the channel buttons not responding when pressed, and that others have reported not being able to click through the chatbox's transparent version. We are naming them because they are on the same page as the ones above, not because the post says the rewrite caused them.

How do I reset it?

Two ways, and they do different amounts.

The big one is a "Reset minimenu ordering" button in the settings. The post says that is the one to use if you want to reset your existing customisations and start from scratch. The minimenu is the game's own name for the little list of options a right-click opens.

The small one is the Reset control inside edit mode, on the row of controls in the table above. That moves all the entries under one object back to default. Our reading is that the rest of your setup is left alone.

Our reading is that this is the part of the post most people will scroll past, and the most interesting thing in it.

The post says that in the 2007 code, its name for the game's original code, the order was fairly simple to achieve: things went into the menu already in the right order by default, apart from a few that were shifted to the bottom. It says that order was tightly coupled to the 3D renderer. The renderer drew every object to the screen back to front and recorded everything under the mouse as it went, which the post says incidentally leaves a list of what was under your pointer in reverse order. Flip it, and you have the order the menu should be in.

Then two things happened, both in the post. The game's own client kept adding to what the menu could do: some entries had to move to the top, some had to move around walk-here, some had to appear only while shift was held, and full reordering arrived. And the game switched to Z-buffered rendering, a way of drawing a 3D scene that works out what sits in front point by point instead of painting whole objects back to front, so the renderer stopped drawing things in that neat order. Our reading is that this is why the menu resisted patching for so long. Its order was a side effect of how the scene was drawn, so changing one meant reaching into the other.

Our reading is that the post is candid about what the rewrite cost, and that this is worth crediting. Drag-and-drop is gone. Some walk-here setups will not carry over. Settings live on one device and stay there. The post says the rewrite "will attempt to migrate" existing customisations and that most will carry over. Our reading is that this is the good kind of trade: the price is written in the same post as the prize.

Our reading is that the game took the harder repair here rather than the quicker one. We read one of the Summer Sweep Up batch's fixes the same way, in our own coverage of it.

What's next, and none of it is dated

Nothing here joins our calendar, because the post puts no date on any of what comes next.

Six issues are listed with the status words "Investigating" and "Issue Raised" as of 3 September. The post says feedback will be closely monitored and asks for thoughts and bug reports in the #mobile-bugs channel on the game's Discord server. It calls the Known Issues box a format it is trialling, without saying whether it stays. And it says the new foundations let the team add support for different styles, larger fonts and better internal debug features, none of which is dated either.

So the honest summary of what comes next is: six known issues with no fix dates, a feedback channel, and a list of things the rewrite makes possible. We will move a date onto the calendar when the post's own follow-ups give us one.

OSRS water sapphire and elemental jewels: where they drop and what they make

2026-09-10T00:00:00Z

Jagex, which is the studio behind Old School RuneScape, shipped the rest of its Summer Sweep Up on 2 September 2026. Everything landed except the pet updates, which its own note says are planned for release within the next two weeks. The changelog is mostly small mercies: stackable Unsireds, a lectern that remembers what you were making, inventory locking in the Seed Vault, and four amulets for spellcasters plus a fifth that combines them.

A little of the game's own vocabulary before the numbers. An Unsired is a drop from the Abyssal Sire, one of the game's bosses, traded in for a reward. The Seed Vault is the storage room for farming seeds. Runecraft is the skill that makes magic runes. GP means gold pieces, the currency. A raid is a dungeon built for a group. And Permanent Deadman Mode, which the changelog names as such, is a high-risk mode where dying costs a great deal.

The numbers worth writing down

Change	Detail
Necklace of Fangs	+12 Ranged Accuracy, +1 Ranged Strength, 1 in 128 from Turoths; also drops from Spiked Turoths, at a rate Jagex does not give
Elemental jewels	1 in 64 each: air from Killerwatts, water from Sea Snake Hatchlings, earth from Molanisks, fire from Infernal Mages
Elemental amulets	+10 Magic Accuracy, +2 max hit, Runecraft 18 to 21 by element
Elemental amulet, combined	The four elemental amulets plus 500 runes of each element, Runecraft 30; +10 Magic Accuracy and +2 max hit on all elemental spells
Shark lures	1 lure, 50% chance of 5 ticks becoming 4; 3 lures, always 4; 5 lures, always 4 with a 50% chance of 3
Fishing Sacks	500 Molch pearls reclaimable per extra sack, from Alry the Angler
Permanent Deadman risk floors	at least 100,000 GP in alch value to attack other players, at least 500,000 near the chest; raid entry needs at least 1,000,000 AND no Deadman protection remaining

Alch value, in that last row, is what an item is worth when magically turned into coins.

Our take: what it means for players

The Unsired fix is the model here, and it is worth explaining, because it shows the right way to solve this kind of problem.

Unsireds could not stack because each one, in Jagex's words, had to retain separate information about its potential reward. Jagex moved the roll to the Font of Consumption instead. Our reading is that this is the harder of the two available fixes and the better one. It makes every Unsired the same item, rather than bolting on a storage exception that would have left the oddity in place. A design fix rather than a convenience feature, and it costs the player nothing.

The same instinct runs through the rest. A lectern that remembers your last tablet. Ghommal's Lucky Penny working when consumed rather than worn. Inventory locks in the Seed Vault. Abyssal Lanterns storable in Magic Wardrobes, which the changelog credits to popular request. None of that is content. Most of it is friction with no benefit to anyone, and removing friction is the cheapest respect a studio can pay to the people playing.

Deadman is the one that will start an argument, and we think Jagex has it right. You now need at least 100,000 GP in alch value to attack another player, and at least 500,000 near the chest. Entering a raid area needs at least a million risked and no protection left. A player who risks nothing can no longer farm players who risk everything. A permanent mode where players fight each other works best when the attacker has skin in the game.

The one blemish is a promise rather than a change. The pet updates would let pets follow you into content like the Gauntlet, Fossil Island's underwater area and various minigames, and respawn with you on death. They did not make this batch, and Jagex says only that they are planned for release in the next two weeks.

What's next

Jagex plans the pet changes for the next two weeks, and lists the Phosani's Nightmare pillar health bars for a coldfix next week. Phosani's Nightmare is a solo version of one of the game's hardest boss fights. Nothing new joins the calendar from this batch.

That coldfix note sits oddly, and our reading is that it is worth flagging. A line further down the same page says the totems and pillars at Phosani's Nightmare were not showing their health accurately and have been fixed, while the Known Issues box still lists the problem as outstanding. Jagex never says the two are the same bug.

The page does carry two dated events: LANscape on 5 September, which is the studio's own in-person day where creators play together, and Dragonwilds 1.0 on 15 September. Both are already on the calendar from their own announcements.

Bronzeman won a majority in Old School RuneScape and lost anyway

2026-09-03T00:00:00Z

Old School RuneScape's Bronzeman vote got more yes votes than no votes and still failed. A change put to a vote in this game needs 70 percent to pass, which is a much higher bar than a simple majority. Jagex's own post-vote note, published 21 August 2026, confirms the majority and the shortfall.

Two things to know if you have never played. Jagex, which is the studio behind the game, puts big proposed changes to a public vote, and the cache for this one says the Bronzeman poll "fell short of the required 70% supermajority". Bronzeman is a self-imposed mode that blocks buying from other players.

What the studio said it did

	Detail
Result	Majority yes, below the 70% bar
Threshold	70%, described by Jagex as the required supermajority for this poll
Studio's advance knowledge	Jagex says it can see results before they are public, and prepared for this outcome
Immediate action	In-game survey, live from 11:15 UTC on 21 August
Proposed change	An optional question in future votes asking why a player voted as they did
Next step	An update once the studio is confident what, if anything, should happen

Our take: what it means for players

We are going to defend the threshold, and then criticise how it was used.

A 70 percent bar is the single most valuable thing this game has. It is why the world still feels like something its players own rather than a product shipped at them, and it is why a studio cannot quietly reshape it in a direction the community hates. A mode that more than half of voters wanted and fewer than seven in ten did is exactly the case the bar exists for. Jagex publishes no percentage, only "a majority" and the shortfall. The bar held. Good.

Where we would push back is the design of the vote rather than its outcome. Jagex said it saw the result coming and had prepared for it, and that it now wants to ask people why they voted. Asking why after the fact is a survey. Asking why on the ballot is data. The studio's own note says this information is "now much easier for us to process with the improved polling system we have", which raises the obvious question of why a proposal this contested went out without it. A failed vote costs the community the wait and costs the studio the work, and both are avoidable when the disagreement is legible in advance.

The tone deserves credit. Jagex asks everyone to focus on "where did we go wrong, and what needs to change in the future". That is the right target. Our reading is that the mode failed because the pitch did not answer the objections, and blaming voters would have been the easy move.

For anyone tracking the discussion, the studio points at the 2007Scape subreddit, the Steam forums and its Discord, and at the Old School RuneScape Wiki for the reference material.

What's next

Nothing is dated. The survey opened at 11:15 UTC on 21 August, with no close given. Jagex said it would return with an update once it knew what should happen, and as of writing it has not. So the calendar carries nothing for Bronzeman, and will not until there is a day to carry.

Old School RuneScape puts twelve creators in a room and lets chat sabotage them

2026-09-03T00:00:00Z

Jagex, which is the studio behind Old School RuneScape, is running a live creator event in London on Saturday 5 September 2026, streamed from 14:00 to 19:30 UTC. Its own announcement is refreshingly clear that this aims at something more relaxed than a polished esports tournament. Twelve Old School RuneScape creators, four teams, in-game and real-world challenges, and viewers voting on how badly to sabotage them.

LANscape, which is what the studio calls the event, is its own in-person day where creators play in one room. The four teams are named after gods in the game's world: Saradomin, Zamorak, Bandos and Guthix.

The four teams, and what they face

Team	Creators
Saradomin	Purpp, Potatohime, Mr Mammal
Zamorak	SoloMission, Tastylife, Sardaco
Bandos	Skill Specs, Katerena, Sick Nerd
Guthix	B0aty, Megan, MMORPG (a creator's handle here, not the genre)

The in-game rounds run on a special event world, which is a separate copy of the game where Jagex can change rules it would never touch on the live one. There is a team tileman challenge scored on crossing as few tiles as possible. There is a boss relay of familiar bosses, one or two of which Jagex says may catch the teams off guard. There is a barrage race across Gielinor, the world the game is set in, with obstacles thrown in. There is hide and seek. And there is a final showdown where players fight each other, where Jagex says points earned earlier could help teams buy upgrades.

Away from the keyboard there are gnome gliders, giant Jenga, cup-stacking and carnival games. The announcement lists all of those as challenges Jagex is "looking at" rather than confirming. Soup and J1mmy host.

Our take: what it means for players

This is the right way to spend a Saturday on a game this old, and the reason is the part that sounds like a joke.

The event world is the news. Jagex is making rule changes it describes as deeply irresponsible anywhere near the main game, which is only possible because the studio is willing to build a throwaway ruleset for one afternoon. Most publishers would either run the event inside the live game with the handbrake on, or build a competitive format only the very best players recognise. A tileman race and a game of hide and seek make sense to anybody who has ever played this game, and that is exactly why they will draw an audience.

Giving the vote to Twitch chat is the other good decision. Handing viewers the power to split a teammate's mouse and keyboard, or take away somebody's F-keys at the worst possible second, makes the audience a participant rather than a metric. It also, quietly, makes the competition unfair on purpose, which removes any pressure to treat it as a ranking.

Credit is the whole point of the event, so we will pass it on. Purpp, Potatohime, Mr Mammal, SoloMission, Tastylife, Sardaco, Skill Specs, Katerena, Sick Nerd, B0aty, Megan and MMORPG are the twelve competing. Soup and J1mmy are hosting. Jagex thanks The Skulled for the announcement video. A game stays alive this long because those people keep showing up.

What's next

The stream runs 14:00 to 19:30 UTC on 5 September, on the Old School RuneScape Twitch channel. Jagex says some participating creators may also stream their own perspectives. The date is on the calendar with the day we last checked it against Jagex's page.

0hp: Old School RuneScape

OSRS Menu Entry Swapper on mobile: how to use MES 2.0 and set your left-click

How do I use the new Menu Entry Swapper?

How do I change what left-click does?

How do I hide an option I keep clicking by accident?

What about walk-here?

Does it work on mobile?

Why isn't my Menu Entry Swapper working?

How do I reset it?

Our take: why the whole menu had to go

What's next, and none of it is dated

OSRS water sapphire and elemental jewels: where they drop and what they make

The numbers worth writing down

Our take: what it means for players

What's next

Bronzeman won a majority in Old School RuneScape and lost anyway

What the studio said it did

Our take: what it means for players

What's next

Old School RuneScape puts twelve creators in a room and lets chat sabotage them

The four teams, and what they face

Our take: what it means for players

What's next