Making a PM System - Revision history

Dutchman101: fix hotlink breaking

2018-09-15T21:20:53Z

fix hotlink breaking

← Older revision		Revision as of 21:20, 15 September 2018
Line 162:		Line 162:

	==Conclusion==		==Conclusion==
	And that is it! You've learn a bit about tables, a bit about arguments, a bit about that third-world variable, and how to create a PM system. For those that would like to see the final code, collapse the code below. PM system is hardly the hardest thing you can create in MTA:SA, it's one of the easiest things. But it may be a milestone for you, so make sure you tell me how you did on this tutorial at [http://forum.mtasa.com/viewtopic.php?t=37395\|the official topic for this tutorial].		And that is it! You've learn a bit about tables, a bit about arguments, a bit about that third-world variable, and how to create a PM system. For those that would like to see the final code, collapse the code below. PM system is hardly the hardest thing you can create in MTA:SA, it's one of the easiest things. But it may be a milestone for you, so make sure you tell me how you did on this tutorial at [http://forum.mtasa.com/viewtopic.php?t=37395 the official topic for this tutorial]

	<section name="server.lua" class="server" show="false">		<section name="server.lua" class="server" show="false">

Qaisjp at 18:35, 10 June 2014

2014-06-10T18:35:38Z

← Older revision		Revision as of 18:35, 10 June 2014
Line 1:		Line 1:
			__NOTOC__
	This is a scripting tutorial teaching you how to create a private messaging system in your server. It was originally created on Thursday November 24th, 2011 at 6:32pm (UTC) by qaisjp for MTA:SA 1.1. The original code was tested on the day of original creation, but it was thoroughly revamped since then.		This is a scripting tutorial teaching you how to create a private messaging system in your server. It was originally created on Thursday November 24th, 2011 at 6:32pm (UTC) by qaisjp for MTA:SA 1.1. The original code was tested on the day of original creation, but it was thoroughly revamped since then.

	~~__NOTOC__~~
	== Creating the basic resource ==		== Creating the basic resource ==
	Creating your resource is one of the important parts of the tutorial. In Multi Theft Auto, resources are described as sets of scripts; there are many different types of resources but I won't go into detail of that because it is outside the scope of my tutorial. I will not teach the details about '''meta.xml''' files, but I will walk you through it. For more detailed information on resources and how to create one, follow the [[Resources]] tutorial.		Creating your resource is one of the important parts of the tutorial. In Multi Theft Auto, resources are described as sets of scripts; there are many different types of resources but I won't go into detail of that because it is outside the scope of my tutorial. I will not teach the details about '''meta.xml''' files, but I will walk you through it. For more detailed information on resources and how to create one, follow the [[Resources]] tutorial.

Qaisjp at 18:35, 10 June 2014

2014-06-10T18:35:29Z

← Older revision		Revision as of 18:35, 10 June 2014
Line 1:		Line 1:
	This is a scripting tutorial teaching you how to create a private messaging system in your server. It was originally created on Thursday November 24th, 2011 at 6:32pm (UTC) by qaisjp for MTA:SA 1.1. The original code was tested on the day of original creation, but it was thoroughly revamped since then.		This is a scripting tutorial teaching you how to create a private messaging system in your server. It was originally created on Thursday November 24th, 2011 at 6:32pm (UTC) by qaisjp for MTA:SA 1.1. The original code was tested on the day of original creation, but it was thoroughly revamped since then.

	~~__TOC__~~		__NOTOC__
	== Creating the basic resource ==		== Creating the basic resource ==
	Creating your resource is one of the important parts of the tutorial. In Multi Theft Auto, resources are described as sets of scripts; there are many different types of resources but I won't go into detail of that because it is outside the scope of my tutorial. I will not teach the details about '''meta.xml''' files, but I will walk you through it. For more detailed information on resources and how to create one, follow the [[Resources]] tutorial.		Creating your resource is one of the important parts of the tutorial. In Multi Theft Auto, resources are described as sets of scripts; there are many different types of resources but I won't go into detail of that because it is outside the scope of my tutorial. I will not teach the details about '''meta.xml''' files, but I will walk you through it. For more detailed information on resources and how to create one, follow the [[Resources]] tutorial.
Line 79:		Line 79:
	If you want to try and test it out on yourself, save this (it should be in server.lua and you should've been editing in that file anyway) and (re)start the resource. Typing the name of someone who isn't on the server should make that error appear, but typing your name (or someone who is on the server) should appear to do nothing... for now.		If you want to try and test it out on yourself, save this (it should be in server.lua and you should've been editing in that file anyway) and (re)start the resource. Typing the name of someone who isn't on the server should make that error appear, but typing your name (or someone who is on the server) should appear to do nothing... for now.

	==~~Tattle tale~~==		==Outputting Messages==
	Now we've sorted out error handling - making sure there is a person to PM to and telling the user he's made a mistake - we can start on the part that tells both users that he/she's sent/received a PM.		Now we've sorted out error handling - making sure there is a person to PM to and telling the user he's made a mistake - we can start on the part that tells both users that he/she's sent/received a PM.
	We will use similar code to the error handling output code, we'll be using hex here too. I won't explain much about hex because it's fairly simple, but Google is your friend for all of eternity (or until the NSA decides to take over the world).		We will use similar code to the error handling output code, we'll be using hex here too. I won't explain much about hex because it's fairly simple, but Google is your friend for all of eternity (or until the NSA decides to take over the world).
Line 103:		Line 103:
	Make sure you read the code, I've explained it in here. Go on, test your message!		Make sure you read the code, I've explained it in here. Go on, test your message!

	== ~~.. there'll be less arguments going on around here, son~~ ==		== Second class citizen ==
	You may have noticed that the PM messages don't go beyond three words. If you're daring you might've tried to extend it to a couple of more words. Don't worry, there's an easy "fix" - and it doesn't involve copying the same variables over and over and over and over and over and over and over and ov.. (I am getting carried away here, aren't I?) .. er again. The wonderful "...", you should already know ".." concatenates (attaches/combines/merges/appends) two variables but "..." is something different. It's a special kind of variable and it cannot be set anywhere except in function arguments, it has to be the last argument and it can only be manipulated when wrapped in a table (in the latest Lua). Tables are rather simple and integral features of Lua but it can be challenging for newcomers. I won't explain this third-world-variable much because you may or may not understand tables correctly themselves.		You may have noticed that the PM messages don't go beyond three words. If you're daring you might've tried to extend it to a couple of more words. Don't worry, there's an easy "fix" - and it doesn't involve copying the same variables over and over and over and over and over and over and over and ov.. (I am getting carried away here, aren't I?) .. er again. The wonderful "...", you should already know ".." concatenates (attaches/combines/merges/appends) two variables but "..." is something different. It's a special kind of variable and it cannot be set anywhere except in function arguments, it has to be the last argument and it can only be manipulated when wrapped in a table (in the latest Lua). Tables are rather simple and integral features of Lua but it can be challenging for newcomers. I won't explain this third-world-variable much because you may or may not understand tables correctly themselves.

Qaisjp: Qais moved page PM System Tutorial to Making a PM System

2014-06-10T18:33:46Z

Qais moved page PM System Tutorial to Making a PM System

← Older revision		Revision as of 18:33, 10 June 2014
(No difference)

Qaisjp: Qais moved page Tutorial:PM System to PM System Tutorial: Final move.

2014-06-08T01:01:29Z

Qais moved page Tutorial:PM System to PM System Tutorial: Final move.

← Older revision		Revision as of 01:01, 8 June 2014
(No difference)

Qaisjp: Qais moved page Tutorials:PM System to Tutorial:PM System: Deary me. Fix title.

2014-06-08T00:59:46Z

Qais moved page Tutorials:PM System to Tutorial:PM System: Deary me. Fix title.

← Older revision		Revision as of 00:59, 8 June 2014
(No difference)

Qaisjp: Qais moved page Tutorials/PM System to Tutorials:PM System

2014-06-08T00:59:17Z

Qais moved page Tutorials/PM System to Tutorials:PM System

← Older revision		Revision as of 00:59, 8 June 2014
(No difference)

Ixjf: /* .. there'll be less arguments going on around here, son */

2013-09-22T09:07:03Z

.. there'll be less arguments going on around here, son

← Older revision		Revision as of 09:07, 22 September 2013
Line 116:		Line 116:
	outputChatBox("[PM < " .. playerName .. "]: #FFFFFF " .. , recipient, 255, 255, 0, true)		outputChatBox("[PM < " .. playerName .. "]: #FFFFFF " .. , recipient, 255, 255, 0, true)
	else		else
	outputChatBox("Sorry, we don't know a person called" .. ~~recipientName~~, ~~recipient~~, 255, 0, 0)		outputChatBox("Sorry, we don't know a person called" .. target, player, 255, 0, 0)
	end		end
	end		end
Line 133:		Line 133:
	outputChatBox("[PM < " .. playerName .. "]: #FFFFFF " .. , recipient, 255, 255, 0, true)		outputChatBox("[PM < " .. playerName .. "]: #FFFFFF " .. , recipient, 255, 255, 0, true)
	else		else
	outputChatBox("Sorry, we don't know a person called" .. ~~recipientName~~, ~~recipient~~, 255, 0, 0)		outputChatBox("Sorry, we don't know a person called" .. target, player, 255, 0, 0)
	end		end
	end		end
Line 157:		Line 157:
	outputChatBox("[PM < " .. playerName .. "]: #FFFFFF " .. message, recipient, 255, 255, 0, true)		outputChatBox("[PM < " .. playerName .. "]: #FFFFFF " .. message, recipient, 255, 255, 0, true)
	else		else
	outputChatBox("Sorry, we don't know a person called" .. ~~recipientName~~, ~~recipient~~, 255, 0, 0)		outputChatBox("Sorry, we don't know a person called" .. target, player, 255, 0, 0)
	end		end
	end		end

Ixjf: /* Tattle tale */

2013-09-07T11:24:03Z

Tattle tale

← Older revision		Revision as of 11:24, 7 September 2013
Line 96:		Line 96:
	outputChatBox("[PM < " .. playerName .. "]: #FFFFFF " .. word1 .. " " .. word2 .. " " .. word3, recipient, 255, 255, 0, true)		outputChatBox("[PM < " .. playerName .. "]: #FFFFFF " .. word1 .. " " .. word2 .. " " .. word3, recipient, 255, 255, 0, true)
	else		else
	outputChatBox("Sorry, we don't know a person called" .. ~~recipientName~~, ~~recipient~~, 255, 0, 0)		outputChatBox("Sorry, we don't know a person called" .. target, player, 255, 0, 0)
	end		end
	end		end

Ixjf: /* Hitting your target */

2013-09-07T11:12:13Z

Hitting your target

← Older revision		Revision as of 11:12, 7 September 2013
Line 54:		Line 54:
	Slow down! Here we set a variable to what "getPlayerFromName" returned. It's like assigning a door a name, the door can contain a player or it can contain nothing - but you can always remember what door it is by the name it is assigned to (the name which is written on the door). This means that ''recipient'' will be the value of whatever getPlayerFromName returns.		Slow down! Here we set a variable to what "getPlayerFromName" returned. It's like assigning a door a name, the door can contain a player or it can contain nothing - but you can always remember what door it is by the name it is assigned to (the name which is written on the door). This means that ''recipient'' will be the value of whatever getPlayerFromName returns.

	We have to check if it returns nil or a player element, since nil is virtually nothing and all it ~~can~~ return is a player element we ~~only really need to check if it returns something~~. Time to carry on my code.		We have to check if it returns nil or a player element, since nil is virtually nothing and all it should return is a player element, so we can send him the message. Time to carry on my code.

	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
Line 72:		Line 72:
	else -- but what if recipient doesn't exist? then...		else -- but what if recipient doesn't exist? then...
	-- This tells "recipient" that he's made a mistake, in red.		-- This tells "recipient" that he's made a mistake, in red.
	outputChatBox("Sorry, we don't know a person called" .. ~~recipientName~~, ~~recipient~~, 255, 0, 0)		outputChatBox("Sorry, we don't know a person called " .. target, player, 255, 0, 0)
	end -- there's no more possibilities, so close off this scope of questioning.		end -- there's no more possibilities, so close off this scope of questioning.
	end		end