RuneScape July 2022 Patch Notes | Get ready to slay in style with these Zamorak-inspired outfits!

Introduction

Calling all fashion-forward gamers! Get ready to unleash your inner glamorak in the latest showcase event. We're inviting dedicated followers of fashion to submit their most devilishly stylish Zamorakian-themed outfits for a chance to win some amazing prizes. The top 10 outfits will be featured in a special blog, and the winners will be chosen by a panel of Jmods. So, don't miss out on this opportunity to show off your fashion skills and dress to impress! Submissions are open until July 13th, so head over to the FashionScapers Discord and join the #zamorak-submissions channel to enter. Good luck, and may the most demonically decadent outfit win!

FINDING YOUR INNER GLAMORAK!

As part of this showcase, we are calling out to all you dedicated followers of fashion to send in your latest Zamorakian-themed outfits. We'll be posting 10 of the most demonically decedent outfits in a special blog, with prizes for the most on-theme outfits! To enter, head on over to the FashionScapers Discord to the #zamorak-submissions channel and add your Outfit Image / RSN, plus a list of the items you used to create the look! To help show off your outfit make sure to give us a twirl, i.e, include a turnaround like these:

The submissions are open until July 13th at 23:59 BST. The winners will be decided by a panel of Jmods, so make sure you dress to impress!

PRIZING

Place	Prize
1st	20th Anniversary Book + King Black Dragon Brick Building Set + 3 Bonds
2nd	King Black Dragon Brick Building set + 3 Bonds
3rd	King Black Dragon Brick Building Set + 1 Bond
4th-10th	1 Bond

THE YEAR WAS 2016...

...and there were whispers in the studio of ideas for a launcher – a way of unifying our games under one banner. We even created a prototype, demonstrating how a player might install and launch both Old School and RuneScape from a central application on their humble Windows desktop. Fast forward to mid-2017, and we had gathered a small team to begin building it. We had lofty ideas of players being able to maintain a longer-lived session of days and weeks, rather than the mere hours we had at the time, so people could quickly get into the games they love without needing to re-enter their username and password. Sound familiar?

RS MOBILE

That same year, Jagex announced that we would be bringing both Old School and RuneScape to mobile – we, therefore, parked the launcher to concentrate on this for the time being. However, this new focus actually gave us new ideas for the launcher, because we were also looking at how to bring long-lived sessions to mobile devices. To this day, it’s possible to boot up both the iOS and Android app and just tap ’Play’ if you've logged in just once before. You can think of this mechanism as the first example of what we now provide in the launcher today, as it's fundamentally built (with a little Jagex magic) on the same core concepts.

DIPPING OUR TOES IN

You may have heard of OAuth2; it's been around a little while. Even if you haven’t, you're likely using OAuth2 every day without realising it! Every time you log into something using your Google, Facebook, Twitter or even Twitch account, you're using it. It's not something Jagex invented and has been worked on for many years by security professionals to provide a watertight method of authorising you to use software. It’s trusted and used by thousands of software companies to keep their accounts as safe as possible. However, RuneScape has also been around for a good long while, and it already had a very well-established way of logging users in, with certain user experience expectations built in too. So, we had to ease our way into utilising a new mechanism carefully. OAuth2 comes with two types of tokens; an Access Token, which is used to authorise network calls, and a Refresh Token, which is used to get a new Access Token when the existing one expires. It's these tokens that give us the ability to log you back into the game, even if you haven't played for days on mobile. In order to maintain our existing user experience at the time, we utilised OAuth2's extension specification and hooked in our existing login processes to generate these tokens. This was our first step towards a new way of logging in. We introduced this feature as part of the mobile beta and subsequent launch of Old School on mobile in 2018.

EVOLUTION

At this point, we were just barely starting to use OAuth2 mechanisms to log people into the game. We knew that we wanted to utilise the standard OAuth2 flows to log people in without having to use the extension we were currently using. Utilising one of the standard flows, i.e., authorization_code, had several benefits:

We could enforce a principle of least privilege - only one location would be responsible for your username and password, rather than entering it in multiple locations (e.g. Website, OSRS Game Client & RS Game Client), this way nothing else ever needs to know your sensitive login details.
We could unify the login process, providing the same user experience no matter whether you were logging into Old School or RuneScape. It would also allow us to centralise ways of logging in (across Google, Apple and Facebook) without needing to update the game client substantially – or even at all!
We could implement strict security controls and use industry-leading software to protect against malicious users effectively because it would only be a single place, and it used the HTTP protocol rather than the custom protocol our game clients used.
It would pave the way for us to integrate other systems we develop to have logged-in functionality more quickly than the custom methods that were being used previously.

