Optimizing Plugins (AMX Mod X Scripting) - Revision history

Kristi at 21:30, 30 August 2017

2017-08-30T21:30:43Z

2013-03-16T19:29:26Z

‎Don't Re-index Arrays

2013-03-16T19:28:21Z

‎Don't Re-index Arrays

2008-11-07T16:11:57Z

2008-11-07T16:11:29Z

added langswitch template

2007-09-10T16:03:58Z

2007-04-13T02:37:48Z

‎Local Strings: Fixed BAILOPAN's nonsense code

2007-01-18T08:59:41Z

Reverted edit of Qqqqqqq, changed back to last version by CyberMind

2007-01-18T01:42:47Z

2007-01-18T01:40:01Z

@@ Line 253: / Line 253: @@
 As of AMX Mod X 1.70, there is an ultra high-speed version of format() called formatex().  It skips copy-back checking, unlike format().  formatex() cannot be used if a source input is the same as the output buffer.  For example, these are invalid:
 <pawn>new buffer[255]
-formatex(buffer, 254, "%s", buffer);
+formatex(buffer, charsmax(buffer), "%s", buffer);
-formatex(buffer, 254, buffer);
+formatex(buffer, charsmax(buffer), buffer);
-formatex(buffer, 254, "%d %s", buffer[2]);</pawn>
+formatex(buffer, charsmax(buffer), "%d %s", buffer[2]);</pawn>
 It should be noted that format() will behave the same as formatex() if it detects that there will be no copy-back needed.  However, formatex() does not check this, and thus is slightly faster for situations where the coder is sure of its usage.

@@ Line 108: / Line 108: @@
+{
     player = players[i]
     team = get_user_team(player)
 }</pawn>
 Not only is this more readable, but look at how much cruft we've shaved off the compiler's generated code:
@@ Line 120: / Line 119: @@
     LOAD players[i]
     STORE player
     CALL get_user_team
     LOAD player

@@ Line 83: / Line 83: @@
 A common practice in Small is to "save space" by re-indexing arrays.  There are a few myths behind this, such as saving memory, assuming the compiler does it for you, or readability.  Fact: none of these are true.  Observe the code below:
 <pawn>new players[32], num, team
-get_players(players, num)
+get_players(players, num, "h")
 for (new i=0; i<num; i++)
+{
     team = get_user_team(players[i])
     set_user_frags(players[i], 0)
@@ Line 94: / Line 92: @@
 <pre>
 :LOOP_BEGIN
     LOAD i
     LOAD players

@@ Line 1: / Line 1: @@
 {{LanguageSwitch}}
 ==Introduction==
 [[Admin-Mod]] and [[AMX Mod X]] became very popular because of their easy to use scripting language.  However, the words "scripting language" come with a lot of loaded preconceptions.  Most people assume that because it's scripted:

← Older revision		Revision as of 16:11, 7 November 2008
Line 1:		Line 1:
		+	{{LanguageSwitch}}
	==Introduction==		==Introduction==
	[[Admin-Mod]] and [[AMX Mod X]] became very popular because of their easy to use scripting language. However, the words "scripting language" come with a lot of loaded preconceptions. Most people assume that because it's scripted:		[[Admin-Mod]] and [[AMX Mod X]] became very popular because of their easy to use scripting language. However, the words "scripting language" come with a lot of loaded preconceptions. Most people assume that because it's scripted:

← Older revision	Revision as of 16:03, 10 September 2007
(No difference)

@@ Line 222: / Line 222: @@
 For example:
-<pawn>set_cvar_string("amx_gaben", get_cvar_string("amx_gaben") + 1)</pawn>
+<pawn>set_cvar_num("amx_gaben", get_cvar_num("amx_gaben") + 1)</pawn>
 This will create two copies of "amx_gaben" in the DATA section.  While this doesn't really hurt, it does increase the size of your plugin.
 Similarly, this has the same problem:
 <pawn>#define AMX_GABEN "amx_gaben"
-set_cvar_string(AMX_GABEN, get_cvar_string(AMX_GABEN) + 1)</pawn>
+set_cvar_num(AMX_GABEN, get_cvar_num(AMX_GABEN) + 1)</pawn>
 The only way to avoid this mess is to use global variables.  As stated earlier, they're basically free storage.
 <pawn>new AMX_GABEN[] = "amx_gaben"
-set_cvar_string(AMX_GABEN, get_cvar_string(AMX_GABEN) + 1)</pawn>
+set_cvar_num(AMX_GABEN, get_cvar_num(AMX_GABEN) + 1)</pawn>
 Again, while not necessary, this will reduce your plugin's size in memory and on disk.  If you're already using defines, you can make this switch easily.
@@ Line 237: / Line 237: @@
 <pawn>new const AMX_GABEN[] = "amx_gaben"
-set_cvar_string(AMX_GABEN, get_cvar_string(AMX_GABEN) + 1)</pawn>
+set_cvar_num(AMX_GABEN, get_cvar_num(AMX_GABEN) + 1)</pawn>
 Now it is a perfectly safe method of storage.

← Older revision		Revision as of 01:42, 18 January 2007
Line 1:		Line 1:
−	~~You can optimize plugins by putting special optimization code in them.~~	+

← Older revision		Revision as of 01:40, 18 January 2007
Line 1:		Line 1:
−	~~LOL HAX~~	+	You can optimize plugins by putting special optimization code in them.
−
−	~~LOL HAX~~
−
−	~~LOL HAX~~