SRL Archive - Archive

Hey all!

After approx. 7 hours of going thought the 8 applicant scripts, I have finally finished and reached my decision on who has won the first official SRL scripting competition.

In the following posts, I will be posting my comments on each persons script; what I liked about them all and what I think could have been improved. The scripts on which i comment on will be attached as i believe a lot of people can learn off of all of the scripts. However, if you want your script removed, please tell me and i will do so.


Table of Contents:

• 1. Introduction Page
• 2. What I have marked you all on

The Scripts

• 3.1. Dan Cardin
• 3.2. N3ss3s
• 3.3. Nielsie95
• 3.4. Psychor
• 3.5. Rikjess
• 3.6. SKy Scripter
• 3.7. Tarajunky
• 3.8. YoHoJo

The Winner and a Final Note

• 4. The Winner!
• 5. Final Message

Well this is the first SRL scripting competition, and i think it turned out really well. I am hoping to turn this into a regular thing with lots of people getting involved, both in scripting and marking.

If you hadn't guessed by now, the point of this competition was to try to motivate lots of people to make a script: a similar script so that at the end you can compare your script to everyone elses, and see what they have done in place of what you have done. This way, we can all see which of the scripting techniques work best in different scenarios.

I hope to get more people involved in the future. The more people who are scripting, the better this competition becomes, and the more experience you can get. I also hope that other people will help me mark the scripts, because currently it is only my views which are taken into account, and so the winner is based on my views of scripting only. The more people marking, the better the results will actually be.

And so as a Disclaimer:

What I say about your scripts are solely my own opinions. All criticism is only meant to be constructive and help you improve your scripts. I'm sorry if any criticism comes out negative, it is not meant like that. Feel free to take none of my advice, I'm not exactly the best SCAR scripter around. I concentrate mainly on criticism, so most of my post will feel negative. I would like to take the opportunity to say now that all of the scripts are of a great quality, and i congratulate you all in making these in such a short time period. Well done.

I would also like to take the opportunity to thank Sumilion for helping me mark the scripts. I really appreciate it :)

So on we go! I hope everyone can learn something from the following scripts. I was very impressed with many of them.

Thanks a lot

Starblaster100

All of the scripts have been marked using the same extensive criteria. I tried to keep it as fair as possible whilst marking the scripts. Below, I will quickly summarize what I was marking you all on, and what I expected from each


1. Technique (/100)

This relates to what type of loops you have used where, how you found that certain object on the floor, how you detected that door, how you made sure your script was fail safe. It also refers to issues such as whether you should have used DTMs / DDTMs / bitmaps there or not, how you have withdrawn that item from the bank, and if you could have done this any better

2. Individuality (/100)

This refers to whether your scripting style is your own or not. The more individual your script is, the better it is for you, because this means you really understand what all of the different procedures / functions / types / methods should be used for. it means you are relying less on other people, and are developing your own style.

3. Use of SRL (/100)

This relates to how well you have used the SRL include. Are you creating custom functions that are already in SRL, or are you using the existing ones in the include. Also, are you using them correctly? There is no point in creating something which is a;ready in the include. Basically this shows how well you have looked through the include before resorting to making it yourself, and it shows your understanding of the include as well.

4. Efficiency (/100)

This is the thing I am most strict about. The more efficient the script is, the better it is. Why constantly write out procedures when you can use a simple repeat instead? Are you using "end else" when needed? Do you have duplicate functions? Are you freeing DTMs / bitmaps after finishing with them? The more efficient your script is, the better it will run, and the easier errors will be to fix when the arise.

5. Presentation (/100)

Presentation of a script is always important! And this should be easy marks. There are only 4 categories. Do you have a respectable title page? A decent progress report? Good scripting standards? Commented procedures and functions? (which is the one everyone always forgets!)

6. Added Extras (/100)

What extra features did you include in your script? The more that are in there, the better it is. Be careful though, because including extra features which don't work / aren't efficient could get you marked down in other categories!

7. Script Run (/100)

How did the script run when we tested it? Did it do what it was asked for? Any problems? As simple as that.

1. Technique (65/100)

Well opening the script up, we can see straight away you have used a lot of DTMs. Nothing wrong with that, but you could have used less, and a smelter is a great place on where you can use Dynamic DTMs (DDTMs) All ore types look the same, and so all you would ahve to do is change the mainpoint color in the Dynamic DTM and you could use 1 for 9 different ores.