However, this presented both a technical and user experience challenge. OAuth2 expects to be handled by a web browser, something that can render HTML, CSS, JavaScript, store cookies and deal with HTTP responses, these aren't things that are performed directly by a game client. Given that the mobile client was already capable of dealing with OAuth2 tokens we decided, once again, to tackle it there first.

We focused on mobile first because we had already made progress utilising OAuth2 tokens with success on that platform, so it made sense to enhance the flow there before trying to recreate it anywhere else. Both Android and iOS have very good support for this kind of flow, specifically providing features to enable OAuth2 via specialised browser windows (Trusted Web Activity and ASWebAuthenticationSession respectively) that could be launched from phone apps. We already had a login experience that people knew from the browser which we like to call the ’web login flow’. People had used this process for years to log in and manage their accounts, post on the forums, or subscribe. It therefore made sense for us to re-use that where we could. We spent a fair amount of time with the game teams from both RuneScape and Old School to ensure that we used all the right security controls on the specialised browser windows mentioned above. We wanted to get to a place where we had a working mechanism to log people in via the same website they trust, get OAuth2 access and refresh tokens via a standardised OAuth2 authorization_code flow and log into the game on mobile successfully. In December 2020, for the first time ever, people who logged in on mobile went through this new flow – supported by the same protections we had in front of our website logins! Things like captcha, WAF, rate limiting and other standardised protections only achievable through a browser and HTTP network calls were now protecting logins to the mobile game.

AND NOW FOR OUR NEXT TRICK!

We were in a good place with Old School on mobile: we had the ability to tweak and add further protections to login, we had those all-important remembered logins and all the other benefits I mentioned earlier, and when it came to releasing RuneScape on mobile in 2021 it was very straight forward to integrate it with the OAuth2 flow. But how would we get these same benefits on desktop? Unlike Android and iOS, Windows does not have a specialised browser window that can be used in the same seamless fashion. Instead, a user can have multiple browsers which do not have first party support from the operating system. So, we experimented with using the user's default browser, in a similar way to how we handle Apple and Google logins on desktop. The principle was simple:

1. Double-click desktop icon.
2. Start the game client.
3. Click ‘Login’.
4. Open the browser.
5. Authenticate.
6. Direct back to the game client.
7. Enter the game with the oauth2 access and refresh tokens.

In practice though, the experience left something to be desired. What you actually end up with is:

1. Double-click desktop icon.
2. Start the game client.
3. Click ‘Login’.
4. Open the browser.
5. Pray the browser will take focus.
6. Authenticate.
7. Receive a ’Success, you logged in!’ message.
8. Have the user manually navigate back to the client.
9. Wait for the login process to finish.
10. Retrieve OAuth2 access and refresh tokens via the old method.
11. Enter the game.

We looked at trying to remove some of the steps. Instead of the game client starting first, why not the browser? And instead of utilising the same mechanisms Apple and Google logins use, we looked at starting the client with protocol handlers. Let’s see how that plays out:

