Table of Contents

• Table of Contents
• Information
  • General RuneScape Commands
    • Setting your RSN
    • Adventure Log Lookup
    • Stats Lookup
      • RuneScape 3
      • OldSchool RuneScape
    • Quest Lookups
    • Travelling Merchant
  • Host Forms
    • RuneScape 3 Host Forms
    • OldSchool RuneScape Host Forms
  • Splitting Loot
    • Splitting Loot Normally
    • Splitting With Additional Percentages
    • Splitting Loot ~ AoD 7 - 10
      • 7 Mans
      • Larger Team Size
    • Splitting Loot ~ Nex AoD
  • Achievement Tracker
    • Information
    • Enabling or Disabling the Achievement Tracker
    • Tracking Users
    • Untracking Users
    • Display All Tracked Users
  • Jagex Clock
    • Enabling or Disabling Jagex Clock
    • Having Roles Mentioned
    • Creating a Reaction Role Embed
  • Pylon & Rex Commands
    • Pylon
    • Rex
    • Pylon Notifications
      • Enabling Pylon Notifications
      • Disabling Pylon Notifications
      • Pylon Notification Settings
      • Enabling Rex Notifications
      • Disabling Rex Notifications
      • Rex Notification Settings

---

Information

The commands in this section are designed to help you with information about RuneScape. They allow you to quickly find information about certain events within RuneScape, host groups for bosses, split loot easily, set up an Achievement Tracker for your server and more.

Note: Certain permission might be required..

General RuneScape Commands

Setting your RSN

This commands sets your RuneScape name for various other commands, like Alog, Stats, 07Stats and more.

-setrsn followed by your RuneScape Username.

Example:

-setrsn Friendliness

This would set my RuneScape name to Friendliness.

Adventure Log Lookup

This command allows you to display what's currently listed on someone's Adventure Log on RuneScape 3.¹

Example:

-alog would look for your currently set RuneScape name, and look that one up.

-alog followed by a username, would look up the username you gave as argument.

Stats Lookup

RuneScape 3

With the stats command you can look up someone's stats on RuneScape 3.¹

Example:

-stats would look up the stats for the RuneScape name you set with the -setrsn command.

-stats followed by a username, would look up the stats of the username you gave as argument.

OldSchool RuneScape

This command lets you look up someone's stats on OldSchool RuneScape.

Example:

-07stats would look up the stats for the RuneScape name you set with the -setrsn command.

-07stats followed by a username, would look up the stats of the username you gave as argument.

Quest Lookups

This command can be used to see if you've done, can do or can't do a quest. It also displays information about the quest, like if it's free or members only and the amount of Quest Points it gives.

-quest "Username" "Quest Search Terms"

Example:

-quest "Friendliness" "One"

This command would look up all of the quests with "One" in their name, for the user "Friendliness".

Travelling Merchant

The following commands allow you to look up information about the Travelling Merchant's stock, such as the current stock, the stock for the coming week and when an item will be in stock in the future.

If you'd like to be notified about the stock every reset, please take a look at Jagex Clock as it's incorporated there.

-merch looks up the current stock.

-merchweek sends you the stock for the coming week.

-merchwhen followed by an item, would look up when the next time an item will be in stock.

Example:

-merchwhen reaper would show you the next 3 times the gift of the reaper will be in stock.

Host Forms

Host forms are basically sign-up sheets, they let you easily form groups or see what people are interested in. There are forms available for all kinds of things, going from bosses to minigames and various other things. These forms will automatically expire, 2 weeks after creation, unless defined otherwise.

If you'd like to see a host form added, please use the -suggest command and suggest it!

An example of those can be found below:

Note: This feature will be reworked in the near future, allowing you to customise them further.

RuneScape 3 Host Forms

This command shows you the available bosses and options for the RuneScape 3 host forms.

-bosses

OldSchool RuneScape Host Forms

The following command shows you the available bosses and options for the OldSchool RuneScape host forms.

-osrsbosses

Creating a Host Form

The following command can be used to create a host form with one of the available options lised in the previous sections.

The only required parameter is the name of the option or boss you'd like to host a form for. There are also various optional parameters you can give, such as: expiry, channel and a description.