You have also used DTMs to find the location of the character. Although this is a good use for DTMs, they are very unreliable on finding locations, if they are solely used like you have done. To make area finding more efficient, i would narrow down the search area of the DTM (i.e not always MMX1, MMY1, MMX2, MMY2) and use symbols as well. Again, you have used Bitmaps and DTMs for walls and stairs on their own, which is not always accurate, especially if the the map rotated slightly. You you do insist on using DTMs and Bitmaps for these, i highly suggest looking at some of the bitmap and DTM rotated procedures.

I love the idea of the GetOre Procedure, of how you have used your type. Excellent IMO, however, some parts of the procedure are incorrect. I'll explain more later on…

In general, you rely heavily on solely bitmaps or DTMs. By combining them with symbols, colors, and static objects, it could be improved greatly, since DTMs and bitmaps are not always accurate on their own.

2. Individuality (50/100)

This script looks a lot like all of the other scripts around. It seems only basic techniques have been used, and where advanced techniques have been tried, some have been used incorrectly and not to their maximum potential. However, i do like how you have used your type.

3. Use of SRL (35/100)

Only a few SRL procedures have been used, mostly to do with Banking, changing angles and finding symbols. In SRL itself, there are already Bitmaps of all Ores and Bars which will be loaded with a simple SetupSRLSmithing as well as funrance finding procedures. You may want a quick gland over at those to see if you can impliment those into your script.

NextPlayer Procedure has unfortunately been used incorrectly, and because of a silly mistake like this, it will cost you a few marks. On line 360 (for example) you have the following:

[php]
if not LoggedIn then
begin
NextPlayer(true);
end else
…
[/php]

This is wrong. If the player is not logged in, then Nextplayer should be false, else it should be true. To solve this problem. The best way to use nextplayer, is at the top of every main procedure put If not(loggedin) then Exit; and then in your main loop put NextPlayer(Loggedin). That way, if you are not logged in, the script won't try carrying on with the rest of the players, and his state will eventually be set correctly.

4. Efficiency (35/100)

I'm glad to see lots of "end else" in your script, which increases efficiency of the script. However, Procedures such as Login and Compass aren't really needed, and an be shrunk down quite a bit.

FindLocation needs "else" in it and procedures such as WalkToBankFromDead need waits in them otherwise SCAR will start to freeze up when it is searching for DTMs and not finding them.

In WalkToFallySmelter you are constantly loading a DTM without freeing it. Thats a big NO NO! After a while of use, SCAR's memory will completely fill up and you will get a DIB error.

In your DoRandoms, you have forgotten the Wait(1) which defeats the purpose of the "For to do case of" method we use.

[php]
procedure AntiRandoms;
begin
DoRandoms;
FindNormalRandoms;
end;
[/php]

There is no point in calling a set of randoms and then calling the again with extras added.

5. Presentation (55/100)

Scripting standards are pretty much perfect. A nice generated title would have been nice, along with comments on what each procedure does. Progress report is slightly disappointing

6. Added Extras (50/100)

Smelting in Lumbridge if you can't find the place was a very nice addon to the script. However, with the area detection being a little dodgy i'm not sure how well it would work, and if it would constantly try smelting in Lumbridge.

7. Script Run (25/100)

Had all sorts of problems with it … thought i was in Al-Kharid aswell, DTMs arent very trustworthy for stuff like this. After i forced Loq := 'Fally' it couldnt withdraw my ores properly. This was mainly to do with DTMs, and using the Step DTMs for walking.

1. Technique (20/100)

Very unorthodox technique of using readlns to setup Usernames, Passwords and Nicks, and a bit annoying if you are constantly starting and stopping the script. It also limits the script greatly to only 3 players, and since you already have some setup in the script (bar type, pin etc) it would have made much more sense to put username and password setup there.

CompassMMouse is an interesting procedure, but with such small wait times, and keys being released at the same time, it makes the script very detectable.

No usage of Bitmaps / DTMs at all? instead you have forced us to have bars in specific bank slots, via the procedure BarSlot. Also, you seem to only be changing the X Coord, so why use a TPoint? You could make withdraing bars somthing as simple as Mouse(GetXCoordForBar, 400, 2, 2, False);

You seem to have not used Multiplayers at all in your main loop. There are no repeats?

All other techniques look like what everyone else will use. And hey, if it ain't broke, why fix it?

