And RTFM. The docs on Easyuo.com are actually quite thorough, enough to get you going. If you have any kind of previous scripting/programming experience, it will help. You should learn some of the basics of procedural programming, such as conditionals, variables, arrays, loops, scope, etc. Once you get those basics down, things become much easier. Armed with the manual and some well designed scripts (such as TM's), oh, and a little can-do attitude, you'll be off and running in no time. A great thing about scripts and the ability to look at the code is "code reuse" (be sure to credit the original author).

/gC

Look for the Jesse Liberty books from O'Reilly for C# reference.  They are really the best I've come across so far.  The three books I use mostly are:

Learning C# (good starting reference)
Programming C# (great comprehensive, easy to read book)
C# Cookbook (Not by Jesse Liberty, but I highly recommend this one so you can get ideas about data structures, etc)

Oreilly books are legendary for being easy to follow without all the useless filler that you find in a lot of books. I think that's why they've been so successful, they are great reference books yes, but also great how to books.

/gC

Impressive!

And to think some people say scripting takes all the fun out of the game 

I wouldn't play this game if it weren't for scripting.

Maybe I will learn python after I get my head wrapped around perl then

Python is great. But....

Python is object oriented. A lot of people have a hard time understanding object oriented concepts because for most of the things they do, procedural is good enough (small projects, programs,etc). Perl is like a mash up of C, shell, awk, sed, and the kitchen sink. There's more than one way to do it (that's the motto). You can get caught up in the all of the idiosyncracies of syntax, but you can also make it very clean and understandable. I've heard C programmers say that perl looks like line noise. That's because you can fit a 1000 line C program into a command line length perl statement to accomplish the same thing.

Php is nice too, but I'd prefer to stick to perl for sysadmin or task oriented things, and php for web development, although php is quite capable of both (just not as popular). If you're working from a UNIX based system, one of the hard things to beat about perl is perldoc and the man pages. Python has an excellent help system, but I find it a bit more tedious to use.

Decide what you're going to do. Are you a scripter or are you a programmer with a computer science objective? I think if you're a scripter, ie, can whip up bash scripts, etc, then perl is going to feel natural to you. If you're a programmer with a CS slant, go with something more programmer like, such as python, C or C++, or java. You'll get more out of it.

/gC

Well, I can only speak for myself, and I have had runs where I haven't gotten a single kit in probably a couple hundred quest iterations.  Then there are times when I get 2 a day.  Perhaps other people have been more lucky, but if you are looking for heartwood kits/saws in particular and are holding your breath, my advise is just start breathing normally because you are going to be questing for a VERY long time, so just breath!

If you have only been running this script for a few days, you'll just have to keep at it.  I guarantee the kits will be looted, however if you are in felucca, you do have to be careful about thieves.

I've gone full weeks without getting green runics. I used to run this script quite a lot, and I can tell you, it is pretty random. There were days when I'd get 3, then I'd go 2 full weeks getting no greens.

/gC