Development application update
It has been discussed by some of the developers in the team that the application to the development teams needs a restructure. Thus we've come to the conclusion that we'll re-evalutate as to what needs to be there in the form itself.
Because lets face it. We're not in 2012 anymore, every script is modular these days. The world isn't bound to just default functions present in the SAMP server package. The current generation of SA:MP developers squeeze out the full potential with the help of new functions in new includes. YSI for example. Thus to improve the basic structure of the script we need new generation developers who're aware of these syntaxes and know their way around it, being able to work with it.
To weed out whatever bad apples we might have. Every developer (including me) will have to fill the same application and it'll be reviewed and then further decisions will be made.
For now, the things you need to know about scripting in pawn before you could even think of applying are as follow:
- Fair understanding in pawn (C or Java - these are optional)
- y_inline (optional)
- y_dialogs
- y_hooks
- sscanf
- streamer
- zcmd and/or pawn.CMD
- Dini
- MySQL (optional)
- foreach
- modular approach to scripting
If the candidate who's applying does not know regarding any one of the things mentioned in the list above they need to reconsider their decision of applying.
P.S. Huge reminder, if there is a part where it states to write a code/snippet and the provided code is not properly indented then we will not consider that application. It's an instant denial.
Good luck to any further applicants we may have.
~SARP Development Team.