2. Individuality (40/100)

A script similar to everyone else around, with very few ( / no?) high level functions used. You have used your own method of setting up players, i'll give you that, but it can be frustrating if you have to do it everytime you run the script.

3. Use of SRL (15/100)

Very few used, only for Banking, Antiban and Antirandoms.

You include Smithing.scar but don't use it.

Multiplayers have not been utilized at all

4. Efficiency (75/100)

Glad to see "end else" have been used where needed.

Script is concise, and only needed functions are used, however, if they fail, there is little backup to support it, and the script will ge lost very easily. Lack of procedures however has limited the script greatly.

Static coord clicking seems to be used a lot which is discouraged.

Correct techniques have been used where needed for maximum efficiency.

5. Presentation (40/100)

Scripting standards are excellent, with minor flaws. However, it is lacking a decent title and procedure descriptions. no Progress Report???

6. Added Extras (0/100)

No added extras seen.

7. Script Run (30/100)

The Readlns were very annoying to use. Plus the fact that I didn't actually have 4 players, so that caused errors. After that, the script had quite a few problems, getting to the bank and smelting.

1. Technique (90/100)

Some very advanced techniques being used here; I particually like TDTMFromStr to create a very efficient Ore and bar DTM procedure. FindRandoms has also been designed very well. Excellent use of different loops.

Is fast tab changing really necessary?

2. Individuality (90/100)

I have never seen a script like this before. Excellent procedures have been used for each little activity neccessary for the script to work well. Your own scripting sytle has developed and it is completely unique, which is what SRL needs. Very advanced techniques used.

3. Use of SRL (90/100)

Excellent knowledge of SRL, with banking, walking, antirandoms, antiban, maths, autocolorings, and inventory procedures all used correctly. SRL used to a great potential.

Some procedures have been made especially for this script though, and maybe you could have used some SRL procedures instead.

4. Efficiency (85/100)

In LoadDtm, where colors are not changing, you should have a static DTM, and not a DDTM.

FastGetLvl is not really needed, GetSkillLevel already switches to the correct gametab.

Excellent use if Changing color comparing speed where necessary

ClickWorldSwitchButton and SelectWorld could be slightly better

Is fast Tab changing really needed? It will take a few seconds more to do it the old way. Why create even more functions when we already have good working ones?

5. Presentation (90/100)

Title, descriptions of each function and perfect presentation on the progress report.

Scripting standards are a little off in a few places, very minor.

6. Added Extras (95/100)

Such a vast number of added extras, which truely makes the script so much better.

Walking to random banks

World switching

Last chance

Custom antiban procedures

Door Opening

Setup Checking

7. Script Run (85/100)

An excellent script run. Could have done with a bit more antiban (mouse movements etc) but thats minor.

Second Chance didn't work properly the second time i ran it however.

1. Technique (45/100)

In some places, loops are not really used properly, which is a bit disappointing. Techniques used are what i would expect most people to use. However, they do work. Lots of coord clicking is slightly disappointing; a bit more randomness is needed.

Efficiency is very low which brings the script down a lot.

In SetUpScript, none of the waits are really needed

2. Individuality (50/100)

A scripting style similar to most other peoples. Little advanced techniques used in custom procedures.

3. Use of SRL (70/100)

Good use of SRL's procedures.

"Turn" is not really needed, and pressing and lifting the arrow keys so fast and so often will get our characters flagged. I would recommend using SRLs one, or creating a slightly better one.

Antiban is good as are the antirandoms use. (Copied directly from SRL? why not just use FindNormalRandoms?)

No use of Smithing.scar - It has a good range of pre loaded bitmaps for ores etc which you could have used.

4. Efficiency (40/100)

Are so many variables needed?

case statement used with only 1 entry: not recommended.

CheckInventory, BankOpen and OpenBankGlassPin could be much more efficient. Is CheckInventory really needed?

WithDrawOre needs rescripting. It can be cut down hugely, increasing the efficiency of the script ten fold.

Static coord clicking with little randomness.

Loading and freeing DTMs which you constantly use is not recommended. Load the once and keep the loaded.

ToFurnaceFromEast and ToFurnaceFromWest can be merged.

MeltOre has static coord clicking with no randomness. This will get us flagged pretty quickly. The procedure can also be improved a lot and made more efficient.