Expiry is an integer, either 0 or 1, and is set to 1 by default. This decides whether the form will automatically expire, 2 weeks after its creation or not. When it's set to 0, the form will not expire unless the host clicks the ✅ emote.

Channel is a text-channel for the host form to be posted to, for example #general.

Description is a small description to add to the form, for example Have fun!. It's also possible to add a maximum amount of players that can sign up, to do this put -max followed by a number in the description.

The syntax would be as follows:

-host [bossname] [expiry][^3] [channel][^3] [description][^3]

Example: A basic host form would be created as follows:

-host aod this would create a host form for Nex: Angel of Death.

A host form with a description:

-host vorago Fun times fighting a large boulder would create a host form for Vorago, with the description Fun times fighting a large boulder.

A permanent host form:

-host interest 0 would create a permanent host form, this form would not expire unless the host clicks ✅

A host form in a specific channel: -host vorago #general would send a form for Vorago to the #general channel.

A more elaborate host form: -host vorago 0 #general Fighting a large boulder -max 5 would create a permanent host form, in the #general channel with the description Fighting a large boulder where a maximum of 5 players can sign up.

Note: This feature will be reworked in the near future, the syntax will likely change to be more user-friendly.

Splitting Loot

This command calculates how much everyone needs to be paid to get a split, you can also optionally include additional players, by adding their additional % of the split.

Splitting Loot Normally

To split without giving anyone an extra percentage, you can type:

-split [Amount] [Players]

Example:

-split 500 7

This would split 500 Million with 7 players.

Splitting With Additional Percentages

To split while giving several players an additional percentage of the loot, you can type:

-split [Amount] [Players] [First Additional %] ...

Example:

-split 500 7 1 2.5

This would:

• Split 500 Million with 7 players
• Two players are getting an extra percentage
  • The first player gets 1% extra
  • The second player gets 2.5% extra

Note: You can include more additional players that get an extra percentage.

Splitting Loot ~ AoD 7 - 10

This command calculates how much everyone needs to be paid for a split according to the rules in the AoD 7 - 10 Man Discord server.

7 Mans

-splitaod710 [Amount] [Optional Amount of Drops]

Example:

-splitaod710 1000 2 would split 1000 Million with 7 players, where there's been 2 drops, according to AoD 7-10 Man's rules.

Note: If there's only one drop, you don't have to type the amount of drops.

Larger Team Size

You can include an optional amount of drops, in case there was more than one drop in the hour, and an optional Amount of Players, in case the team size was bigger than 7.

-splitaod710 [Amount] [Amount of Drops] [Amount of Players]

Note: If the team size is larger than 7 and there was only one drop, you still have to type 1 for the amount of drops, then followed by the number of players in your team.

Splitting Loot ~ Nex AoD

This command calculates how much everyone needs to be paid for a split according to the rules in the Nex AoD Discord server.

-splitnexaod [Amount] [Optional Amount of Drops]

Example:

-splitnexaod 1000 2 would split 1000 Million with 7 players, where there's been 2 drops, according to Nex AoD's rules.

Note: If there's only one drop, you don't have to type the amount of drops.

Achievement Tracker

Information

This allows an Administrator to enable or disable the tracking of RuneScape 3 Achievements in the server. They can select a channel for these achievements to be sent to.

Once enabled, users can sign up to be tracked and have their Achievements sent to the channel you chose, automatically.

You can see some examples below:

Note: The Achievement Tracker can only track users if their RuneMetrics profile is public.

1

Enabling or Disabling the Achievement Tracker

²

-achievementtracker [Mode] [Channel]

Example: -achievementtracker enable #general

This would enable the Achievement Tracker in the #general channel.

To disable this again, you would have to type:

-achievementtracker disable

Tracking Users

Once the Achievement Tracker is enabled, users can sign up to have their achievements tracked in your server.

This can be done by using the following command:

-track [RuneScape Username]

Example:

-track Friendliness

Untracking Users

To stop tracking a user's achievements, an Administrator can use the following command.

-untrack [RuneScape Username]

Example:

-untrack Friendliness

Display All Tracked Users

