Uploaded September 2019 | Updated November 2026, 1 hour ago
Zenject is a Dependency Injection Container Framework built for .NET that is also compatible with Unity. Lets learn some of the basics of how to get Zenject setup and start injecting components.
The "Hello World" example for Zenject is here with instructions: github.com/modesttree/Zenject#hello-world-example
Dependency Injection is an Inversion of Control design pattern that switches the way classes find and resolve their dependencies. Instead of an object declaring the specific dependencies it uses the classes declare the types of their dependencies and a second controller identifies and "injects" those dependencies for the object to use.
This helps keep your objects a bit easier to maintain at the cost of some initial abstraction. Because your dependencies are injected into the classes instead of each class declaring their dependencies changing each dependency across an entire project can be done in a single place without having to modify large amounts of code. Additionally, when constructing tests for your project you can use this pattern to easily inject new behavior (either through mocks/fakes or with real implementations) that make your tests more predictable and easier to understand.
A potentially good use of Zenject is in place of the common static Game Manager classes a lot of games seem to inherit. These classes typically contain static references to dozens of different objects that control various parts of the game. As implemented this means that a single object has to understand all or most of how your game works. This typically leads to a large or difficult to maintain type. Using Dependency Injection each of those subtypes of the Game Manager can be their own dependency which is only injected into the classes that actually need to reference the component.
Zenject on GitHub: github.com/modesttree/Zenject
Zenject on the Unity Asset Store: assetstore.unity.com/packages/tools/integration/zenject-dependency-injection-ioc-17758
Join the World of Zero Discord Server: discord.gg/hU5Kq2u
Zenject is a Dependency Injection Container Framework built for .NET that is also compatible with Unity. Lets learn some of the basics of how to get Zenject setup and start injecting components.
The "Hello World" example for Zenject is here with instructions: github.com/modesttree/Zenject#hello-world-example
Dependency Injection is an Inversion of Control design pattern that switches the way classes find and resolve their dependencies. Instead of an object declaring the specific dependencies it uses the classes declare the types of their dependencies and a second controller identifies and "injects" those dependencies for the object to use.
This helps keep your objects a bit easier to maintain at the cost of some initial abstraction. Because your dependencies are injected into the classes instead of each class declaring their dependencies changing each dependency across an entire project can be done in a single place without having to modify large amounts of code. Additionally, when constructing tests for your project you can use this pattern to easily inject new behavior (either through mocks/fakes or with real implementations) that make your tests more predictable and easier to understand.
A potentially good use of Zenject is in place of the common static Game Manager classes a lot of games seem to inherit. These classes typically contain static references to dozens of different objects that control various parts of the game. As implemented this means that a single object has to understand all or most of how your game works. This typically leads to a large or difficult to maintain type. Using Dependency Injection each of those subtypes of the Game Manager can be their own dependency which is only injected into the classes that actually need to reference the component.
Zenject on GitHub: github.com/modesttree/Zenject
Zenject on the Unity Asset Store: assetstore.unity.com/packages/tools/integration/zenject-dependency-injection-ioc-17758
Join the World of Zero Discord Server: discord.gg/hU5Kq2u
 from an earlier video on the channel.
When this grid snapping is applied against a mesh there are a few additional decisions we need to make. This includes what coordinate space we want to perform the operation in. Coordinate spaces describe an object relative to that space. For example an object space representation is an identical representation for each version of that object whereas a world space version of the same object would describe the unique position, rotation and scale of that object in the world. Which coordinate space we decide to create our grid in will effect the final result: if we snap vertices in object space then even as that object is rotated or moved through the world the rounded vertices will not change. However if we perform the grid snapping in world space the final results will change as the object is moved and rotated through the world. Depending on the effect we want to achieve different coordinate spaces may be more appropriate. For our testing purposes though well just use object space since this is the most straightforward to implement.
The vertex shader code that snaps to a grid looks like this (this is the surface shader implementation):
```shader
void vert(inout appdata_full v) {
v.vertex /= _GridSize;
v.vertex = round(v.vertex);
v.vertex *= _GridSize;
}
```
Note: the syntax is slightly different between the Surface Shader and Vertex Shader implementations however the principals are the same. Both implementations are demonstrated in the video.
You can view the entire playlist of implementing this effect here: https://www.youtube.com/playlist?list=PLEwYhelKHmiixWR3Tn5dYt1iUlSCL6OFq
***
More Visual Effects weve built on World of Zero: https://www.youtube.com/playlist?list=PLEwYhelKHmig6ttzH0nRL3OOQsGLtVrtX
Unitys Surface Shader examples: https://docs.unity3d.com/Manual/SL-SurfaceShaderExamples.html
If youre interested in learning more about coordinate spaces (object space/world space/etc) this article goes into a bit more depth and also describes the relationships between the different coordinate spaces: http://davidlively.com/programming/graphics/coordinate-spaces/
The Bomber Bug asset is located here: https://assetstore.unity.com/packages/p/bomber-bug-pack-pbr-63127
Come chat in the World of Zero Discord Server: https://discord.gg/hU5Kq2u What Happens When You Snap Vertices To A Grid?](https://i.ytimg.com/vi/e8NItqF_9hQ/mqdefault.jpg)