In general most of the functions/ procedures can be made much more efficient, most probably cutting the script down by 2/3. This will increase efficiency and runtime, and it will be much easier to fix errors when they occur.

not so sure about the FSymbol function, it could be scripted much better. (I.E Mouse and Flag need to be wrapped in a begin and end!)

5. Presentation (85/100)

Very nice progress report, and good title. No comments on procedures and functions though.

Scripting standards are excellent, only a few minor errors.

6. Added Extras (70/100)

Sound playing option is a nice idea.

Good use of both banks.

Nice idea to check if you can actually smelt the ore or not, depending on your level

7. Script Run (10/100)

Didn't run at all I'm afraid. It failed to find my ores, and after that… barely anything.

1. Technique (60/100)

procedure FindRandoms; - You are calling FindFastRandoms and the FIndNormalRandoms. FastRandoms are all in NormalRandoms, so this procedure is unneeded: Unfortunately, this is bad scripting.

Extensive antiban use, which is great, but lots of little flaws in there: If you turn the compass, will the script still work in the direction it is facing? If you are not at the furnace and it starts to try and find it, won't this look a bit suspicious?

Might the script try talking to itself in the Chat procedure? you do not look for the name of the person who is chatting to you.

WithOre procedure can be cut down and made much more efficient. maybe try learning "types" next, and combining it with "arrays". SCAR is also very fussy, so you might want to try turning everything into lowercase before doing a case blah of. "bronze" is different to "Bronze"

Good use of symbols to detect which bank you are in. you may want to create a function to lower the accuracy a few times however, just incase someone is standing on one of the symbols.

Clicked:= 0; should be at the top somewhere, not somewher randomly in the middle of your main loop

Good use of DDTMs. you have a good understanding of what they are used for.

2. Individuality (65/100)

An individual script no doubt, with lots of failsafes which many people do not take the trouble to put in. However, basic custom functions were used throughout the script. Where slightly advanced ones where used, they were used in a decent manner.

3. Use of SRL (55/100)

function FindFastRandoms: Boolean; //By WT-Fakawi. - I did say you had to create all of your own functions!

Excellent use of Smithing.scar. maybe also look at the find furnace functions in there

Good use of backup mouse clicks incase RRW doesn't work. However, you are using Mouse clicks! Static coords are not advised in walking.

Nice use of SRL to get all levels, lots of extensive antiban, and good antirandoms.

Good use of lots of failsafes.

4. Efficiency (40/100)

procedure FindRandoms; - You are calling FindFastRandoms and the FIndNormalRandoms. FastRandoms are all in NormalRandoms, so this procedure is unneeded: Unfortunately, this is bad scripting.

Not so many Global vars are needed, many can be localised inside of procedures. E.g Procedure Chat; and the variable click / clicked.

In chat, after chatting to someone, you should exit out of the procedure. There is no point in trying to look for more chat to answer to if you just answered someone.

procedure Smelt; very poorly designed. Firstly, you shouldn't use bitmaps to look for objects on the gamescreen, as they can be very fussy. Secondly, you will only be able to break out of the loop when Found = True, and if it finds it the first time, found will not = true, and so it will carry onto trying to find it the second time. basically this means that the script will always use findobj to look for the furnace, in your procedure.

Everytime the procedure smelt is done, you load SRLSmithing bitmaps and then free them! This is very bad and will cause SCAR's memory to come to the max, and you will get DIB errors. Load them once in your main loop and then forget about it, just like SetupSRL;

Waiting for the bars to complete smelting can be improved. Lots of long, unneccessary waits, and you need an exit; in the "if click then" part

Lots of long unneccessary waits. You should use loops to detect when something you want to happen has happened, and then act on that. That will increase the speed of your script, and make it much more fail proof.

CurrentPlayer := Currentplayer; ?!?!?

5. Presentation (30/100)

Scripting standards are very off, I'm afraid.

No comments on procedures / functions.

A title, and welcoming text, but not very presentational.

A more extensive progress report would have been nice. also needs a bit of updating, We now have functions such as StrToBool whoch you should use. This will increase efficiency

6. Added Extras (60/100)

Use of both banks: Excellent.

Custom chat reposnder

7. Script Run (90/100)

Excellent script run! Worked perfectly well, however there were some long unneccessary waits. Banking was also a bit "botty", how you were just extending the square you were searching it. Very nice antiban as well!

1. Technique (75/100)

