Talk:Hibakeresés: Difference between revisions

From Multi Theft Auto: Wiki
Jump to navigation Jump to search
(Created page with 'Isn't isTimer already MTA function? http://wiki.mtasa.com/wiki/IsTimer Also, is this really the way MTA isTimer works? If having a lot of timers, better method would be to remove…')
 
(→‎Can I just say: new section)
Line 3: Line 3:
Also, is this really the way MTA isTimer works? If having a lot of timers, better method would be to remove the table key in the function setTimer references to. And onColShapeLeave just check if the key exists.
Also, is this really the way MTA isTimer works? If having a lot of timers, better method would be to remove the table key in the function setTimer references to. And onColShapeLeave just check if the key exists.
  --Madis
  --Madis
== Can I just say ==
that this article is too complicated. Maybe break it down to several easy to read pages that don't look scary at all to someone starting scripting. Maybe a step by step example of what to do when your code don't do what you expect. So newbies posting, 'Why my script no work?' on irc can be redirected to it with no come back. I'ma thinking like 3 steps with plenty of white space: '1. Copy this bit of code at the start of your function' and then like '2. Change it like this to suit what your function is doing' and like '3. Save and restart the resource and look at the debug window'.

Revision as of 05:26, 26 February 2011

Isn't isTimer already MTA function? http://wiki.mtasa.com/wiki/IsTimer Also, is this really the way MTA isTimer works? If having a lot of timers, better method would be to remove the table key in the function setTimer references to. And onColShapeLeave just check if the key exists.

--Madis

Can I just say

that this article is too complicated. Maybe break it down to several easy to read pages that don't look scary at all to someone starting scripting. Maybe a step by step example of what to do when your code don't do what you expect. So newbies posting, 'Why my script no work?' on irc can be redirected to it with no come back. I'ma thinking like 3 steps with plenty of white space: '1. Copy this bit of code at the start of your function' and then like '2. Change it like this to suit what your function is doing' and like '3. Save and restart the resource and look at the debug window'.