Developer console

From Darkan
Jump to navigation Jump to search
Console screen view (with commands). (Click image for larger size.)

The Developer console has been around for a long time<ref>http://www.youtube.com/watch?v=pXcs4O9jMSc</ref>, but was only made available to players with the release of Z-buffering on 15 September 2010. It may, according to Jagex, "prove useful in tracking down the cause of more technical issues with the client on your computer." You can view a list of commands by typing either help or commands in the window. It also displays RuneScape's Build number in the lower right corner.

The latest build number is Build 742 1.

To get to this console press the [`] (quote/grave accent) or [²] (superscript 2). It is found to the left of the '1' key on most QWERTY keyboards. The tilde [~] is on the same key, on some keyboards. Typing in the alt-key code for ² (Alt+0178) will also open the console. If you find yourself unable to close it, try holding [shift] while pressing any of these buttons. The console is useable on the login screen.


Commands

File:Fps counter bug.png
God Wars Dungeon killcounts and the XP counter are displayed at the same place as the FPS.

The list of current commands are:

Command Action
commands List Commands
cls Clears the console screen.
displayfps Toggles frames per second (FPS) and other information screen
renderer Prints graphics renderer information
heap Prints Java memory information
getcamerapos Prints location and direction of the camera for use in bug reports
help Lists commands

When one logs out, all entered commands will be deleted and cannot be retrieved.

Player or Forum Moderators also only have access to the standard Player commands, as the Console is primarily only for Jagex Moderator usage.

Alternative appearance

Occasionally the developer console will change appearance, usually in relation to an event.

  • In build 666, the background colour changed from purple to red, probably as a pun referring to the fact that '666' is considered the devil's number and hence, red. Later on, this was confirmed as when the 667 build was released, the colour changed back to purple.
  • During the 2011 Christmas Period the Developers Console featured snow flakes on the interface.

Trivia

  • Pressing the "Page Up" or "Page Down" keys on your keyboard can list the previously used commands in the Developer console.
  • Text that has been copied from another source can be pasted into the console using Control-C (copy) and Control-V (paste). Text in the console can be copied using Control-A (select all) and then Control-C when the console is open.
  • This is the first time ever that Jagex has enabled access to the very tools they use to develop the game. The developer's console available to the players is a restricted version, so players cannot affect the game in any way with it.
  • When the developer's console is open, clicking somewhere will have the normal effect. The keyboard commands, such as the F1-F5 hotkeys or the arrow keys that move the camera position, won't work until the player closes the developer's console again.
  • When one enters a command, the time of entering it is displayed in UTC.
  • The 'cls' command will clear the console, but will not delete the previously entered commands. When one has cleared the console, and then presses Control-A they will still select all hidden previous commands (and any commands not hidden). This can then be copied and pasted somewhere to see the cleared commands.
  • You can not enter text or rotate the camera in the game while the developer's console is open (the only way to rotate the camera is pressing the scroll button down on your mouse).
  • The developer's console can be used as a temporary extra long notes. It can be used to track doors while dungeoneering, especially on large floors.
  • In the "DisplayFPS" command under FPS numbers 0-19 are red, and 20+ are yellow. Red numbers for FPS mean you might experience lag or disconnection. The highest FPS number you can get is 50 (confirmed by Jagex).
  • Since the beginning of 2012, there have been severe FPS issues. Many players report average FPS of around 10. Many players use the "DisplayFPS" command to check their personal FPS.

References

<references/>