[php]
if (not(LoggedIn)) then
begin
LoginPlayer;
Exit;
end;
[/php]

Sound not put that in the antirandoms. The script could try to start from anywhere, which will make all of your chars lost!

MouseCenterFlag is another great idea. However, if 1 color is found very far off, then this could affect the mid point greatly. Also, what happens, if the wrong color is picked?

GetFallyRoadColor is a good idea. Nice backup as well.

Good withdraw Ore Procedure, combined with Smithing.scar

Good use of forward technique, but how you have used it might be suseptable to infinite loops. You must be careful about that.

FindBankers needs some improvement. Just blindly goes for all Yellow locations

2. Individuality (80/100)

Like AMin and AMostColor and how you have used them. Good ideas.

Very individual Script. A unique scripting style, and with a few improvments can be very effective.

Good use of custom functions. Advanced techniques have been used very well, when used.

3. Use of SRL (50/100)

Good use of Smithing.scar

if (not(LoggedIn)) then LoginPlayer; in the main loop!? That completely goes against the use of SRL.

Need to break out of potential infinite loops!

[php]
if (not(LoggedIn)) then
NextPlayer(Players[CurrentPlayer].Active);
[/php]

should be

[php]
if (not(LoggedIn)) then
NextPlayer(False);
[/php]

You can't always guarantee that Players[CurrentPlayer].Active is going to be false, so better be safe than sorry

4. Efficiency (65/100)

Are so many color converting functions really neccessary?

GetFallySmeltSymbol and GetFallyBankSymbol can really just be replaced with a find symbol, with a function to lower accuracy to a certain amount.

A very good use of Labels.

[php]
if (not(BankScreen)) or (not(LoggedIn)) then Exit;
repeat
if (not(LoggedIn)) then Exit;
[/php]

Second Not Loggedin then Exit not really needed. You only need to check once.

CountItemBmpTol is very laggy; not recommended.

5. Presentation (25/100)

I like the small break between each function. Simple, but effective

Scripting standards are very poor

Progress report is highly disappointing.

No procedure comments, or title.

6. Added Extras (60/100)

CompassWalk is a great idea.

Good use of both Banks.

7. Script Run (80/100)

Runs stable, could have some problems getting in the furnace sometimes but it usually gets there in the end.

1. Technique (65/100)

[php]
FTWait(1);
FFlag(0);
FTWait(1);
[/php]

Are all of these really needed everywhere to make sure the flag is gone?

DTM's the best way to find the furnace?

Even though I dont think the unique symbol colors are needed, i still like how you have done this. A very clever method.

Script can be condensed a lot, you are repeating yourself a lot.

2. Individuality (90/100)

A very individual script, based mainly on custom procedures. Quite a bit of it could be made more efficient, as there seems to be a lot of unneeded things in there. Good use of advanced techniques; maybe a bit too much???

3. Use of SRL (70/100)

Many many failsafes, which is very good.

Excellent use of the main SRL include.

No use of smithing.scar?

Good use of multiplayers, breaking out of loops etc.

4. Efficiency (50/100)

FindFurnace needs a couple of waits in there to avoid lag

WithdrawOres could use some serious optimizing.

Looking over most of the script, quite a bit of it could be made more efficient so it runs more smoothly.

Quite a few DTMs have been used, which can slow down the script a lot. I'm not sure if how you have used them are the best way to find the furnace, the ladder etc. I would probably have tried a different technique, probably FindColorsSpiralTol

5. Presentation (65/100)

Scripting standards are slightly off.

Good title

Very nice progress report.

No Procedure / function comments.

6. Added Extras (90/100)

Love the symbol finder. A very clever method, however is it really needed? Symbols dont really change that much, and aren't that big of a problem.

Location detection is a good idea.

Like the idea of auto detecting the level and setting what to smelt from that.

Excellent use of both banks.

7. Script Run (40/100)

West Bank: It was very slow and didnt reach the furnace that well. It first walked past it, then entered it, then walked out, then entered it again.

East Bank: This one was the most problematic. It got to the furnace fairly well, still very slow and the clicks were too far if you ask me. When it tried to walk back it walked in the park, further and further …

1. Technique (55/100)

Were dynamic DTMs really needed? I reckon you could have used static ones.

Function BankOpened:Boolean; really needed?! "function BankScreen: Boolean;" should sufice!

