![](/uploads/1/2/7/6/127683234/426290274.jpg)
The Game Client is the Old School RuneScape launcher built by Jagex for desktop platforms. In the past, the client was an alternative method to play the game in a browser. However, due to multiple browsers discontinuing support for Java, Jagex was forced to drop support for browser play.Currently, Jagex has official clients for Windows, Mac, and Linux. Cashflow 202 pdf.
From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Game Client was removed after an update. The contents of this page no longer exist in RuneScape, and this article is kept for historical purposes. |
This section or article is incomplete and could do with improvement. Reason: This article is being reviewed for an expansion. You can discuss this issue on the talk page or edit this page to improve it. |
The launcher screen is the same as the normal one on the web.
The popup shown when logging into the Java client before its removal
The Game Client (or the Java client) is a deprecated open-source RuneScape launcher built by Jagex. At the time of release, the client was an alternative to playing the game in a browser. It was used by 75% of players before the introduction of NXT.[1]
The project began on 20 January2010 and was launched on 25 May 2010, originally only being available to Windows users. An unofficial GUI client was eventually developed to work with macOS by taking the jar file from the Windows client and wrapping it in the standard macOS Application Bundle. Jagex later placed its imprimatur on the unofficial macOS client by making it available in the download section of the Runescape website. As of 5 August2015, the latest release is version 1.2.7.
Prior to 25 May 2010, the client was an Internet Explorer-based site-specific browser application that allowed a user to play RuneScape without using a conventional browser. However, players using higher-end computers may prefer to use the browser based version as the client has size and resolution limitations that the browser version does not. Using third-party software to play RuneScape does not violate the Rules of RuneScape, but is not recommended for use by Jagex. Version 1.0.0.5 was the last stable of this release client version by Jagex.
On 7 November2019, download links for the client were removed. Access to RuneScape through the Java client was removed entirely on 18 December 2019.[2][3]
- 2Troubleshooting
- 3Editing the client's configuration
- 4Configuration options
- 5Use on Linux
Downloading[edit | edit source]
The download links for the Java client have been removed.
Troubleshooting[edit | edit source]
If users are having problems with the Game Client, they are recommended to try following these steps in order and see if they can resolve their problem.
Set up exceptions to your firewall for RuneScape[edit | edit source]
- Some security programs including 360, Avast, AVG, Avira, Bitdefender, BullGuard, K9 Web Protection, McAfee and Outpost have blocked or interfered with Java-based applications like RuneScape in the past. If you're getting a firewall error, make sure you have added exceptions for: Java.exeJagexLauncher.exe *.runescape.com For instructions on how to do this check your antivirus/firewall software's website.
- On your router, you would need to open the following ports: 443, 43594 and 43595 This will vary depending on your make and model of router, and instruction booklets are often included with your router or can be found on the manufacturers website. You can also find information on How to Forward a Port
Clear the game cache[edit | edit source]
If you're game has crashed or if you've experienced any errors such as a black screen, graphical bugs or you're getting no sound, you'll need to delete the following files and folders if they exist on your Windows computer.
Note: After clearing your cache, you may lag until the cache gets rebuilt to 100%. You can review your cache %by using the displayfps command on the Developer console.
Launching the client on Safe Mode[edit | edit source]
To start the game client on safe mode, press repeatedly or hold the letter 'S' when you launch the game client. After you've reached the login screen, you can play the game using the Safe Mode display mode but it is recommended to switch to DirectX if you're using Windows or OpenGL if you're using Mac or Linux. Both DirectX and OpenGL should give you a higher fps than Safe Mode.
Error applying transforms[edit | edit source]
If you get a message saying 'error applying transforms' when attempting to install the client, switching your computer's language to English should make the error go away letting you install it.
Unable to create advertising[edit | edit source]
If you're getting this error, you might need to clear your game cache. If you're trying to play with 3 or more simultaneous instances of the client, click the icon a bunch of times really quickly.
Unable to load parameter[edit | edit source]
This error means the shortcut you use to launch the game is having a problem.
- Right click shortcut
- Properties
- Target
- Edit target parameter to match:
C:Users<user_name>jagexcachejagexlauncherbinJagexLauncher.exe runescape
When the Game Client loads, I get a page saying 'Page cannot be displayed'[edit | edit source]
This is most likely to do with a personal firewall which is blocking the Client from accessing the internet. Users will have to allow the program ('runescape.exe' or 'JagexLauncher.exe' for Windows users, and 'RuneScape.app' for Mac users) access to the internet in order for it to work. If that doesn't work, try changing the world the client connects to or use a VPN.
When clicking on the map, the screen goes black, as if loading, but never loads[edit | edit source]
Click on the screen, and if it doesn't load, open another program to minimize it. If that doesn't work then just exit the program and restart it.
(Mac) When I try resizing the window, the client locks up[edit | edit source]
The Mac version of the client cannot be resized in software mode. Switching to OpenGL solves the problem and will allow access to the resizable and full screen options. The window can be resized in OpenGL, and the graphics can subsequently be switched back to software mode without problems.
Too many login attempts from your address[edit | edit source]
This is a known issue some Players are currently experiencing. If it happened to you, report it to Jagex. You might also be able to login by using a mobile connection or VPN.
Editing the client's configuration[edit | edit source]
If you update your client, you will have to apply the changes made to the configuration again.
Windows[edit | edit source]
On Windows the configuration is stored in the file
%USERPROFILE%jagexcachejagexlauncherrunescaperunescape.prm
To edit this file type
%USERPROFILE%jagexcachejagexlauncherrunescape
into Explorer's address bar and open runescape.prm
in Notepad. If you can't save, make sure the game is closed and try again.macOS[edit | edit source]
On macOS, the configuration is stored in the file
Runescape.app/Contents/Info.plist
To edit this file open Terminal and type the following:
Configuration options[edit | edit source]
Connecting to Old School, Classic, Beta[edit | edit source]
- Open
%USERPROFILE%jagexcachejagexlauncherrunescaperunescape.prm
in Notepad. - Remove the flag:
- Replace it with one of the following:
- Classic:
-Dcom.jagex.config=http://classic3.runescape.com/jav_config.ws
- Old School:
-Dcom.jagex.config=http://oldschool.runescape.com/jav_config.ws
- RuneScape 3:
-Dcom.jagex.config=http://www.runescape.com/jav_config.ws
- Beta:
-Dcom.jagex.config=http://www.runescape.com/jav_config_beta.ws
- Classic:
- Save and close the file
Change the world the client connects to[edit | edit source]
- Open
%USERPROFILE%jagexcachejagexlauncherrunescaperunescape.prm
in Notepad. - Remove the flag:
- Replace it with the # of the world you want to connect to as shown on the following example:
- Old School (world 330):
-Dcom.jagex.config=http://oldschool30.runescape.com/jav_config.ws
- RuneScape 3 (world 34):
-Dcom.jagex.config=http://world34.runescape.com/jav_config.ws
- Old School (world 330):
- Save and close the file
Increasing maximum heap usage[edit | edit source]
You can increase the amount of maximum heap the RuneScape client uses and it is often a recommended step in troubleshooting on the official Forum. To do this:
- Open
%USERPROFILE%jagexcachejagexlauncherrunescaperunescape.prm
in Notepad. - Change
-Xmx384m
to a higher value;-Xmx512m
is recommended - Save and close the file
Allocating too much memory to the heap can cause game instability. If, after increasing the amount of maximum heap, your client begins to crash to desktop, decrease the maximum heap size and try again.
-Xmx512m
is generally considered a safe heap size, and should not be increased unless absolutely necessary.Using a different garbage collector[edit | edit source]
You can optionally choose a different garbage collector for the RuneScape client to use. This will potentially improve map loading times, and decrease lag caused by garbage collection.
To make the changes to your Client's configuration file:
- Remove the following flags
- Add the following flags:
SSL connectivity[edit | edit source]
Enabling SSL connectivity will help you if you're connecting via a mobile network, restrictive network, proxy, or firewall.
To do this add one of the following flags to the configuration file:
or
Multiple client configuration[edit | edit source]
- Go to
%USERPROFILE%jagexcachejagexlauncher
- Create a new folder and name it either 'oldschool' or 'classic' for whichever version you'd like to create a client for
- Copy the .prm file from
%USERPROFILE%jagexcachejagexlauncherrunescape
- Paste the .prm file inside the newly created folder named 'oldschool' or 'classic'
- Rename the file to match the folder;
oldschool.prm
orclassic.prm
- Open the renamed .prm file in Notepad.
- Remove the flag:
- Replace it with the corresponding flag:
- Classic:
-Dcom.jagex.config=http://classic3.runescape.com/jav_config.ws
- Old School:
-Dcom.jagex.config=http://oldschool.runescape.com/jav_config.ws
- Classic:
- Save and close the file
- Locate the Game Client shortcut and make a copy of it; By default, the Game Client shortcut is found on your desktop
- Right-click the new shortcut copy, and select 'Properties' from the context menu
- Under the shortcut tab, find the box right of the word 'Target'; It should display
C:UsersUSERPROFILEjagexcachejagexlauncherbinJagexLauncher.exe runescape
- Change the
runescape
on the end to match the the folder name created in step 2 - Click OK to save the changes made
Use on Linux[edit | edit source]
Create an executable sh file and add the following to it (you must have 7zipinstalled before running):
Alternative use on Linux[edit | edit source]
It is possible to use the windows client on linux systems as follows:
- Download the windows client (Runescape.msi) from the RuneScape website
- Rename it to a zip file (eg RuneScape.zip)
- Extract RsLauncher.cab from the zip file
- Rename RsLauncher.cab to RsLauncher.zip
- Extract JagexAppletViewerJarFile.XXXXXXXX_XXXX_XXXX_XXXXXXXXXXXXXX from RsLauncher.zip (X is a hex digit)
- Rename JagexAppletViewerJarFile.XXXXXXXX_XXXX_XXXX_XXXXXXXXXXXXXX to jagexappletviewer.jar
- Extract JagexAppletViewerPngFile from RsLauncher.zip
- Rename JagexAppletViewerPngFile to jagexappletviewer.png
- Copy jagexappletviewer.jar to ~/.jagex/runescape/bin/jagexappletviewer.jar
- Copy jagexappletviewer.png to ~/.jagex/runescape/images/jagexappletviewer.png
- Copy the following 3 lines into a text file called runrs.sh in your home directory:
Everything from '/usr' to '/images' is a single command line in the script file. You can also increase the memory allocation (-XmxNNNm where NNN is a number) if you want. See 'man java'.
12. Make runrs.sh file executable (chmod a+x ~/runrs.sh)
13. From a terminal. ~/runrs.sh
14. You may also need to create the following directories:
13. From a terminal. ~/runrs.sh
14. You may also need to create the following directories:
~/.jagex_cache_32 ~/.jagex_cache_32/runescape ~/c:
You could also get the client to be installed by downloading the program Wine and using it to install the client. (confirmed for Debian Squid, and it also works out-of-the-box on Linux Mint 12 with Cinnamon, though not with XFCE4 (and maybe some other DE's). More confirmation needed)
Java on Linux[edit | edit source]
There are two main versions of Java available, OpenJDK and Oracle. For each, version 6 or version 7 can be used. There may be issues associated with some versions, for example oracle versions 1.7 may work only in software mode, while 1.6 will work in OpenGL (which is preferred.). OpenJDK-7 should also work in OpenGL.
To install OpenJDK version 7 on Ubuntu 12.10, type in a terminal:
It is possible to install a version of Java specially for the game client, so that it doesn't need to change the Java used by other applications on the operating system. This can be done for example by downloading and installing the Oracle Java packages without using the OS package manager. It can then be installed in its own directory, for example /usr/lib/jvm/jre1.7.0_13/, and then for the simple script above, the final 'run the client' line the following would be used instead of just 'java':
Official changelog[edit | edit source]
- 1.0.0 - Initial release.
- 1.0.1 - Fixed bug where Vista and 7 users need to disable UAC to be able to install client, added an options bar with a language setting on top.
- 1.0.2 - Uses its own interface instead of the default Windows style for the language setting. Client automatically removes the languages menu and copyright notification upon log in.
- 1.0.4 - Client scrollbar changed.
- 1.1.0 - Client update on 17 October.
- 1.2.0 - Possibly unsuccessful attempt to remedy lag problems after the bot nuke event.
- 1.2.3 - Fixed the removal of the languages menu and copyright notifications when logging in on Linux and Mac, plus providing a direct link for the jagexappletviewer.jar for use by custom clients like the RSU-Client and other Linux Clients.
- 1.2.4 - The client may now be launched directly from the website.[4]
- 1.2.5 - Added support for the Local timestamps in chat boxInterface setting.
- 1.2.6 - Fixed an issue that prevented use on mobile networks.
- 1.2.7 - Fixed scrollbars in adverts.
Update history[edit | edit source]
The update history project is a work-in-progress – not all updates to this topic may be covered below. See here for how to help out!
- patch9 December 2019 (Update):
- Updated the Java client removal messaging.
- patch11 November 2019 (Update):
- Added a daily popup for Java to inform about the Java client being no longer supported.
- Fixed an issue where player appearance would cause a crash.
- Tidy up some legacy code on the back end systems.
- patch7 October 2019 (Update):
- Fixed an issue where Java client would crash when opening the bank.
- patch16 September 2019 (Update):
- Corrected a client crash from rapidly selecting and clearing achievement paths.
- patch29 April 2019 (Update):
- Google login is no longer supported on the Java client.
- patch1 April 2019 (Update):
- Particles within the black stone dragon encounter appear above the ground symbol when playing on the Java Client.
- patch11 March 2019 (Update):
- Fixed an issue with Quest Journal that was causing issues in Java.
- patch25 February 2019 (Update):
- Fixed a crash in Elite Dungeons when using the Java client.
- patch11 June 2018 (Update):
- Selecting ironman game modes in account creation when using the Java client will now correctly apply the selection.
- patch14 May 2018 (Update):
- Fixed numerous client crashes that could occur in specific situations.
- patch23 October 2017 (Update):
- Players can once again switch graphical toolkits when using the Java client.
- patch10 July 2017 (Update):
- A client crashing issue that previously occured after using the Communication device during the Dishonour among Thieves quest in the Java client has been fixed.
- hotfix3 July 2017 (Update):
- 26/06, 11:00 UTC: Environment overrides were stopped from applying when using the Java client, since they were not applying correctly.
- hotfix26 June 2017:
- Environment Overrides in Java have been disabled. [5]
![Java Java](/uploads/1/2/7/6/127683234/326661508.jpg)
- patch5 June 2017 (Update):
- Fix for volumetric overrides.
- Fix for quick chat.
- patch15 May 2017 (Update):
- It is no longer necessary to auto-setup every time when graphics drivers are out of date.
- patch6 March 2017 (Update):
- The lobby no longer flickers when using the Java client.
- patch27 February 2017 (Update):
- The shoreline wobbegong fishing spot is once again visible when using the Java client. Wobbegongs out in the sea remain unchanged.
- patch25 July 2016 (Update):
- Added engine support for Arc content.
- patch11 July 2016 (Update):
- A fix for NPCs occasionally not appearing in the correct positions has been implemented.
- patch20 October 2014 (Update):
- Point lights will correctly appear in java and HTML5 when switching to an instanced area not on level 0.
- patch28 February 2014 (Update):
- A fix has been applied for a rare crash on ATi cards.
- A fix has been applied to the camera angles when forcing the camera to move to a new position.
- A fix has been applied to remove some instances of double hitbars.
- A fix for grass appearing through other objects has been implemented.
- A fix for ATI cards not displaying large models correctly has been added.
- A fix for Mac screens flickering black while moving around the world has been implemented.
- patch23 September 2009 (Update):
- Changed some core code to fail gracefully rather than cause the game client to crash.
- patch9 September 2009 (Update):
- We've also fixed a large majority of game crashes that users have been experiencing.
- patch6 May 2009 (Update):
- Fixed a render issue with the various full helms and your chathead.
- Fixed an animation that was playing faster than intended.
Trivia[edit | edit source]
- Previously, if you dragged a desktop icon of a website on the old client, the program could be used to browse any website.
- The client source bundle (jagexlauncher-src.tar) consists of 7.826.577 (7.8 million) lines of code. This includes 89 lines of C++ code for the Jagex Launcher itself, and approximately 7.8 million lines of Oracle's JDK.
- In 2011, a regional lockout function was implemented into the client which could prevent players outside of select countries from accessing Jagexservers. This function remained unused since implementation.
References[edit | edit source]
![Java Java](/uploads/1/2/7/6/127683234/693813352.gif)
- ^Mod Philip. 'New Runescape Client.' 28 March 2015. Developer Blogs Forums.
- ^Jagex. 'The future of RuneScape technology.' 7 November 2019. RuneScape News.
- ^Update:Game Update: Christmas 2019 & Daily Challenge Rework
- ^Mod Rascasse. PSA: Google Chrome will no longer support Java meaning no Runescape. reddit. 30 March 2015.*
- ^Jagex. Mod Shauny's Twitter account. 26 June 2017. (Archived from the original on 2 February 2020.) Mod Shauny: '#RSHotfix: We've disabled Environment Overrides in Java while we investigate a full fix, this should stop issues like this image.'
Mechanics | |
---|---|
Engine | |
Products | |
Performance | |
Graphics | |
Servers |
Retrieved from ‘https://runescape.wiki/w/Game_Client?oldid=31585786’
Java is a computer programming language that is designed to let application developers “write once, run anywhere”, meaning that code that runs on one platform (OS X, Windows, Android) does not need to be recompiled to run on another. Java is an Oracle Corporation product.Java is used both by applications and web browsers. However, the nature of Java means that it is, i.e., using Java could make it easier for bad people to get their hands on your data.For this reason, Apple has chosen to stop including Java with OS X for security reasons and because most people don’t need it.There are two very popular games, Minecraft and Runescape, that both require Java in order to run.
The Mac version of the online backup service CrashPlan needs Java, but interestingly the Windows version of the client does not. Adobe Creative Suite also requires Java to be installed for some of the features to work. For instance, you can’t install Illustrator without first installing Java, but you can install Photoshop. OpenOffice and NeoOffice, two alternatives to Microsoft’s Office suite, are two more Mac-based applications that require Java for some of their main features, most notably the OpenOffice database application Base, to function properly.That’s about it for most of the mainstream desktop applications that are out there. There are more niche products that require it, but if you are using these applications, you probably already know if they require Java.The Bottom LineIf you want to be the most secure about Java and don’t have any applications that require itusing Software update. This update uninstalls the Apple-provided Java applet plug-in from all web browsers.
Office vba functions. If there are no records 'we won’t execute any code in the if.end if statement.MoveLast.MoveFirst 'It is not necessary to move to the last record and then back 'to the first one but it is good practice to do so. While (Not.EOF) 'With this code, we are using a while loop to loop 'through the records.
To use applets on a web page, click on the region labeled “Missing plug-in” to go download the latest version of the Java applet plug-in from Oracle. This update also removes the Java Preferences application, which is no longer required to configure Java applet settings.If you have applications that require Java and you don’t have itIf you have applications that require Java, and all you want to do is disable Java on the internet, you can turn off Java in Safari. Open Safari’s Security Preferences and uncheck the Enable Java checkbox to turn off Java in Safari. As an alternative, if you have multiple browsers installed, like Chrome or Firefox, you can elect to pick just one browser to use with Java. Choose which browser you want to use Java with and only enable Java in that browser’s preferences.For the most part, the majority of users can get by without ever installing Java on their Macs and never know what they were missing.
![](/uploads/1/2/7/6/127683234/426290274.jpg)