Hello,

let’s start with a fundamental question: what are SAMP commands?

SAMP commands are part of the game client, which you can download from sa-mp.com/download.php; every server has them, regardless of game mode or anything else. There aren’t that many of these commands, but they can come in handy!

Now let’s move on to the commands themselves; we’ll start with the most commonly used ones.

Full list:

/q

/save

/rs

/headmove

/fontsize

/pagesize

/timestamp

/fpslimit

/dl

/nametagstatus

/audiomsg

/mem

/interior

First, let’s look at the /q command, also known as /quit 

This command disconnects you from the server almost instantly, without having to press ESC. I’d say there’s nothing more to discuss here, as most of you already use it.

Another command that’s certainly used a lot is /save.

This command saves your position to the file `savepositions.txt`, located in the `GTA San Andreas User FilesSAMP` folder. File path: `C:UsersUserDocumentsGTA San Andreas User FilesSAMP`

Now let’s look at the most important things you’ll find in this file.

AddPlayerClass(123,-9875.1425, 1234.8416, 5555.0123, 179.1320,0,0,0,0,0,0);

The part before the parentheses shows that you’ve saved this as a player.

The first number (123) is your skin ID. The following three numbers (in our case -9875.1425, 1234.8416, 5555.0123) specify the coordinates: X, Y, Z. (This precisely determines the position on the GTA SA map.) The next set of digits (179.1320) determines the player’s rotation (0–360); this is a standard angle. 

The remaining numbers, where we have a zero, are used to store weapon IDs and their ammunition counts. The first 0 is the weapon ID, the second is the number of rounds, and so on. 

The second option is to save the position in a vehicle. We’ll just go through the changes that will take place.

AddStaticVehicle(451,-1686.6906,987.1920,17.2921,89.7897,36,36);

451 is the vehicle ID, not the player’s skin; in our case, it’s the Turisimo. Next come the X, Y and Z coordinates and the rotation. The next two numbers (36,36) are the vehicle’s colours (Colour_1 and Colour_2).

What’s in /save is absolutely brilliant for anyone creating a pawno, because they can simply copy it and the spawn position for the vehicle or player is already set, so they don’t need to adjust anything.

A command similar to ‘save’ is the ‘/RS’ command.

This command saves only the position in coordinate format to the file rawposition.txt. (same folder as savepositions)

e.g.: 2114.6189,1413.6863,10.8203,292.9460 

Here again, we find the X, Y and Z coordinates and the character’s rotation. It does not distinguish between a player and a vehicle.

The next command is /headmove.

As the name suggests, this command disables or enables head rotation relative to the direction you are facing.

Now for the commands to customise the chat. Here we’ll look at the /fontsize and /pagesize commands, and then we’ll also walk you through how to work around the system using commands.

The first command, /fontsize, sets the font size in chat, text draws, dialogue boxes… in short, all text. Valid values are whole numbers ranging from -3 (smallest) to 5 (largest).

The second command – pagesize – sets the number of lines in the chat. The permitted values are 10–20, though this can be easily bypassed.

This ‘workaround’ involves the sa-mp.cfg file, which you’ll find at the same location as savepositions.txt.

I’ll be going into detail about this file in a future article, but here you can set any value for /pagesize and /fontsize. For example, I have pagesize=35. 35 is the number of lines. You’ll find out how to change the chat font in the next article.

Another command for making minor adjustments to the chat is /timestamp.

This command adds a timestamp in the format [HH.MM.SS] (hours, minutes, seconds) before every message in the chat.  What a timestamp actually is would be best left for another article, but I’d rather recommend you ask Uncle Google, as this is also a very interesting topic. I’ll just let you know that it involves counting time from 1 January 1970 at 12:00; since then, +1 has been added to the number every second. At the time of writing this article, the EPOCH TIME was 1515827209.

Another command you’re bound to be familiar with is /fpslimit.

This sets the FPS limit at which the game will run. FPS stands for ‘frames per second’ (the number of times per second that your screen is refreshed). The range for this command is 20–90, though, again, this can be bypassed via our sa-mp.cfg file. However, you must have the frame limiter enabled in the settings.

The last well-known and widely used command is /DL (debug label).

For each vehicle, you’ll see a so-called ‘debug label’, which is information about the vehicle. We won’t go into exactly what each part means, as it’s all written there, but I’ll tell you what you’ll find there.

You’ll find the vehicle ID (1 – max 1999 – SAMP 0.3.7 limit), the vehicle type (i.e. the vehicle ID), e.g. 411 infrenus, followed by the vehicle’s health (HP); however, these HP values are ten times higher than the actual health. By that I mean that if a vehicle has 100 HP, it’s listed as 1000.0; you’ll also find details on the vehicle’s loading status, number of seats, distance from the player, saved position and current position. Just read it carefully and you’ll know everything about the vehicle.

Now for the first, lesser-known command: /nametagstatus.

This command enables or disables the display of an hourglass next to a player’s nickname.

Another command, which is already included in the mod, is /audiomsg.

This command enables or disables the reception of all AudioStreams. (/radioonline, admin music, etc.)

A command that might be interesting, though for the most part completely unnecessary for us, is /mem.

It displays the current SAMP memory usage in the chat.

And finally, the command /interior.

This command displays the ID of the interior you are currently in. However, that’s a topic for a lengthy explanation in its own right. I’ll just briefly mention that every type of interior has its own ID and coordinates. It’s a bit like the Virtual Worlds we have, but perhaps I’ll cover that another time.

I hope you’ve enjoyed my breakdown of the SAMP commands and that you’ll now use them more actively.

Taken from wiki.sa-mp.com and from my own head.

Baseball