mixster
2009-10-31 12:10:34
Welcome!
Junior members, your mission, if you choose to accept it, is to develop the include.
Closed
This is the second Junior Member competition! All entrants must be Junior Members as of submitting their entries (if membership is gained after submitting then you are still entitled to win). This competition is run in accordance with RM's approval. Near all content will remain the same, but some small changes may be made over time, but they will be slight and I will announce them, so try to stop by every now and then to check up.
What you will be required to do for this competition is submit 6 to 8 procedures that you think should be added to SRL. They can be rewrites of existing procedures, completely new ones that you think SRL should have in it and they can also be for a completely new file that doesn't exist already.
Rules:
Small note:
One modification is that "own work" will be slightly rephrased for this competition - I will be allowing you to base your work off existing SRL procedures. If you do so, you must state the original procedure and then you will only be marked on your improvement to the procedure.
Likewise, relating to RuneScape means that it should have some use for RuneScape, so no Neopets login procedures or the like.
Small addition:
Now, there will also be one other addition to normal competition - as you have the goal of creating include worthy procedures, all the submissions will also be forwarded on to the Devs so they can see if there's anything they want to add. For every procedure that gets directly added with minimal altering, you will be awarded an additional 25 points. If a procedure is added after quite a bit of modifying, then you will get 10 points.
Judging criteria:
They have been slightly adjusted to make them more suited to this style of competition (see bottom of post for a rundown of what they represent). The values afterwards represent what the maximum amount of points from each can be.
Prize
The prize will be SRL Members, a competition cup, love, respect and reputation. There is also the possibility of the Aristocrats cup if your entry is of a high enough quality (it will still be judged according to normal cup criteria, so I can't make any promises with this and so will be handed out at the staffs discretion).
Submissions
They should be sent to me via PM. Once you have submitted one, I will not accept any others and will only accept entries before the deadline. Likewise, if there are less than 6 procedures, I will not accept it (you will be allowed another entry) and if it has more than 8 procedures I will inform you of this and you will have 24 hours to either re-send one with 8 or less else I will only include your first 8 as your entry. I will not post them publicly until after the competition and neither should you to ensure no stealing of ideas occurs. After the competition, all entries will be posted up.
Why should I enter
This is a small yet flexible competition - you don't have to produce a full script and your submitted procedures can all be short, so it can be a quick and easy entry to make. On the other hand, you can spend ages working and refining a handful of procedures till they're perfect. You can also do something in between. Basically, regardless of your skill or free time, it will be easy to enter, but has enough flexibility that you can truly push yourself. I do encourage everyone who participates to put as much time and effort in as they can though :)
Not only that, but you get real feedback from several skilled scripters (the judges), so it can be a great learning experience. On top of that, you may also get your procedures added to the include!
So the real question is why shouldn't you enter and the answer would be that there is no reason why you shouldn't.
Judging criteria explained
Individuality is still quite straight forward - submitting unique procedures and approaching the same problem in a different way gets points here.
Presentation applies primarily to showing all procedures like they are in the includes with the little header description. It also covers how you name your variables for reading through and how accurately you indent and split up code and the like.
Technique and Creativity covers how you solve the problem. It does have "Adherence to SRL Rules" thrown in too, so making sure there are no possible infinite loops, that it does everything in a logical manner, no possible way to cause a runtime error, checks for invalid input before running and throws an error message where needed and more.
Reliability should be obvious. As a SRL function, reliability is key - it should run properly every time and it shouldn't return the wrong result. If it is a somewhat unreliable procedure because what you are trying to do is pretty hit and miss, then it should at least return the result that would have the least impact on a script (ie usually false) or have a set return value for when it failed (ie -1, '') and it should be stated as such in the procedure description.
Efficiency & Simplicity is another obvious one. It should run quickly and it shouldn't be over complicated purely to impress. This doesn't mean it should be as short or as quick as possible - it should still be a reliable procedure, but you will get more points with a simple, elegant approach rather than one that uses nearly every procedure known to Scar.
Suggested areas
Of course, the whole of the include is at your disposal, but if you're struggling to think of what to do, I've looked through and have a couple of key areas where the include is lacking (I won't list all areas as that's something for you to do).
Last of all, I would like to thank RM on top of the old credits list for making this possible.
May the competition commence!
Junior members, your mission, if you choose to accept it, is to develop the include.
Closed
This is the second Junior Member competition! All entrants must be Junior Members as of submitting their entries (if membership is gained after submitting then you are still entitled to win). This competition is run in accordance with RM's approval. Near all content will remain the same, but some small changes may be made over time, but they will be slight and I will announce them, so try to stop by every now and then to check up.
What you will be required to do for this competition is submit 6 to 8 procedures that you think should be added to SRL. They can be rewrites of existing procedures, completely new ones that you think SRL should have in it and they can also be for a completely new file that doesn't exist already.
Rules:
- Must be your own work
- Must be submitted by the deadline
- Must contain no reflection
- Must relate to RuneScape
Small note:
One modification is that "own work" will be slightly rephrased for this competition - I will be allowing you to base your work off existing SRL procedures. If you do so, you must state the original procedure and then you will only be marked on your improvement to the procedure.
Likewise, relating to RuneScape means that it should have some use for RuneScape, so no Neopets login procedures or the like.
Small addition:
Now, there will also be one other addition to normal competition - as you have the goal of creating include worthy procedures, all the submissions will also be forwarded on to the Devs so they can see if there's anything they want to add. For every procedure that gets directly added with minimal altering, you will be awarded an additional 25 points. If a procedure is added after quite a bit of modifying, then you will get 10 points.
Judging criteria:
- Individuality (75)
- Presentation (75)
- Technique & Creativity (100)
- Reliability (125)
- Efficiency & Simplicity (150)
They have been slightly adjusted to make them more suited to this style of competition (see bottom of post for a rundown of what they represent). The values afterwards represent what the maximum amount of points from each can be.
Prize
The prize will be SRL Members, a competition cup, love, respect and reputation. There is also the possibility of the Aristocrats cup if your entry is of a high enough quality (it will still be judged according to normal cup criteria, so I can't make any promises with this and so will be handed out at the staffs discretion).
Submissions
They should be sent to me via PM. Once you have submitted one, I will not accept any others and will only accept entries before the deadline. Likewise, if there are less than 6 procedures, I will not accept it (you will be allowed another entry) and if it has more than 8 procedures I will inform you of this and you will have 24 hours to either re-send one with 8 or less else I will only include your first 8 as your entry. I will not post them publicly until after the competition and neither should you to ensure no stealing of ideas occurs. After the competition, all entries will be posted up.
Why should I enter
This is a small yet flexible competition - you don't have to produce a full script and your submitted procedures can all be short, so it can be a quick and easy entry to make. On the other hand, you can spend ages working and refining a handful of procedures till they're perfect. You can also do something in between. Basically, regardless of your skill or free time, it will be easy to enter, but has enough flexibility that you can truly push yourself. I do encourage everyone who participates to put as much time and effort in as they can though :)
Not only that, but you get real feedback from several skilled scripters (the judges), so it can be a great learning experience. On top of that, you may also get your procedures added to the include!
So the real question is why shouldn't you enter and the answer would be that there is no reason why you shouldn't.
Judging criteria explained
Individuality is still quite straight forward - submitting unique procedures and approaching the same problem in a different way gets points here.
Presentation applies primarily to showing all procedures like they are in the includes with the little header description. It also covers how you name your variables for reading through and how accurately you indent and split up code and the like.
Technique and Creativity covers how you solve the problem. It does have "Adherence to SRL Rules" thrown in too, so making sure there are no possible infinite loops, that it does everything in a logical manner, no possible way to cause a runtime error, checks for invalid input before running and throws an error message where needed and more.
Reliability should be obvious. As a SRL function, reliability is key - it should run properly every time and it shouldn't return the wrong result. If it is a somewhat unreliable procedure because what you are trying to do is pretty hit and miss, then it should at least return the result that would have the least impact on a script (ie usually false) or have a set return value for when it failed (ie -1, '') and it should be stated as such in the procedure description.
Efficiency & Simplicity is another obvious one. It should run quickly and it shouldn't be over complicated purely to impress. This doesn't mean it should be as short or as quick as possible - it should still be a reliable procedure, but you will get more points with a simple, elegant approach rather than one that uses nearly every procedure known to Scar.
Suggested areas
Of course, the whole of the include is at your disposal, but if you're struggling to think of what to do, I've looked through and have a couple of key areas where the include is lacking (I won't list all areas as that's something for you to do).
- Various skill files, eg Ranging, Cooking, WoodCutting and more. They could all use some basic and extended procedures for various things.
- World map - a some what recent addition and it still doesn't have any part of SRL devoted to it.
Last of all, I would like to thank RM on top of the old credits list for making this possible.
May the competition commence!