![Getting Started Building Pong in my Terminal - Pong in Bash - Part 1
Ive been exploring a few of the fun ways you can write text to a terminal. One of the more interesting commands available for this is `tput`. The `tput` command provides a variety of options for updating or checking the state of your terminal. This includes things like making text **bold**, *italics* or underlined. You can leverage `tput` to change the color of the foreground and background of your terminal. For us though were going to use it to position the cursor. This will allow us to simulate moving an object in the terminal like the ball in pong by updating the cursor position we draw at.
For this video well be looking to explore that capability by starting work on building pong in our shell. Our initial goal is to build a simple ball that bounces left and right horizontally across our screen (vertical movement and paddles will come later). This will involve creating a basic REPL (read-execute-print-loop) script in bash that can track the velocity and position of the ball, print the ball at its current position and test if the ball has collided with either side of the terminal.
* `tput cup [row] [column]` updates the cursor position to the provided row and column (zero indexed).
* `tput cols` returns the number of columns in the current terminal window.
* `tput rows` returns the number of rows in the current terminal window.
Our basic script looks like this after implementing this:
```sh
#!/bin/bash
width=$(tput cols)
echo width = ${width}
ball_x=$((width / 2))
echo ball pos = ${ball_x}
ball_vel_x=$((1))
trap tput cnorm; exit SIGINT
tput civis
while true; do
ball_x=$((ball_x + ball_vel_x))
# Hit the right hand wall
if [ $ball_x -gt $width ]; then
ball_vel_x=$((-1))
fi
if [ $ball_x -lt 1 ]; then
ball_vel_x=$((1))
fi
clear
tput cup 0 $ball_x
echo o
done
```
Note: not mentioned in the video, but Ive included a `trap` to restore the cursor to its normal visibility when you exit the script (more on this in a future video).
If youre looking for a deeper dive into tput linuxcommand.org has put together a great resource with a number of examples demonstrating many of the features of tput: http://www.linuxcommand.org/lc3_adv_tput.php
Ive been live streaming development and some games on Twitch at: https://www.twitch.tv/worldofzerodev
Join the World of Zero Discord Server: https://discord.gg/hU5Kq2u Getting Started Building Pong in my Terminal - Pong in Bash - Part 1](https://i.ytimg.com/vi/fEtcGFEiuQM/mqdefault.jpg)



![Adding an Accent to our Contrast Shader - Lets Make a Side Scrolling Shooter - Part 4
Lets spice up our our contrasting transition shader with an accent color that more clearly marks the border between one color and the next.
Part 1 of building this contrasting shader is here: https://www.youtube.com/watch?v=jJcSbixSy5c
Most of the magic of this shader happens in these lines which select the color we want to draw:
```
float maskPrimary = (_Transition + barrierSize [LESS THAN] maskStrength);
float maskSecondary = (_Transition - barrierSize [GREATER THAN] maskStrength);
float maskAccent = !(maskPrimary || maskSecondary);
o.Albedo = maskPrimary * _PrimaryColor
+ maskSecondary * _SecondaryColor
+ maskAccent * _AccentColor;
```
Come join the World of Zero Discord channel to talk software, game development and more: https://discord.gg/hU5Kq2u Adding an Accent to our Contrast Shader - Lets Make a Side Scrolling Shooter - Part 4](https://i.ytimg.com/vi/gu_bFoI2fIg/mqdefault.jpg)


Join the World of Zero Discord Server: https://discord.gg/hU5Kq2u Implementing Scene Switching - An Elevator Between Scenes - Part 2](https://i.ytimg.com/vi/hr6ox4bg3Ow/mqdefault.jpg)