Post by scotty on Sept 1, 2008 13:46:59 GMT -5
Since I don't want any problems in the server with noobs not knowing how to role play, i'll make this for you.
1) Roleplaying is acting out parts of real-life, but to the point where you know it isn't real-life.
2)
A-
There are things called metagaming for roleplaying servers; metagaming is when you assume you know someone's identity or standing without having been introduced.
B-
There is also something called powergaming; powergaming is when you abuse a * command in a manner that isn't realistic... i.e.-
Nathan Clipso rapes Niko Wofl!
as a * command would be severe powergaming, as it doesn't give Niko an opportunity to defend himself.
3) Most roleplaying games have jobs, a currency system, and attributes.
For "The Specialist" modification for Half-Life (Gold-Source Engine) there is a job, a currency system, and a skill-attribute system. These, of course, are plugins that are possible because of third-party mini-addons like amx and amxx, which was the continuation of amx.
4)
A-
To DM, is to deathmatch. Which is what you would normally do in a classic TS (The Specialist) server. It is what happens when you kill people for no real reason other than that you wanted to, or in the act of killing them you failed to roleplay it (hence the common term, "you fail at RP").
B-
There is also the act of an RK, which is Revenge Killing. That's a horrible thing to do when attempting to roleplay, as it is killing somebody out of anger or a feeling of injustice after having been killed. In short, it is Revenge Killing. If somebody DMs you, or CKs (which will be explained next), you are not to even pass a second glance as if you still knew them after respawning.
C-
Now, for CKing. That is called character-killing; which generally occurs when you are in roleplay, everything is fair, and your character dies... for good, that is. If you are CKed, you have no right to complain, as you usually agree to have that occur... or are aware that it may happen. It is okay to keep the same name & job after such actions, since it is a video game & can't be expected to resemble real-life too closely.
5) In roleplaying servers & games, it is critical that you obey the rules, act out in accordance to what the laws allow you to do, and respect fellow players & admins.
It is sometimes difficult to respect fellow players, and especially admins, in first-person shooters like TS; as everything moves very fast, and roleplaying isn't any fun when you must wait a minute or two for each thought to go forward through a "/me" command. I will explain how to work through that next...
6) To work through the issue of slow-paced roleplaying, you should use binds. A bind is usually a key you have scripted to perform a specific action; more complex actions require alias commands to be setup and bound to said alias command. I will give examples in the following...
Examples-
bind b "say * holds hostage down, pointing a gun into his back."
That will roleplay out taking a hostage, letting him know you will have a legitimate reason to character-kill him, or her, should they attempt to flee.
(On a side note, hostages attacking, or killing, the hostage-taker is poor RP, if the hostage-taker used such a * command & gave two or three seconds for reaction)
bind v "say /s stay away or the hostage gets it!"
bind v "say shout stay away or the hostage gets it!"
Depending on if you use /s, a shorter command script to use the shout feature, or type shout out fully, is your choice... I recommend /s though, as Half-Life (Gold-Source Engine) is unable to extend chat to accommodate short script commands like shout. Those commands, however, should show roleplaying police & civilians that they aren't to interfere in your business, lest you kill somebody in roleplay.
That will be all for those examples in bindings, if you desire more information; PM me & I will give you an example alias script to drop all weapons, and drugs, instantly (can be useful when PD surrounds you).
7) Now, I will give a listing of basic commands you may execute in-game, and where they may be useful -
* ACTION
-That is good to make an action statement out of chat, for performing an action in roleplay (you must act it out yourself, it will only alert people to your doings).
/shout WORDS
-This will use a shout command, making what you say in text reach out farther in radius, and generally forcefully capslocking the text put in.
/quiet WORDS
-This will make the chat radius for said words very small, enabling only those within hugging distance of hearing you.
/rules
-This will display the rules of the server, out of character ones, so you know how to behave towards admins & fellow players, and whether or not deathmatching is tolerated.
/laws
-Most servers will have the in-character roleplaying laws displayed upon this command, but Prodigy TSRP is pretty sweet in that /laws alerts you to these
/laws1
/laws2
/laws3
-A series of laws through several commands, listed from 1 (minor felonies), to 3 (major felonies).
/cuff
-If you are a cop, some servers allow you to use that command to cuff people. I have not had a job in the PD department, so I personally don't know what their commands are. Hink Dink can help you out, more than enough, if you desire more information in that area.
That will be all, for the commands at least.
Cool This is a very important part, as I will help guide you into what you are to do if somebody is deathmatching when they shouldn't be, harassing you, or calling you names...
Open up your console, using the "~" key (otherwise known as the tilda key), and type these two commands, one at a time, in the console -
status
condump
This way, you will be able to collect a basic chatlog and the person's steamID, whoever it was that wronged you when you were forced to do this. Avoid spamming the condump command, as it creates the .txt files (new ones each time you use the command, it will not overwrite old condumps) in your modification folder.
Another thing you can do is press your Prt Scrn (aka Print Screen) button, usually found just to the right of your "F12" key, and above insert (if you use standard keyboards they dish out for AMD computers, in USA). That way, you can make a photographic copy of whatever was on your screen at the time; using that key to collect racial comments, insults, or people who have DMed, is very helpful in getting them punished.
There is also the record command, to make videos of people who have wronged you... they are much more solid evidence, perfect brick walls even, against people; should you take them properly, that is. So you type this in console -
record DEMONAME
DEMONAME, is whatever you want your ".DEM" file to be named inside of the modification folder (if you play CS:S, and do that, it is in the CS:S/CStrike folder, and likewise for other mods & games DIR paths).
Before typing -
stop
in your console, it is best that you type -
status
first... that way the demo will have the steamID recorded in it as well, as there is a program called "Demo Freak" that allows you to view the steamIDs of those playing the game when viewing ".DEM" files, so long as status was typed into the console before the demo was stopped.
You *must* be careful with recording demos, for recording two demos of the same name will overwrite the older one, making whichever one to be your latest to be your only demo.
1) Roleplaying is acting out parts of real-life, but to the point where you know it isn't real-life.
2)
A-
There are things called metagaming for roleplaying servers; metagaming is when you assume you know someone's identity or standing without having been introduced.
B-
There is also something called powergaming; powergaming is when you abuse a * command in a manner that isn't realistic... i.e.-
Nathan Clipso rapes Niko Wofl!
as a * command would be severe powergaming, as it doesn't give Niko an opportunity to defend himself.
3) Most roleplaying games have jobs, a currency system, and attributes.
For "The Specialist" modification for Half-Life (Gold-Source Engine) there is a job, a currency system, and a skill-attribute system. These, of course, are plugins that are possible because of third-party mini-addons like amx and amxx, which was the continuation of amx.
4)
A-
To DM, is to deathmatch. Which is what you would normally do in a classic TS (The Specialist) server. It is what happens when you kill people for no real reason other than that you wanted to, or in the act of killing them you failed to roleplay it (hence the common term, "you fail at RP").
B-
There is also the act of an RK, which is Revenge Killing. That's a horrible thing to do when attempting to roleplay, as it is killing somebody out of anger or a feeling of injustice after having been killed. In short, it is Revenge Killing. If somebody DMs you, or CKs (which will be explained next), you are not to even pass a second glance as if you still knew them after respawning.
C-
Now, for CKing. That is called character-killing; which generally occurs when you are in roleplay, everything is fair, and your character dies... for good, that is. If you are CKed, you have no right to complain, as you usually agree to have that occur... or are aware that it may happen. It is okay to keep the same name & job after such actions, since it is a video game & can't be expected to resemble real-life too closely.
5) In roleplaying servers & games, it is critical that you obey the rules, act out in accordance to what the laws allow you to do, and respect fellow players & admins.
It is sometimes difficult to respect fellow players, and especially admins, in first-person shooters like TS; as everything moves very fast, and roleplaying isn't any fun when you must wait a minute or two for each thought to go forward through a "/me" command. I will explain how to work through that next...
6) To work through the issue of slow-paced roleplaying, you should use binds. A bind is usually a key you have scripted to perform a specific action; more complex actions require alias commands to be setup and bound to said alias command. I will give examples in the following...
Examples-
bind b "say * holds hostage down, pointing a gun into his back."
That will roleplay out taking a hostage, letting him know you will have a legitimate reason to character-kill him, or her, should they attempt to flee.
(On a side note, hostages attacking, or killing, the hostage-taker is poor RP, if the hostage-taker used such a * command & gave two or three seconds for reaction)
bind v "say /s stay away or the hostage gets it!"
bind v "say shout stay away or the hostage gets it!"
Depending on if you use /s, a shorter command script to use the shout feature, or type shout out fully, is your choice... I recommend /s though, as Half-Life (Gold-Source Engine) is unable to extend chat to accommodate short script commands like shout. Those commands, however, should show roleplaying police & civilians that they aren't to interfere in your business, lest you kill somebody in roleplay.
That will be all for those examples in bindings, if you desire more information; PM me & I will give you an example alias script to drop all weapons, and drugs, instantly (can be useful when PD surrounds you).
7) Now, I will give a listing of basic commands you may execute in-game, and where they may be useful -
* ACTION
-That is good to make an action statement out of chat, for performing an action in roleplay (you must act it out yourself, it will only alert people to your doings).
/shout WORDS
-This will use a shout command, making what you say in text reach out farther in radius, and generally forcefully capslocking the text put in.
/quiet WORDS
-This will make the chat radius for said words very small, enabling only those within hugging distance of hearing you.
/rules
-This will display the rules of the server, out of character ones, so you know how to behave towards admins & fellow players, and whether or not deathmatching is tolerated.
/laws
-Most servers will have the in-character roleplaying laws displayed upon this command, but Prodigy TSRP is pretty sweet in that /laws alerts you to these
/laws1
/laws2
/laws3
-A series of laws through several commands, listed from 1 (minor felonies), to 3 (major felonies).
/cuff
-If you are a cop, some servers allow you to use that command to cuff people. I have not had a job in the PD department, so I personally don't know what their commands are. Hink Dink can help you out, more than enough, if you desire more information in that area.
That will be all, for the commands at least.
Cool This is a very important part, as I will help guide you into what you are to do if somebody is deathmatching when they shouldn't be, harassing you, or calling you names...
Open up your console, using the "~" key (otherwise known as the tilda key), and type these two commands, one at a time, in the console -
status
condump
This way, you will be able to collect a basic chatlog and the person's steamID, whoever it was that wronged you when you were forced to do this. Avoid spamming the condump command, as it creates the .txt files (new ones each time you use the command, it will not overwrite old condumps) in your modification folder.
Another thing you can do is press your Prt Scrn (aka Print Screen) button, usually found just to the right of your "F12" key, and above insert (if you use standard keyboards they dish out for AMD computers, in USA). That way, you can make a photographic copy of whatever was on your screen at the time; using that key to collect racial comments, insults, or people who have DMed, is very helpful in getting them punished.
There is also the record command, to make videos of people who have wronged you... they are much more solid evidence, perfect brick walls even, against people; should you take them properly, that is. So you type this in console -
record DEMONAME
DEMONAME, is whatever you want your ".DEM" file to be named inside of the modification folder (if you play CS:S, and do that, it is in the CS:S/CStrike folder, and likewise for other mods & games DIR paths).
Before typing -
stop
in your console, it is best that you type -
status
first... that way the demo will have the steamID recorded in it as well, as there is a program called "Demo Freak" that allows you to view the steamIDs of those playing the game when viewing ".DEM" files, so long as status was typed into the console before the demo was stopped.
You *must* be careful with recording demos, for recording two demos of the same name will overwrite the older one, making whichever one to be your latest to be your only demo.
