A "Rush Code" is a personalized line of coded symbols which says something about you as a Rush fan. It contains coded information such as how many times you've seen Rush live, your favorite era of Rush's music, and which Rush album you would take with you on a desert island. A Rush code looks something like this: RC1.0 bc g/g 2/0/d/tG MP/+ ~30 gdbkvo+ < 43% [29sep2001] Each Rush Code is different, so they will all look different. The above is just one example. Everybody can automatically generate their own personalized Rush code automatically by answering a few questions on the JavaScripted form here. When your code is generated, you should copy and paste it to a text file and keep it. You can use this code in your email and usenet signature, put it in an "X-RushCode" header if you like, and generally display it anywhere. Other peole who are familiar with the Rush code will be able to tell some basic, unique information about you by looking at your code. Likewise you might see other Rush fans displaying their own code in their own signature files. By understanding the basic rules of how to make and read a Rush Code, you can communicate your personal feelings about Rush to other fans, and know also where they stand. The following are rules for Rush Code. If you want to generate your own Rush Code automatically, go here.
Current
Rush Codes all begin with RC1.0. This indicates that it is "Rush
Code version 1.0." Note that there is also a "Floyd Code"
for fans of Pink Floyd. Rush codes begin with the letters "RC"
and the version.
Variable 1 determines which era of Rush you prefer. Not mentioning an era doesn't necessarily mean you do not like it; only list the era(s) you emphatically PREFER over the others.
Note: you can list more than one era. Ex: ab
Variable 2a indicates whose solo effort(s) you like best.
Ex: a
Variable 2b indicates who your favorite member of Rush is. Choosing one doesn't mean you dislike the others. If you have trouble choosing, pick whichever one you most idolize, or who you'd most like to spend a day with.
Building on the example from 2a above Ex: a/n
Variable 3a indicates the number of times you have seen Rush live. It can be any number. Ex: 3
Variable 3b indicates the number of times you have met a member of Rush in person (this includes members of the touring band and people strongly associated with Rush like Donna Halper, Terry Brown or Andrew MacNaughton.) It can be any number. Building on the example from 3a above, Ex: 3/0
Variable 3c is what eras of Rush have you seen live?
(You may use more than one character to indicate several different eras.) Again building on the previous examples, Ex: 3/0/cd
Variable 3d. This factor is only relevant if variable 3a does not = 0 and indicates whether or not you have ever sat near people who screamed, sang or were otherwise disruptive (intentionally or not) during a concert. If you have never seen Rush live in person, then enter RD as below.
Again building on the previous examples, Ex: 3/0/cd/tinG
Variable 4a is the desert island factor. Which Rush album would you choose if you were stranded on a desert island and could only have one? This uses the standard abbreviations used on the Internet. Ex. PeW
Variable 4b is the "Tai Shan" factor. If you like "Tai Shan" add a "+". If you don't like "Tai Shan" add a "-". If you aren't familiar with the song or have no opinion add a "n". Building on the example from 4a above, Ex: PeW/-
Variable 5 indicates the number of Rush boots you own by purchase, download, copy, or trade. Only full recordings count. (That is, an mpeg of just a song or two doesn't count as a boot, but mpegs of a whole CD counts.) This is a number. Add a "~" before the number if it is just an approximation/guess. Ex: 9
Variable 6 indicates whether you are a musician, and what instrument(s) you play.
You may optionally add a "-" at the end if you're just learning to play the instrument. You may optionally add a "+" at the end if you've had formal training on one or more instruments AND are fully proficient. It is possible to have a "-+" if you are just learning one instrument but very proficient on another. Note: guitarists may optionally use "gl" to indicate they mostly play lead guitar or "gr" if they mostly play rhythm guitar. Just "g" alone is fine as well. Don't indicate both "gl" and "gr"; if that is the case, just use "g" Ex: gb-
Variable 7 indicates your general political/philosophical leaning. Everybody leans one way or another. Pick whichever most RESEMBLES your own position.
Ex: >
Variable 8 in the percentage of your life which you've been a fan. This is automatically calculated in the JavaScript Rush Code page using your birth month and year, and the approximate month and year when you became a Rush fan. It is expressed as a percentile (%) including the percent symbol. The number is always rounded to the nearest 1%, and is only an approximation. Ex: 36%
A Rush Code ends with a date stamp, the date on which you made or updated your Rush Code. The stamp is placed in square brackets [like this] and consists of:
Ex: [29sep2001] Now that you've seen the rules for the Rush Code, here is the author's Rush Code as an example. What can you tell from it? RC1.0 bc g/g 2/0/d/tG MP/+ ~30 gdbkvo+ < 43% [29sep2001]
If you want to generate your own Rush Code automatically, go here.
Notes on syntax: A space in your code indicates where one variable is separated from another variable. A / character is reserved for dividing multiple elements within one variable. Appended symbols do not require a / symbol. (This is more confusing than it sounds. If a variable is split into subsections (i.e. 3a, 3b, 3c) then use a / character to separate those elements--otherwise, leave it out.) Extra thanks to Rick Karhu for creating The (Pink) Floyd Code, which I maintained for a while, and which inspired and served as the starting point for the Rush Code.
Note on versions of The Rush Code:
1.0
Initial debut of the Rush Code. 29 September 2001
|