21.09.2017, 19:41
@OP: Would you kindly stop naming your threads those with those nonsensical names? Here's a quick "how to" on solving problems.
1. Read the error message. Usually it's clear enough and points you at what you need to fix
2. If the error is confusing, go to your favourite search engine and write something like "site:forum.sa-mp.com My problem". This might give you a few solutions
3. If that doesn't help you, then do the "divide and conquer" method. Comment out 50% of your code, and check if the errors have changed (there will be errors as you are commenting out half your code, duh). If they haven't, comment 50% of what's not commented. Do so until you find which lines cause it
4. If that doesn't help - ask here. Use a meaningful thread name. Do not screencap stuff (unless it's an ingame display issue or something). Paste the errors, and code related to the error line - this means a full command, callback or -20 - 20 lines around the error.
There, please follow that
1. Read the error message. Usually it's clear enough and points you at what you need to fix
2. If the error is confusing, go to your favourite search engine and write something like "site:forum.sa-mp.com My problem". This might give you a few solutions
3. If that doesn't help you, then do the "divide and conquer" method. Comment out 50% of your code, and check if the errors have changed (there will be errors as you are commenting out half your code, duh). If they haven't, comment 50% of what's not commented. Do so until you find which lines cause it
4. If that doesn't help - ask here. Use a meaningful thread name. Do not screencap stuff (unless it's an ingame display issue or something). Paste the errors, and code related to the error line - this means a full command, callback or -20 - 20 lines around the error.
There, please follow that