1. Double click the desktop icon.
2. Open the browser.
3. Authenticate.
4. Receive ‘Success’ message.
5. Receive ’Are you sure you want to open this program dialog?’ message that forces users to choose ‘yes’ or ‘no’ when using protocol handlers (some browsers allow you to remember this choice, but others don't… we’re looking at you Microsoft Edge...)
6. Click the ’Yes I'm sure; button – if you don't, nothing happens.
7. Start the game client, which now takes focus automatically thanks to the protocol handler.
8. Retrieve OAuth2 access and refresh tokens via the authorization_code flow.
9. Enter the game.

This was closer to what we wanted. We're using the OAuth2 authorization_code flow as intended now. However, we've also now got a horrible system dialog that we can't style or change in any way! Plus, if the user selects no, then nothing ever happens, and they're forced to start again. Also, what happens if the game is already open? Should we start a new instance or pass the authorisation to the existing instance? RuneScape already has a way of opening the game from the browser, of course. But the whole ethos of RuneScape's client is built around running as many instances as you want, rather than keeping a handler open to just one, making this a tricky technical challenge. There are a couple of strategies which would allow us to avoid the dialog altogether:

Have the game client run a web server on the user's computer and redirect to that in the browser. With this solution, we would end up in the same situation where the user had to manually switch back to the game client once they finished authenticating, so we ruled this out pretty quickly.
Have the game client bundle its own CEF (Chromium Embedded Framework) web browser, which we'll discuss further below.

WHAT A BUNDLE OF FUN!

If we bundled a browser in with the game, this would give us a UX which we could completely customise – no dialogue, no need for the user to manually swap between applications. On the face of it, this seemed like everything we wanted, but there are a few caveats. One is RuneScape-specific, and the others are presented with an eye to future Jagex publishing opportunities.

1. We’ve always prided ourselves on maintaining a relatively small download size for the game client. Bundling something like CEF would more than double the downloadable package – something we wanted to avoid, especially if it’s only for authentication purposes.
2. We said originally that our aim was to have a centralised and unified authentication experience when logging into any Jagex product, and that this would include future games, so:
  - If we bundled a browser into RuneScape, were we then dictating that all games published by Jagex and using our authorization mechanisms would need to do so as well? This could be a significant integration pain point if a game never considered needing CEF initially.
  - A weakness of an embedded browser is that with some relatively straightforward code, the hosting application (i.e. the game client) can access the username/email and password. In the case of first-party games like RuneScape, this was less of a concern as Jagex was in control of the security standards and we could maintain responsibility for the security of those credentials. As soon as we provide this mechanism to game developers other than Jagex, like via the Jagex Partners Scheme, we'd be pushing the responsibility for maintaining security around credentials in that part of the flow to them, and not our internal staff. This wasn't a responsibility we wanted other studios to have to take on.
  - If multiple games have embedded a browser, should a security vulnerability be discovered in that embedded browser technology, all games would need to update to protect you effectively – a mammoth task that only grows the more games we add.
3. Embedding a browser in each client would prevent us from utilising any kind of single sign-on mechanisms across each game, as they'll not share any storage for tokens returned. In an ideal world if you log in to RuneScape, you're authenticated for Old School and any other game we publish, such as Melvor Idle.

It became clear that while it may give a better user experience than the default browser approach we considered previously, bundling a browser directly into a game wasn't feasible long term. We needed to revisit an old idea...

AN OLD IDEA RESURFACES

Towards the end of 2020 we were ready to discuss the prospect of a launcher, only this time with much more experience and focus. We took the same concepts we discussed about an embedded browser above and applied them instead to a launcher, and found that it fit our use cases and user experience goals perfectly. This launcher would be developed using an embedded browser from the start, one that would be used for more than just authentication and authorisation – and would set the overall user interface as a baseline. So let’s run through the requirements we mentioned above, and show how the launcher enables us to meet them:

1. Standard authorization mechanism – with the launcher embedding a browser, the OAuth2 authorization_code flow works out of the box as it can handle all the things a normal web browser can.
2. Security and automated attack prevention – as we mentioned before, industry leaders who offer these services provide software which only works properly in a browser and over HTTP. The launcher allows us to standardise with things like Captchas, WAF, rate limiting integrating seamlessly.
3. Remembered logins – because the launcher is also a native application, it's capable of storing the OAuth2 Access and Refresh tokens securely on your computer, so remembering your logged in session is both straight forward and secure. Best of all any Jagex game you play in the future gets it for free too, so you never have to enter your credentials again for a new game. It will just know who you are!
4. Seamless user experience – as you never leave the launcher to enter your credentials, there's no risk of a user needing to manually switch applications, and no nasty dialogs popping up during the login process.
5. Minimum game client download – by using a launcher to serve authorization purposes, the game clients no longer need to bundle anything extra for this purpose, and can maintain the minimalist game download size.
6. Centralised credential responsibility – the launcher is now, and will always be, under the developmental control of Jagex. This means Jagex will always remain responsible for the security of your username/email and password, with OAuth2 tokens passed to games instead regardless of whether the game was developed internally or externally to Jagex's development teams. It also means that all our games get updates, fixes, improvements to the flows at the same time.
7. SSO across our games – no matter what Jagex game someone plays, now or in the future, they will always have the launcher to start it. It becomes a centralised location for authorization credentials to reside and if players want to swap to a different game, they don't need to authenticate again.

At this point, hopefully it becomes clear that the launcher delivers exactly what we wanted to achieve, both from a user experience and a security perspective. There are of course numerous other benefits that it also brings in terms of insight and user experience optimisations, but perhaps those are for another blog…

THAT'S A WRAP!

I hope this gives you an insight into some of our developmental process when it came to creating a launcher, and the challenges we needed to overcome in delivering it to you. We made sure that your account's security was our top priority every step along the way, as well as making sure that every interaction you have with our games is as seamless as it can be without compromising that security. Going forward, we'd like to talk more about the additional features and benefits the launcher brings our players, and how we're continuing to support this vision of security and user experience into the future. Keep an eye out for more insights soon – and thanks for reading!

announcing the winners of the Zamorak Fashion Contest!

Ninja Strike: Scattershot Pyramid Plunder changes, farming tweaks and more!

The Ninjas are back with all manner of Quality of Life improvements – and there should be a little something for everyone! For the agriculturally minded, Farming clicks are now a whole lot nicer, with no more Farmers and Leprechauns milling around. Message box clutter has also been reduced, and a brand new Shop interface is just a left click away! Those plucky Ninjas have also taken on some of the minor frustrations with Pyramid Plunder by making all entrances go to the Guardian Mummy and removing its violent outbursts for players with Level 41+ thieving! On top of that, a variety of Skilling tools are now Bladed Dive compatible, giving you extra mobility even when you’re not in a fighting kind of mood! Head to the Patch Notes section for details on all these improvements and more...

Treasure Hunter: Academy of Heroes Wanna score some new Cosmetic Ability Overrides?

We’ve got a new PvM-themed Treasure Hunter! This time you're levelling up a character and slaying monsters to get their loot! Sounds familiar? Academy of Heroes offers regular Treasure Hunter Skilling Rewards alongside new Cosmetic Ability Overrides and PvM rewards never seen before in a Treasure Hunter promotion. That’s Aura Refreshes, Life Refreshes, Soul Reaper Refreshes and Item Protection Contracts! So how does it work? Every Key used will give you a reward and damage the monster. Slaying the monster will then give you three items at the rarity displayed. Don’t stop there, though, because every Monster you defeat will level you up (capped at 138, of course!) and you'll deal more damage on average with every level. Every 10 levels or so you'll get guaranteed PvM-based rewards, including Deathtouched Darts! Finally, if that's not enough to tempt you – every single Monster loot drop has the chance to include new tradeable Cosmetic Ability Overrides for Hurricane and Dragonbreath. See them in action below:

Treasure Hunter: Academy of Heroes begins Thursday, July 21st!

Series Launch: Let's Chat About... Developers open up on topics you care about

Did you catch the launch of our new series last Friday, in partnership with The RS Guy? Let’s Chat About… is a new video series where we invite a community creator to visit Jagex for extended conversations about some of the design topics you care about the most. We've made this to show to give you an insight into what we’re thinking right now as we work on future RuneScape updates. It's not all about concrete announcements and commitments, more of an in-progress creative conversation that we hope will enable richer, more open discussions between developers and players.

Winners
1st	RSN: Zoidburg26
2nd	RSN: Hekserij
3rd	RSN: Zlayer

Massive congratulations to each of our top three winners! That's not all, though. While not quite making it to the top three, we had a handful of runners-up who will each win a Bond! In no particular order:

Finalists
RSN: Cutey pie	RSN: Kaylen
RSN: Sira1992G	RSN: Firehelm17
RSN: Noctylla	Rsn: B 0 0 G Y
RSN: Drace

Physical prize winners will be contacted shortly to organize delivery and Bond winners will receive them in-game soon!

Prime Gaming Drop Grab your Treasure Hunter Keys and more!

Our latest Prime Gaming drop arrives tomorrow! This month our Prime pals are giving you a Currency Pack, which features:

35 Treasure Hunter Keys
200 RuneCoins
An Umbral Chest

Patch Notes Fixes and improvements in this week's game update

NINJA STRIKE

The login and lobby screens' text components have been replaced with TrueType fonts.

WORLD MAP

Worldmap icon tooltips for the Archeology excavation site are now split over two columns if there are more than three artefacts or materials, so that they better fit a mobile aspect ratio.

FARMING

Leprechauns now confirm successful noting of produce by using items with an infobox.
Leprechauns and Farmers now remain in place rather than wandering about the farm.
Farmers now offer items for sale in a Shop rather than through dialogue.
Farmers now have Pay as their left-click option.

PYRAMID PLUNDER

Instead of three or four entrances to Pyramid Plunder taking you to an empty tomb, all four entrances now take you to the Guardian Mummy.
Players with 41+ Thieving entering Pyramid Plunder are now sufficiently stealthy to always avoid a random act of violence from its Guardian Mummy (the poor Sarcopha-guy has a tendency to lash out… but he's working on his mummy issues.) This levelling benefit is indicated in the Thieving skillguide.
Converted various feedback messages in Pyramid Plunder to infoboxes, so you get feedback if your chat is closed.

BLADED DIVE AND SKILLING TOOLS

The (Augmented) Crystal Chime/Chisel/Hammer/Knife/Saw/Tinderbox, (Enhanced) Pyro-matic/Hammertron, and Sculpting Chisels of Bandos/Guthix/Saradomin/Seren/Zamorak ALL now allow you to use Bladed Dive, when wielded with Laceration Boots or an appropriate off-hand item.
Catalyst fragments from Sliske's Endgame now count as an off-hand item for Bladed Dive, similar to other skilling off-hands.
Fixed a bug that prevented green text about Laceration Boots from appearing in the Bladed Dive tooltip when the ability's wield requirements are met.
Clarified the Requirements tooltip for the' 2x' icon when Bladed Dive is dragged to the centre of the Powers parent interface.

HITBOXES

The agility obstacles at Het's Oasis are now easier to tap on mobile.
Wisps now maintain the same clickbox when turning into fountains.
Bird Snares are now easier to tap on mobile.
The agility obstacles on Anachronia are now easier to tap on mobile.

LORD OF CHAOS

Adjusted Zamorak's common drop table.
Adjusted the weighting of rares on Zamorak's drop table so players should see bow pieces slightly more often, and chaos roar slightly less often when rolling a rare.
Players will now be awarded more common loot and higher chances at rare drops for Zamorak when running the Elite Dungeon.
Any summoned monster during the Zamorakian Undercity Elite Dungeon will now show '(summoned)' on their name, to differentiate between summoned monsters and standard monsters.
Completing The Zamorkian Undercity Elite Dungeon will now progress Daily Dungeoneering Challenges.
- Please note: Story Mode will NOT count towards your Daily Challenge progress.
Following feedback, changes have been made to the way group Enrage works for the Zamorakian Undercity encounter:
- Enrage is now shared between groups of 2-5 players, meaning your highest Enrage will be applied to every group size.
- Messaging has been updated at the end of a Zamorak, Lord of Chaos encounter to clearly state the highest Enrage you have achieved.
- Solo Enrage is tracked separately and remains unchanged.
- When you next log in, your Enrages from groups of 2-5 will be looked at by the system and the highest amount will be taken. A chatbox message will appear to inform you of this.
During the Zamorak, Lord of Chaos fight, if you are within Infernus, you will now hear Zamorak's VO:
- If you are in a solo encounter, you will hear the VO from the Decimate attack.
- If you are in a group encounter, you'll hear all of the VO whilst inside Infernus.
To avoid any confusion when trying to enter a Zamorakian Undercity Elite Dungeon with loot to claim, the following change has been made:
- A new interface will appear when clicking the chest, allowing players to choose between collecting dungeon loot or boss loot.
Following feedback, the amount of Reaper kills given out for a Zamorak, Lord of Chaos task has been brought in-line with other Elite Dungeon boss tasks.
- You'll now be asked to kill Zamorak 2-3 times, rather than 1-8.
If you have Freedom Mode unlocked for the Zamorakian Undercity, using the Zamorak teleport will now place you directly inside the arena, rather than outside the portal.
- Please be aware, if the boss fight has already started, you will not be able to teleport into the arena.
Added quick chat option for Zamorak kills and highest enrage.
When wearing the Vestment of Chaos armour set, the buff icon for the Berserk ability will now correctly last for 26 seconds, rather than 20 seconds.
During the Infernal Tomb mechanic in the Zamorak, Lord of Chaos fight, the Chaos Demon will now spawn in facing east (towards the portal), rather than south.
Fixed an issue that would cause Zamorak to appear in an incorrect location during phase seven of the Zamorak, Lord of Chaos boss fight.
The 'Inner Chaos' buff is now cleared after killing Zamorak and teleporting away from the boss arena.
Whilst in Infernus during the Zamorakian Undercity Elite Dungeon, the 'escape' option on the portals didn't actually do anything! Now, you will be able to leave the dungeon completely, as intended.
The players will no longer be stalled when Eterna teleports.
Fixed an issue where wearing the Vestments of Chaos armour would show the incorrect amount of player adrenaline when a piece of the outfit was removed.
Fixed an issue with clickbox size of the portals within The Zamorakian Undercity.
Added 'The Worst Witch's Grimoire' requirement for the Master Quest Cape achievement.
Finding and reading Archaeology Journal - H.F.A now awards the 'Madness and Malediction' achievement.
- Added 'Madness and Malediction' requirement for Master Quest Cape.
Zamorak, Lord of Chaos is now correctly displayed on the Grim Gem.
Corrected typo in 'The Zamorakian Undercity' option in the Elite Dungeon Chest teleportation UI.
Updated visibility of rare drop animation around the player.
Hotfixed: Fixed an issue where Zamorak's red bar would reset in phase 7 at 1500+ enrage.

OTHER

Damage done to Raksha's shield is no longer capped based on Raksha's remaining health.
Ironmen are now included when sharing drops via group lootshare.
The Beach: Using the Sunshine ability while attacking and destroying the piñata no longer causes a script error.
Added the missing 'Activate' option to the remaining auras in the Aura Management interface
Jellyhead-head will no longer spawn on the water on the Cannonball Run island
Added a missing Plover Birds teleport option to the Trapper outfits.
Hydra's Regrowth ability can now be cast on the Trahaearn Tree Patch
An issue preventing some players from completing Missing, Presumed Death has been fixed.
Fixed an issue which caused the Kerapac's Wrist Wraps to appear twice in the Grand Exchange window.
Fixed an issue where a Dinarrow projectile shot backwards.
Halved the drop chance of dino eggs from Seggregation and zygomite sporelings from Carestyling.
Fixed an issue with gathering resources after the Croesus encounter.
Corrected a few typos during the Desperate Measures quest.
Fixed an issue with being able to use the Strange Device in the Wilderness.
Fixed an issue where gathering Fungal Spores from Decaying Varrock guards with the Volcanic Trapper outfit equipped resulted in the player collecting only one piece of Fungal Spores instead of two.
Fixed an issue where the Collection Log was shown every time the Red and Green Goblin Mail was obtained.
Changed Arc Journal to no longer work while on the Hefin Agility Course.
Twisted Jester Walks preview now shows up correctly in the Customisations menu.

REQUIREMENTS CHANGES

In the coming months, RuneScape will no longer support Windows 32-bit builds or graphics cards that do not support OpenGL 3.0 or higher. This change allows us to focus our technical development and testing resources on more commonly-used platforms.

Community The latest goings-on from our community

COMMUNITY SHOWCASE

@BidoAE has made this wonderful take on the Sword of Edicts. Aren't they fab?

SCAPERS' SCREENSHOTS

Sir Theodore of Falador getting ready to hold the line against whatever is on the other side of that portal. Rather him than us!

You fight the gods if you want to. Elej is taking it easy!

PINK SKIRTS PLAYER EVENTS

Each week the Pink Skirts put on a selection of fun activities that everyone can join. Here are the main events this week:

Corporeal Beast

Hosted by: Patrick K & Clackworthy
Date/Time: Monday July 18th, 19:00 Gametime
World: 123
Location: Corporeal Beast Lair
FC: Patrick K

Nex - Angel of Death

Hosted by: Spotleewolf & Nexaodmass
Date/Time: Friday July 22nd, 23:00 Gametime
World: 92
Location: God Wars Dungeon - Ancient Prison
FC: Nexaodmass

Gregorovic

Hosted by: Pippyspot & Boss Guild
Date/Time: Saturday July 23rd, 20:00 Gametime
World: 88
Location: The Heart of Gielinor - Sliske Lobby
FC: Boss Guild

COMMUNITY SPOTLIGHT

Shining a little light onto community events and activities

OFFICIAL RUNESCAPE DISCORD

It has been two weeks since Zamorak launched, and we have had a blast watching you all taking on the Lord of Chaos. We want to give you the opportunity to display your Zamorak achievements out-of-game as well as in-game, and to flex your PvM prowess in our official Discord! Post in the #zamorak-clears channel proof of 100% and 1000% Enrage to earn exclusive roles and icons in the server!