[php]
Players[currentplayer].Banked:=Players[currentplayer].Banked+1;
FreeBitmap(BankBit[1]) FreeBitmap(BankBit[2]) FreeBitmap(BankBit[3])
[/php]

You dont want to do this until yopu are certain the bank is open, otherwise you will get errors. Needs slight rescripting.

Using a bitmap to find the furnace is a bit dodgy in my opinion. Bitmaps are very specific, and the furnace will always look different to when you took the pic.

Always TypeSend('33');? Dont you thionk thats a bit detectable? How about TypeSend(IntToStr(28 + Random(100));

So many global vars? This slows down the script greatly! Make more of them local vars, and use more functions to get around this problem.

2. Individuality (55/100)

An individual script, no doubt, but similar to many others.

Some nice custom procedures used. However, when you have used advanced techniques, they are slightly unstable / unneeded.

3. Use of SRL (20/100)

Very limited use of SRL IMO.

No use of smithing.scar?

Multiplayer usage is not quite used properly.

4. Efficiency (35/100)

You don't need the procedure LoadShit or LoadOreDTM. Load all DTM's once, and keep them loaded. unfortunately, SCAR isn't as efficient as we would like it to be in freeing everything, and so if you are constantly using the DTMs you should keep them loaded.

You are loading DTMs in procedures without freeing them! BAD!

EnterFurnaceRoom needs some waits otherwise you'll get lag. Also needs the use of "end else"

WaitWhileSmelt, not freeing the bitmaps / DTMs!

You are declaring NickNameBMP twice in the main loop. LoginPlayer already does this for you.

5. Presentation (30/100)

Scripting Standards are a bit off

No title

No procedure / function comments

A very disappointing progress report.

6. Added Extras (60/100)

Good use of both banks.

Use of an auto talker. Not many people use these anymore. however, most people think these are a bit dodgy as you are opening yourself up to a fire of questions. Auto responders are preferred now.

7. Script Run (50/100)

A few problems, and quite "botty" looking. Did just about manage to complete one run, but mucked up a bit after that.

Congratulations to Nielsie95 for winning the first scripting competition! His script truly amazed me, and is definitely worth checking out. Nielsie95, contact me to claim you prize of 2 Million RS2 GP

In order of First to Last, the scripting competition results are as follows:

• 1. Nielsie95
• 2. Tarajunky
• 3. SKy Scripter
• 4. Rikjess
• 5. Psychor
• 6. Dan Cardin
• 7. YoHoJo
• 8. N3ss3s

Congratulations to everyone who entered. I was a very harsh marker whilst marking these scripts, and I hope you don't take offense to anything I said. "Practice makes perfect." Maybe you can try fixing your scripts up now, and seeing if you can get them any better in the 7 categories I marked you in :)

Anyone who got over 350 points is well on their way to becoming a great scripter. Anyone who got under, just needs to put in a little extra effort to pull themselves up.

And that about wraps up the first SRL scripting competition! Make sure that if you didn't enter this time, you do so next time, and if you didn't win this time, you script to win next time ;)

If you want to learn how to script, this truly is a great way to learn. Help is at hand to anyone who asks politely, and is willing to help themselves!





C ya around

Starblaster100

First post. Gratz winner and I will be using these scripts!

Try learning from them instead of using them ;)
That was the main point in posting them all up

I'll Also be using these and proggys will be Pmed to the scripter who wrote them, if they want to make them better :D

~Stupedspam

Edit: I will be learning from them Star :D One might spark and idea

Im sure many people will learn from them but I'm sure scripters do not write scripts simply to stare at the code. They want them to be used. I will use them and provide progress reports as always. Feedback on a script is important to make it perfect. Also we have not had a working fally bar smelter for quite some time that I have seen so it will come in great use.