An Administrator can use the following command to display all the users that are currently being tracked in your server.

-alltracked

Jagex Clock

This feature sends RuneScape notifications to a channel, such as the changing of the Voice of Seren, Wilderness Warbands, Minigame Spotlights, Raven, Pink Skirt events (the events on the RuneScape in-game calendar), messages when RuneScape is streaming, monthly & weekly resets, rotation cycles for Araxxor, RotS & Vorago and the Travelling Merchant's stock for the day.

Note: I plan on adding more events to the Jagex Clock notifications in the future.

Enabling or Disabling Jagex Clock

To enable or disable this feature, you can use the following commands respectively:

-jagexclock on, followed by a channel enables the feature.

-jagexclock off, followed by a channel disables the feature in your server

Example:

-jagexclock on #general would enable the Jagex Clock feature in the #general channel.

-jagexclock off #general would disable the Jagex Clock feature in the #general channel.

Having Roles Mentioned

The Jagex Clock tracker is also able to create & mention roles when something happens. This command will try to find existing roles initially, if it can't find them it creates them.

The roles it looks for are the following: Amlodd, Cadarn, Crwys, Hefin, Iorwerth, Ithell, Meilyr, Trahaearn, Wildernesss Warbands, Spotlight, Araxxor Rotation, RotS Rotation, Vorago Rotation, Weekly Reset, Monthly Reset and Travelling Merchant.

Use the following command:

-jagexclockroles

Note: I plan on adding more roles to this in the future.

Creating a Reaction Role Embed

If you'd like people to be able to sign up for mentions for the Jagex Clock, there's an easy way to set up reaction roles. You can do this by using the following command: -jagexclockreacts

This will look as follows:

Pylon & Rex Commands

These are commands related to the Pylon in Kharid-Et and the roar of Osseus on Anachronia. With these you can check the status of these pylons or even be notified when the percentage hits 95% of 100%.

Pylon

This command will show you the current Pylon status.

-pylon

Rex

This command will show you the current status of the roar of Osseus.

-rex

Pylon Notifications

Enabling Pylon Notifications

This command² sets up a channel and role to be notified when the Pylon percentage hits 95% and or 100%. The role that is automatically created is @Pylon, unless you choose another role.

-notifypylon enable followed by a channel and optionally a role to enable this.

Example:

-notifypylon enable #general would enable the notifications in the #general channel -notifypylon enable #notifications @Spaghetti would enable the notifications in the #notifications channel, and would ping the @Spaghetti role.

Disabling Pylon Notifications

To disable the Pylon notifications, you can use the following command.

-notifypylon disable

Pylon Notification Settings

This command allows you to change settings for the notifypylon command, such as whether the notifications should ping you, whether you should be notified at 95% or not and whether you should be notified at 100%.

-pylonsettings followed by the mode and then by the setting

Example:

-pylonsettings enable 95 would enable notifications at 95%. -pylonsettings disable 100 would disable the notifications at 100%. -pylonsettings disable ping would disable the role mentions of the Pylon notifications.

Enabling Rex Notifications

This command sets up a channel and role to be notified when the Roar of Osseus percentage hits 95% and or 100%. The role that is automatically created is @Rex, unless you choose another role.

-notifyrex enable followed by a channel and optionally a role to enable this.

Example:

-notifyrex enable #general would enable the notifications in the #general channel -notifyrex enable #notifications @Spaghetti would enable the notifications in the #notifications channel, and would ping the @Spaghetti role.

Disabling Rex Notifications

To disable Rex notifications, you can use the following command.

-notifyrex disable

Rex Notification Settings

This command allows you to change settings for the notifyrex command, such as whether the notifications should ping you, whether you should be notified at 95% or not and whether you should be notified at 100%.

-rexsettings followed by the mode and then by the setting

Example:

-rexsettings enable 95 would enable notifications at 95%. -rexsettings disable 100 would disable the notifications at 100%. -rexsettings disable ping would disable the role mentions of the Rex notifications.

---

1. The RuneMetrics setting in the Account section on the website, has to be set to Public for this to work! ↩ ↩²

2. To use this command, you need either the administrator permission or have one of the Admin Roles. ↩ ↩²