#unityscript

数年ぶりにjsでUnity触った。。

また書き方忘れそうなのでメモ。

コンポーネントを取得するとき

C#

gameObject.GetComponent<Renderer>().enabled = true;

JavaScript

gameObject.GetComponent.<Renderer>().enabled = true;

I ran into a couple of issues while learning Unityscript that made me question if I should be learning it, instead of C#. I've come to the decision that I'll be going with C# due to its usability outside of Unity (as opposed to Unityscript being a unity only language) and all of the documentation found online for C#. This is a personal decision that I think a lot of people that are just getting into Unity and scripting will run into so I wanted to make a compilation of some discussion that I've found useful in helping me make a decision on the subject.

http://embracing-unity.blogspot.com/2013/05/unityscript-vs-c.html

http://forum.unity3d.com/threads/boo-c-and-javascript-in-unity-experiences-and-opinions.18507/

http://forum.unity3d.com/threads/scripting-section-faq.19302/

http://forum.unity3d.com/threads/do-you-script-in-unityscript-or-c-and-why-poll.201260/

http://www.reddit.com/r/Unity3D/comments/193m4p/starting_out_in_unity_c_or_javascript/

As you can see, it mainly comes down to personal preference and mechanically you can get the same-ish performance out of both of them via techniques. So if mechanics aren't an issue, what is? Like I mentioned earlier, online documentation is a huge factor on how fast you'll be able to learn the language. I say that because if you're anything like me, learning a language is a metric-shit-ton easier if you have a lot of material to cross-reference. Secondly, what if you find you want to do some programming outside of unity? Well if you spent all your time investing in Unityscript you'll only be able to take away the basics of coding/scripting from it and still be left with learning another set of syntax and rules.

I've found that over the course of learning the unityscript language it has been impossible for me to use only one guide and comprehend everything I'm reading. No matter how good I feel a guide is, none will ever be perfectly formatted and explained for my specific learning capabilities. So what have I done to help alleviate this problem? Cross reference, cross reference, cross reference. And that's what I'm here to post today. A list of a few scripting tutorials I've been going back and forth through when ever I'm starting to draw blanks on any particular subject.

This .pdf is what I suggest you focus on... bim.wikispaces.com/file/view/UnityScript_Basics_for_Noobs.pdf

Then use these sites to help you along the way... http://forum.unity3d.com/threads/34015-Newbie-guide-to-Unity-Javascript http://wiki.unity3d.com/index.php/Head_First_into_Unity_with_UnityScript https://docs.unity3d.com/Documentation/ScriptReference/ http://unity3d.com/learn/tutorials/modules/beginner/scripting

Let me tell you what. Every single time you get stumped while reading the .pdf just go between all of these sites (skip to the problem area's section) and after reading each of them go back to the .pdf. Do this till you understand the problem area. If you're anything like me, it may help everything click while also giving you a better understanding of the language as a whole.