uhh..i should be ahead of yohojo?? he got 305 and i got 315…otherwise :( sadness that i didnt do better(though its my fault) and congrats to nielsie

Yea, im hoping to learn from these scripts, and i'll try to enter the next SRL scripting competition if im not too busy.. :)

so!! whens the new competition…and when am i going to be named 6th place:p

Congrats to Nielsie95.

I have updated my script since submitting it, so people should check out the updated one.

When is the next competition :sasmokin:

A big congrats to all those that entered and those that won, but I believe the community here is really the winners for this contest.

• 1. Nielsie95
• 2. Tarajunky
• 3. SKy Scripter
• 4. Rikjess
• 5. Psychor
• 6. YoHoJo
• 7. Dan Cardin
• 8. N3ss3s

Starr, You did an excellent job on your critiquing, this was a very good read ! It's very informative, to be able to look over EVERYONE's script, and see how different people come up with different solutions to the same task. I know this has been helpful to me, as I'm sure it will be to many other people.I'm looking forward to the next one as well, Maybe I'll even make a submission ;)

Thanks Again for all your hard work and time in this contest, as well as everyone that entered,

~RAM

nielsie95, is inhuman. How the fuck did you do all that shit in 1 flippin` weak, </3</3</3</3

Jealousy >:{

(:p ), I'm going to study your script, after studying for school.

Yea, i've already learned a lot just by looking through nelsie's. (His is the only one i've looked through so far). But, i do have one question.. How does that TDTMFromStr function work?? I looked through it, but it confused me..

Lovely!

I really hope I have enough time to compete next time.

Going to aim for 100% originality, (and mabey some others too, lol)

Great critiques, I'm jealous of them!

Congrats Nielsie! (what'd I tell ya?)

Good Job @ All entrees!

*walks off carrying a pile of scripts to study*

nielsie, your script is amazing!
congrats to everyone who entered, especially to the non-srl members who really did themselves proud
i am looking to enter the next comp so whenever you are ready star ……..
oh and thanks for all your efforts in marking the scripts star, they were done really well

Thx, remember star, I made it in 2 hours, and it aint finished :)

EDIT: When is the next competition?
because on the next one I dont have any trips to summer cottage…
EDIT EDIT: What type of a script will the next competition need? :P

Congratz on every one who enterd the scripting Competition, the scripts look realy nice. :D
@nieslie, gratz. i still dont understand everything of your script. :p
Nice job sb100 with reading all those scripts.
Wow,, iam 4th. :eek:
I hope iam not on hollyday when the next competion is…

I am very sorry for my small mistake Dan Cardin, I have now corrected it. Please bare in mind that I was up until about 2 last night typing all of this up so i was slightly tired :redface:

I have a good idea for the next scripting competition, it will probably start next week sometime. Give me a chance to rest!

Congrats to everyone again, I really enjoyed looking through all of the scripts.

nielsie has just inspired me… thank you nielsie.

Thanks for all the great comments, I'm proud of myself :).
I think all the people who joined did a great job :)

I don't think I can join with the next competition, because I'm on holidays then.

Congrats Nielsie,
Srry Dan, but you GetOre procedure is still very similar to the one I gave you.
http://www.villavu.com/forum/showthread.php?t=12011 post #18
You should not get credited for type, and YoHoJo should be in 6th place.
This is just my opinion, and I don't want to ruin the competition for any of you.

congz to neilson.

it may be similar but i am almost positive i didnt look at urs when writing it. and i dont see that i could do much different if i wanted to keep it as short as it was.

Good Job to all Entries!

Congrats Winner!

Hopefully i will learn by viewing these scripts…

Congrats everyone who entered, you did a great job. Also congrats to Nielsie for winning.

Star you need to make a global PM next time you have one of these cause I didn't even know it was going on.

Ya congrats to everyone that joined. I am planning on joining the next one :D. Maybe I'll beat Nielsie:p He isnt even entering I dont think so I might have a chance :)

Grr i did really bad this sucks =(
I did make this in like 4 days though but yea didnt expect that.
Oh well ill start earlier and try harder next time !=(!

From: YoHoJo
Oh well ill start earlier and try harder next time !=(!

That's the spirit! :)

nice one nielsie but star you posted member scripts here so leechers can use them to

Hopefully they will learn something as well, that was the idea

I Never Do good until i know what im up against…. lol..
but i love the way you graded these…. very very nice… the time waiting was very worth it…. but im very suprized that i made it 3rd place….(i would have been suprize making 5th as well, lol) but the day Nielsie showed me his on MSN i knew who the winner was going to be lol… i wish i could come up with good ideas like that…

congratz, Nielsie ;)

These are awesome, everyone did a really good job, but some of the scripts have things I've never even seen before, I downloaded them all just to learn from.

lie3k nielsie is nubzor hwo did he win :p Nah great job guys. I actually think it was closer then people think… There is only so many ways to re invent the wheel.

Congratz nielsie! Your script is good, just been looking through it.

And Starblaster love how you set and wrote about each of the scripts, very easy to read. Must of took awhile to do it all. Good Job.