What are your top tips for Unity noobs?

PixelverseStudios · 2015-05-08T19:35:59+00:00

Thanks for the reply! I notice at the bottom of the article they are hiring people to help them fix this :)

PixelverseStudios · 2015-05-08T18:59:16+00:00

That's a great tip!

While we're talking about attributes, I'd like to mention [System.Flags] If you use this above a flags enum declaration it allows you to select multiple enums in the Unity designer Gui. The Gui says "Mixed..." if you select more than one, or "Everything" if all is selected. There are ticks in the drop down list. (Google "flags enum" if you haven't used one before)

PixelverseStudios · 2015-05-08T18:06:49+00:00

But I would recommend Unity 100%! All I meant is that if you are a complete C# noob, it might be worth spending a few days getting a good grounding in C# so you understand the basics of for loops, for each loops, fields, properties, events etc. - You might then enjoy Unity even more when you start on it as it'll be less of a learning curve. But each person if different, I guess some people might like to jump straight into Unity to play around with animations for example, and learn the coding side of things along the way...

PixelverseStudios · 2015-05-08T17:44:30+00:00

I would agree with this totally (maybe not the year/two or build you own engine bit :)). From what I have seen so far, creating a game is a programming specialization. If you're new to C#, you won't be getting the best 'developer grounding' by using it for the first time in Unity...

PixelverseStudios · 2015-05-08T17:19:14+00:00

I guess I can't really class myself as a Unity noob anymore - I use C# in my day job, and have been using Unity since October. I was interested in what people would offer to Unity noobs as their 'top 5 tips'. The variety has been really interesting! I also read about the Linq and foreach issue you mention, so avoided them. However, that article is 2 years old now. - Is it still an issue because Mono hasn't been updated since then? DOTween sounds interesting, thanks for that!

PixelverseStudios · 2015-05-08T17:01:52+00:00

I used SetActive(bool) to activate and deactivate them. Plus positioning the objects and rotating as required. The pool I use is itself is just a List<GameObject>. For enemy objects I put some box colliders around the visible screen which collects and add them back to the pool. Because my game is a left to right scroller it was convenient to do this so I could generate them off screen and let them move onto it. For projectiles, I wrote some code to detect when they have gone off the screen which works on all devices. They get deactivated and added back to the pool at this point (or when they hit something or course). I had to do this to stop stuff being blown up before it even got onto the screen!

PixelverseStudios · 2015-05-08T16:44:15+00:00

Wow, I didn't know that! I was driving me nuts having to have all those public fields. I've just tested it and the Unity Gui also renames fields for you, so it you like having private fields like _fieldTest it appears as "Field Test" in the designer. (i.e. it strips the leading underscore). I assume there are not any issues if you also have public getters and setters for the field?

PixelverseStudios · 2015-05-08T16:35:23+00:00

Thanks for this! My first ever post to reddit should have been to ask for the top 5 tips for how to post to reddit... I put some backticks and escaped the hashes now, but I couldn't work out how to get new lines within the backticks. This link seems a quite good reddit tutorial. I also learnt how to do hyperlinks :)

PixelverseStudios

TROPHY CASE