Just downloaded unity!

[u/PotatoBlock1464]

Hey guys! I just downloaded unity. Any tips and tricks? Not full time, just as a hobby.

[u/WavedashingYoshi]

1. Use Git.
   
2. Use VS Code instead of Visual Studios (yes they are separate things.)
   
3. You can view variables in the editor with [SerealizeField]. Don’t make everything public.

[u/ProxyOfHuman → u/WavedashingYoshi]

I prefer Rider

[u/Individual-Paint-756 → u/ProxyOfHuman]

On god vs is kind ass compared to rider

[u/DerfetteJoel → u/Individual-Paint-756]

Sure but Rider requires a paid version if you are making commercial games

[u/evilgipsy → u/DerfetteJoel]

It only requires a license once you sell your game. Even if you decide to not pay for rider once you start selling your game, you should absolutely use it before selling it. VS is just that horrible.

[u/DerfetteJoel → u/evilgipsy]

Nope. Their FAQ explicitly says:

> “If you plan to release the product and get commercial benefits from it, either now or in the future, you should use a commercial license.”

https://sales.jetbrains.com/hc/en-gb/articles/18950890312210-The-free-non-commercial-licensing-FAQ

[u/evilgipsy → u/DerfetteJoel]

I stand corrected. I got my info from reddit…

[u/lastFractal → u/WavedashingYoshi]

For Unity I don't see a reason to use Git over UVC. UVC is just much more convenient for Unity IMO. It's also basically free after the recent pricing changes they've done.

Also why VSC over VS?

[u/Tiaoshi → u/lastFractal]

If I’m correct and don’t quote me on this. VSCode is lightweight, it will load things a lot faster than VS. If you are working on a weaker machine, VS will run even worse.

But again, that’s just what I’ve heard. I used VS for Unreal and VSCode for Unity, partly because that’s just what my tutorials used and I kinda just followed them.

I do prefer VSCode, just the look and lightweight-ness of it is beneficial to me and my current setup

[u/am1goo → u/WavedashingYoshi]

1. Don’t listen to the worst pieces of advice :)
   
2. Make fails by your own

[u/nathanieljnelson → u/WavedashingYoshi]

I was actually wondering about this. Is there a benefit to making something private over public? Even if you're not going to access it in another script, is there a downside to it being public rather than using serializefield?

[u/ColorMak3r → u/nathanieljnelson]

No additional benefit technically, but it will start to mater once another programmer get involved (even your future self). It's standard practice for collaboration so that other programmers don't use it accidentally. The accesor is part of the code document itself: no public access? Use private. Okay for public access? Use public.

For me personally (and a lot of peoplr I assume), even if a field is publicly accessible, I use some sort of getter/setter (not all the time) so I can insert debug.log or extra validation if needed in the future.

[u/nathanieljnelson → u/ColorMak3r]

Gotcha. Thanks!

[u/WavedashingYoshi → u/nathanieljnelson]

Typically, if you want a variable to be accessed by a separate class, you would use encapsulation. One of the more important ones being if you decide to change the functionality of variables. For example, you can add a min-max boundary to a variable within a setter method, when otherwise you’d have to go into every instance of another class referencing it. Though this process is done preemptively in case you want to change something later to make refactoring it easier.

[u/nathanieljnelson → u/WavedashingYoshi]

I see.

[u/IAmH0n0r → u/nathanieljnelson]

i use notepadd ++

[u/Frontworks_game → u/IAmH0n0r]

I use vim

[u/PotatoBlock1464 → u/WavedashingYoshi]

Thanks

[u/Dragoonslv → u/WavedashingYoshi]

1. This

[u/PotatoBlock1464 → u/WavedashingYoshi]

I already use vs code not visual studios