Mafiascum.net

Unity is a cross-platform game engine developed by Unity Technologies and used to develop video games for PC, consoles, mobile devices and websites.
First announced only for OS X, at Apple's Worldwide Developers Conference in 2005, it has since been extended to target 21 platforms.

With an emphasis on portability, the engine targets the following APIs: Direct3D on Windows and Xbox 360; OpenGL on Mac, Linux, and Windows; OpenGL ES on Android and iOS; and proprietary APIs on video game consoles.
Unity allows specification of texture compression and resolution settings for each platform that the game engine supports, and provides support for bump mapping, reflection mapping,
parallax mapping, screen space ambient occlusion (SSAO), dynamic shadows using shadow maps, render-to-texture and full-screen post-processing effects.
Unity's graphics engine's platform diversity can provide a shader with multiple variants and a declarative fallback specification, allowing Unity to detect the best variant for the current video hardware and,
if none are compatible, to fall back to an alternative shader that may sacrifice features for performance.

Unity is notable for its ability to target games to multiple platforms. Within a project, developers have control over delivery to mobile devices, web browsers, desktops, and consoles.
Supported platforms include Android, Apple TV, BlackBerry 10, iOS, Linux, Nintendo 3DS line, OS X, PlayStation 4, PlayStation Vita, Unity Web Player (including Facebook), Wii, Wii U, Windows Phone 8,
Windows, Xbox 360, and Xbox One. It includes an asset server and Nvidia's PhysX physics engine. Unity Web Player is a browser plugin that is supported in Windows and OS X only, which has been deprecated in favor of WebGL.
Unity is the default software development kit (SDK) for Nintendo's Wii U video game console platform, with a free copy included by Nintendo with each Wii U developer license.
Unity Technologies calls this bundling of a third-party SDK an "industry first".

https://unity3d.com/get-unity/download
For the purposes of this project [and really any purposes you'll likely ever need..], I would suggest using the Free version.
For this, we will be using Version 5.42. Try to make sure you have an up to date version if you already have Unity on your system!
Follow the installation process and if you have any trouble then refer to this Unity troubleshooting page:
https://docs.unity3d.com/500/Documentat ... Unity.html

If you're still having issues, drop a post in the thread or give us a shout on the discord and we'll try to help you figure it out.
Once Unity is installed, you'll need to create a Unity account. There's no fee or anything for joining, it just gives you better access to various features which can help you with your Unity programming experience
[and it's mandatory but I mean..]
If all worked as it should have, you should see something like this when you run the Unity shortcut:

When you're developing/programming, it's usually best to try and keep all of your files as organized as possible.
Basically this lets you quickly/easily access stuff, saves you the headache of hunting around on your computer for where you saved something and helps you to keep your projects separated in a clean way.
You can mix things up a little if you want based on your personal preference of organizing things, but for me, I like to organize my projects as follows:
i) Create a folder on your desktop called "Development" [All of your programming files would then go in here]
ii) Create a folder within Development called "Unity" [All unity related files go in here and if you were to start using another language, you would create a new folder for it]
iii) Create a folder within Unity with the name of your project.

In this case, we'll be calling our project "HelloWorld". You can also help to organize your projects by giving them number prefixes to help you get to your most recent projects faster. IE: "01_HelloWorld"
[Sorting your folders by date made will also function in the same manner]

When Unity is first booted up and you're logged in, you will be brought to the Project Wizard screen. Unfortunately there are no real wizards here, only project specification options.
Set the project directory to point to your working directory as we set it up in the last task.
For the purposes of this first project, you won't need to worry about importing any packages so just ignore that mumbo jumbo for now.
Underneath the login there's an option for choosing whether the project is 2D or 3D. For now we're going to stick with 2D, so please change the project to be 2D.

https://docs.unity3d.com/Manual/Learnin ... rface.html

I've highlighted and elaborated on portions of the interface that I feel are most important to understand [at least to start out with].
:
A viewpoint that allows you to see the level that you're designing as you work. This viewpoint is meant to be flexible to allow you to get proper angles and orientations to edit things as you want them to look.
:
A viewpoint that allows you to see the level in the context of what the player will see as they play. You can only translate your viewpoint as a player playing the game and not as an editor. This is primarily for testing.
[Nothing will show up in this panel if your game isn't running]
:
Hierarchical text representation of every object in the scene. The hierarchy reveals the structure of how objects are attached to one another.
:
Shows all of your assets that you can currently use for your project
:
Allows you to view and edit all the properties of the currently selected object.
:
Place for the game to give text output for the programmer to see. Very useful for checking the status of various aspects of the game as it runs/testing for problems and bugs.
:
Tools for manipulating the scene in various ways.

:
"GameObjects are the fundamental objects in Unity that represent characters, props and scenery. They do not accomplish much in themselves but they act as containers for Components,
which implement the real functionality."
https://docs.unity3d.com/Manual/class-GameObject.html

Now that you've got your first project going and you're a little familiar with the interface, we're going to jump right into your very first Unity program!
The first thing you're going to need is a game object. In Unity, most game behavior is represented by how game objects are programmed to behave/how they interact with each other.
In this case, we want an object that is programmed specifically to send us a message. So, to start, go to the menu at the top, select the GameObject menu and create an empty object.
If you look at the Hierarchy panel, you'll see a new object called "GameObject" alongside the Camera that was there before. In general, you'll want to name all objects [and really everything you ever use] in a way
that makes it a little more clear to you as to what they do.
IE: This gameobject that is going to send a message to you might be better named "Messenger" rather than just "GameObject". So, click it once and rename it.

Next, we want to actually create the code that will attach to this object to create and send the message to us when the code is running.
Move your attention to the Project Panel and find the Asset section. Right click and under the create section, choose C# Script. A new C#Script file will show up under the asset section with a generic name.

We'll rename this file to SendMessage.
Open SendMessage and once you're done loading, you should see something similar to the following:


This is essentially your first Unity Program. There's a decent amount to take in here if you’ve never programmed before or are a little inexperienced, so I'll ask you to mainly focus on two parts of the program:

i) // Use this for initialization
void Start () {

}

ii) // Update is called once per frame
void Update () {

}

The first block is a section of the code that will run when the object is created.
The second block is a section of code that will run constantly while the program is running.
For the purposes of HelloWorld, all we really want to do is send a single message to ourselves, so we'll focus primarily on the Start block.
In the empty line between "void Start() {" and "}" we're going to add Debug.Log("Hello world!");
This will write "Hello world!" to the Console [a part of the interface] when the program first starts if it is attached to an object.
Also, replace NewBehaviorScript with SendMessage in this line if it hasn't already been changed otherwise you may get a compilation error:
"public class SendMessage : MonoBehaviour"

Save and close your code editor and return to the Unity Editor. We have a script, but as of right now the script isn't doing anything because it isn't attached to a Unity Object. Think of a script as behavior and an object as something that does that behavior. IE: Walking could be a script and a person could be an object. A person can’t walk unless it is instructed to do so, right?

To instruct the Messenger object to send us a message, double click on it and bring your attention to the inspector panel. You should see a button that says "Add Component", click that and choose Scripts and then assign the SendMessage script that we created to it. If it worked, you should see the script as part of the object in the inspector panel:


And we're nearly there! All of our program has been set up to run properly, now all you need to do is actually run the program. If you look at the top at the toolbar, you'll see a play button. If you hit play, your program will start.
If you click on the console, you'll see the following when your program is running:


If you've reached this point, you've completed lesson one without incident! Congrats!