say your scripting refrence for begginers

[ARM]

say your scripting refrence for starting and being expert in scripting for begginers
:)

[Solid Snake]

Sorry, what?

[ARM]

say how did you start scripting.
and what refrence is helpful to be expert in it.

[Tumbleweed]

Started with those tutorials mentioned here (http://forums.epicgames.com/showthread.php?t=724939).

Becoming expert or at least advanced - Google, UDN (http://udn.epicgames.com/Three/UDKProgrammingHome.html), exploring the already existing code.

[Wormbo]

How I started scripting:

read the language reference (nowadays you can browse the UDN, that didn't exist back when I started with UnrealScript!)
read the source code
hack together small stuff
read the source code
hack together more small stuff
read the source code
browse UDN
read the source code
browse UnrealWiki
read the source code
hack together slightly larger stuff
read the source code
...

And in case you didn't get it:
Read the source code and start working upwards in terms of size!

[Blade[UG]]

Reading the source for as many Unreal Engine 2 games as I could possibly find. (and there are a ton of them)

[Floomi]

A four year course in Computer Science at University.

Scripting is easier when you already know how to code. Learning to code is easier when you have someone teaching you the basics (at least it was for me).

[spacepaw]

I agree with Floomi :) if you have no idea how to program at all first try to learn java or c# (or c++ but that's bit more difficult). When you'll be able to grasp the concepts of object oriented programming come back to Unreal Script :) it will be much easier

[KamiKaziKarl]

-Hacked N64 (used gameshark to read code)
-learned basic C
-learned XNA
-tore apart base UDK code
-tried simple ideas
-broke down base UDK code into a relation/function diagram
-started programming more complicated things

As stated above, READ what Epic gives you. Every action you could possibly use is referenced in some way in the code UDK comes with. If something cofuses you, read the base stuff and see where everything ties together. It will do wonders in helping you learn UnrealScript and understand coding in general.

[Blade[UG]]

as far as beginning programming itself goes, I went from Commodore BASIC to QuickBASIC (and several other variants of BASIC) to C, to dozens of interpreted/scripting languages.

[Tumbleweed]

Hehe, in that case I can say:
QBasic->looong break->tried C++ (failed)->Python->Haskell->tried C++ (failed)->Java->C#->C++ (success :P )
UnrealScript I wouldn't list here, because it's just for Unreal.

[Wormbo]

UnrealScript I wouldn't list here, because it's just for Unreal.

That excuse doesn't count. Any language counts when looking at the big picture.

Personally I started out with QBasic -> Visual Basic 4 (-> some Pascal) -> UnrealScript (!) -> Java -> C++/Perl/PHP/...
Knowing Visual Basic back then (10 years ago; VB actually still was "basic" without ) really helped me get used to the event-driven nature of UnrealScript. UnrealScript then helped me understand OOP and thus learning Java.