Post by Xarious on Aug 21, 2016 12:57:02 GMT -5
This post is going to be entirely focused on teaching some of the really basic stuff that most new guys wont know. Yes, I realize I already posted the Game Optimization thing from FL that might make this a bit redundant, but I wanted to slim it down and give a basic newbie guide to knowing the non-combat-related basics.
Opening the Console: On Qwerty keyboards, it is Shift and ~ at the same time. However, if it is not, than it is Shift and whatever key is directly under Esc. You can navigate up and down in the console by using the PageUp and PageDown keys.
How to Bind: Binds are a relatively simple thing. They follow this rule: /bind <key> <action> <applicable value (text, number, etc)>. To explain, let me show a few basic example binds:
/bind 1 say Hiya - This will bind your "1" key so that every time you press it in game, you will say in the chat, "Hiya"
/bind 2 kill - This binds your "2" key to kill you when you press it
/bind 3 sens 4000 - This will bind your "3" key to make your sensitivity 4000
None of these are suggested, they are just examples. Hopefully these make sense. Below are a few common bind actions:
Set name - Allows you to set your name with a very large increase to your allowed character limit, and also allows you to have spaces in your name.
Name - Only difference between set name and name is that set name has an increased character limit (and you need quotation marks to allow spaces with name as opposed to set name which does not require them).
Say - Lets you bind keys to say things.
Kill - Kills you.
Private Chatting: The private chat key, by default, is "U" however if you have bound over this, you can open the console and bind it (the command is /bind <key> messagemode3). To private chat, you need to aim at someone and press your private chat key. It will look like normal chat, but will only send to the person you have aimed at. Private messages all are written in pink (unless the person typing them uses text color changes, the default is pink) and the name of the person writing the message will be in brackets ( [Name]: Hi! )
Last Killed Chat: This is the most annoying thing ever in my honest opinion. Default key is "I" and what this will do is send a private message to the last person who killed you. I always rebind this with teamchat because it is so easy to accidentally start chatting the wrong person with this key, but, to each his own. If you want to bind it (for some unknown reason) the command is /bind <key> messagemode4
Colored Text: Each number corresponds with a color to get a given color, you need to use the ^ sign followed by the number of the color you want. Number colors are: 01234567
8 is black and 9 is red, but these are less clean, so to speak. In regular text and in your name, they show as proper colors, but they do not show up correctly in the console. For both 0 and 8 which are black, unless you are in an otherwise modded server, you will need two ^'s for it to show in your name, but only one ^ for it to show in regular text. Keep in mind that each ^ and number count toward your character count, which is why /set name becomes extremely helpful for long colorful names.
Examples:
"^3 How are ^5you^2?" would show as "How are you?"
"^^0Awesome" would show as "^Awesome"
You can also add color to the ^'s. "^2^^0Awesome" will show as "^Awesome"
Basic Settings:
So, for new players, allow me to quickly give a short list of commands you should enter to help stabilize your game, and I'll explain them along the way.
/rate 25000 - This can only help. It is the rate at which packets are moved. The default is 4000, which means by increasing it to 25000, you decrease your ping significantly.
/cl_maxpackets 100 - A lot of people like to set lower packets like 15 because it artificially lowers ping, but the reality of it is, that ping lowering doesn't help really. 100 creates a smoother transfer of packets that will make fighting easier.
/cg_fov 97 - The default fov, or Field of View, is 80. It means the camera is bashing into your characters head. With 97, which for some unknown reason 97 is the max you can extend it, you have a wider view of your surroundings which makes life 1000x easier.
/com_maxfps 125 - Assuming you can GET 125 fps, this is the best fps option available. FPS stands for Frames Per Second, this will make the game smoother, make strafing easier, make attacks more effective by registering better, and is just overall so much nicer to play on. You may have to lower your fps count if you have really high ping because you'll otherwise get "Connection Interrupted." Lower ping = More fps you can have.
/cg_drawfps 1 - This will show an fps counter in the top right corner of your screen so you can judge the smoothness of gameplay.
/snaps 100 - Snaps are only really important if you are on a server with an increased sv_fps. Your snaps need to be higher than the sv_fps, otherwise the game wont run as smoothly. Servers run at a variety of sv_fps settings usually ranging between 20 and 80, so setting this to 100 will ensure that snaps will just default to whatever the server framerate is on a given server.
/cg_hudfiles 1 - This is mostly preference. This will give you a much more basic hud with a much better view.
For any command that you do not like changes to and wish to reset defaults: Type the base command and it will tell you what the default setting is. For example, typing /cg_fov without any value will show that the default is 80.
Screenshots: Ever have the urge to take a picture of something? Well, if you go in the console and do /screenshot it will screenshot everything on your screen and place that screen in your base folder under screenshots (unless (!) the server you are on has a server folder. For places like Random EU that save to the "automod" folder, you will find your screenshots in there. Don't want the half of your screen to be the console when you screenshot things? Then /bind <key> screenshot and then press that key in game for it to screen things for you.
Configuration Saving: Don't want to have to do all these commands every time you enter a server? /write <configuration file name> will save a cfg file in your base folder (unless it saves to a server folder, like previously stated, in which case you will need to move it to the base folder in order to execute it) that you can execute by doing /exec <cfg name>
How to Add Custom Things: Soo, you're new to the game and want a cool looking skin or saber hilt or just want to add your own edited configuration file to your game? Well it's easy! If you have a .pk3 or .cfg file you want to add, you'll need to put it in the Base folder. To get there, go to where your JKA is located (Usually, Computer > Local Disk > Program Files > Lucas Arts > Jedi Knight: Jedi Academy > Gamedata > Base) and just put it in there. Its that simple!
Commands NOT To Do: These are things you should NEVER type under any circumstances.
/Delete ANYTHING is always bad. Don't do it. Don't say I didn't warn you.
/Q anything. /Qu /Qui /Qui gon jinn, doesn't matter, all are just short versions of /Quit and will kick you out.
/Disco anything. Disco sabers would be cool, but getting Disco-nected is not.
/r_prims above 3, I believe, is bad. Haven't tried to to be certain, because I'm not a fan of game breaking my stuff, and neither should you be.
/spwin Spins you in circles
/splose Spins you in circles the other direction. Both require restart to fix.
Commonly Unknown Facts:
-In JKA, quotations marks show as invisible. If you want to use quotes, you have to use '
-The console, the in game names that appear when you point the crosshair, the tab key player list, the chat, and the text you type before entering it into the chat all use different fonts. This means that, while alt codes work in almost all of these, they will all show up differently depending on which you look at. I say "almost" all because they wont show up when someone points the crosshair at you and reads your name. So if you name is, say, Xânadûs, don't get upset when people look at you and assume your name is "Xnads" (sorry Xan.
).
-Percent signs (%) also do not work in JKA. If you try to make one, it will show up as a period.
Tips:
-Go to Katas section. Read. Do not kata.
-Read the rest of the database and learn.
/Q uestions? Comments? Concerns? Let me know below!
Opening the Console: On Qwerty keyboards, it is Shift and ~ at the same time. However, if it is not, than it is Shift and whatever key is directly under Esc. You can navigate up and down in the console by using the PageUp and PageDown keys.
How to Bind: Binds are a relatively simple thing. They follow this rule: /bind <key> <action> <applicable value (text, number, etc)>. To explain, let me show a few basic example binds:
/bind 1 say Hiya - This will bind your "1" key so that every time you press it in game, you will say in the chat, "Hiya"
/bind 2 kill - This binds your "2" key to kill you when you press it
/bind 3 sens 4000 - This will bind your "3" key to make your sensitivity 4000
None of these are suggested, they are just examples. Hopefully these make sense. Below are a few common bind actions:
Set name - Allows you to set your name with a very large increase to your allowed character limit, and also allows you to have spaces in your name.
Name - Only difference between set name and name is that set name has an increased character limit (and you need quotation marks to allow spaces with name as opposed to set name which does not require them).
Say - Lets you bind keys to say things.
Kill - Kills you.
Private Chatting: The private chat key, by default, is "U" however if you have bound over this, you can open the console and bind it (the command is /bind <key> messagemode3). To private chat, you need to aim at someone and press your private chat key. It will look like normal chat, but will only send to the person you have aimed at. Private messages all are written in pink (unless the person typing them uses text color changes, the default is pink) and the name of the person writing the message will be in brackets ( [Name]: Hi! )
Last Killed Chat: This is the most annoying thing ever in my honest opinion. Default key is "I" and what this will do is send a private message to the last person who killed you. I always rebind this with teamchat because it is so easy to accidentally start chatting the wrong person with this key, but, to each his own. If you want to bind it (for some unknown reason) the command is /bind <key> messagemode4
Colored Text: Each number corresponds with a color to get a given color, you need to use the ^ sign followed by the number of the color you want. Number colors are: 01234567
8 is black and 9 is red, but these are less clean, so to speak. In regular text and in your name, they show as proper colors, but they do not show up correctly in the console. For both 0 and 8 which are black, unless you are in an otherwise modded server, you will need two ^'s for it to show in your name, but only one ^ for it to show in regular text. Keep in mind that each ^ and number count toward your character count, which is why /set name becomes extremely helpful for long colorful names.
Examples:
"^3 How are ^5you^2?" would show as "How are you?"
"^^0Awesome" would show as "^Awesome"
You can also add color to the ^'s. "^2^^0Awesome" will show as "^Awesome"
Basic Settings:
So, for new players, allow me to quickly give a short list of commands you should enter to help stabilize your game, and I'll explain them along the way.
/rate 25000 - This can only help. It is the rate at which packets are moved. The default is 4000, which means by increasing it to 25000, you decrease your ping significantly.
/cl_maxpackets 100 - A lot of people like to set lower packets like 15 because it artificially lowers ping, but the reality of it is, that ping lowering doesn't help really. 100 creates a smoother transfer of packets that will make fighting easier.
/cg_fov 97 - The default fov, or Field of View, is 80. It means the camera is bashing into your characters head. With 97, which for some unknown reason 97 is the max you can extend it, you have a wider view of your surroundings which makes life 1000x easier.
/com_maxfps 125 - Assuming you can GET 125 fps, this is the best fps option available. FPS stands for Frames Per Second, this will make the game smoother, make strafing easier, make attacks more effective by registering better, and is just overall so much nicer to play on. You may have to lower your fps count if you have really high ping because you'll otherwise get "Connection Interrupted." Lower ping = More fps you can have.
/cg_drawfps 1 - This will show an fps counter in the top right corner of your screen so you can judge the smoothness of gameplay.
/snaps 100 - Snaps are only really important if you are on a server with an increased sv_fps. Your snaps need to be higher than the sv_fps, otherwise the game wont run as smoothly. Servers run at a variety of sv_fps settings usually ranging between 20 and 80, so setting this to 100 will ensure that snaps will just default to whatever the server framerate is on a given server.
/cg_hudfiles 1 - This is mostly preference. This will give you a much more basic hud with a much better view.
For any command that you do not like changes to and wish to reset defaults: Type the base command and it will tell you what the default setting is. For example, typing /cg_fov without any value will show that the default is 80.
Screenshots: Ever have the urge to take a picture of something? Well, if you go in the console and do /screenshot it will screenshot everything on your screen and place that screen in your base folder under screenshots (unless (!) the server you are on has a server folder. For places like Random EU that save to the "automod" folder, you will find your screenshots in there. Don't want the half of your screen to be the console when you screenshot things? Then /bind <key> screenshot and then press that key in game for it to screen things for you.
Configuration Saving: Don't want to have to do all these commands every time you enter a server? /write <configuration file name> will save a cfg file in your base folder (unless it saves to a server folder, like previously stated, in which case you will need to move it to the base folder in order to execute it) that you can execute by doing /exec <cfg name>
How to Add Custom Things: Soo, you're new to the game and want a cool looking skin or saber hilt or just want to add your own edited configuration file to your game? Well it's easy! If you have a .pk3 or .cfg file you want to add, you'll need to put it in the Base folder. To get there, go to where your JKA is located (Usually, Computer > Local Disk > Program Files > Lucas Arts > Jedi Knight: Jedi Academy > Gamedata > Base) and just put it in there. Its that simple!
Commands NOT To Do: These are things you should NEVER type under any circumstances.
/Delete ANYTHING is always bad. Don't do it. Don't say I didn't warn you.
/Q anything. /Qu /Qui /Qui gon jinn, doesn't matter, all are just short versions of /Quit and will kick you out.
/Disco anything. Disco sabers would be cool, but getting Disco-nected is not.
/r_prims above 3, I believe, is bad. Haven't tried to to be certain, because I'm not a fan of game breaking my stuff, and neither should you be.
/spwin Spins you in circles
/splose Spins you in circles the other direction. Both require restart to fix.
Commonly Unknown Facts:
-In JKA, quotations marks show as invisible. If you want to use quotes, you have to use '
-The console, the in game names that appear when you point the crosshair, the tab key player list, the chat, and the text you type before entering it into the chat all use different fonts. This means that, while alt codes work in almost all of these, they will all show up differently depending on which you look at. I say "almost" all because they wont show up when someone points the crosshair at you and reads your name. So if you name is, say, Xânadûs, don't get upset when people look at you and assume your name is "Xnads" (sorry Xan.
).-Percent signs (%) also do not work in JKA. If you try to make one, it will show up as a period.
Tips:
-Go to Katas section. Read. Do not kata.
-Read the rest of the database and learn.
/Q uestions? Comments? Concerns? Let me know below!