Uploaded December 2019 | Updated November 2026, 2 hours ago
Your terminal can maintain a list of directories you have visited by storing them in a stack. You can manipulate this stack using commands like `pushd` to push a new entry onto this stack or `popd` to pop an existing entry off of the current stack. We can also take advantage of this directory stack to create easily navigable sets of directories when we need to work with multiple directories simultaneously. An example that sets up a three directory workspace with three directories named `a`, `b` and `c` might look like this:
```sh
pushd c
pushd ../b
pushd ../a
pushd .
dirs -v
```
Running the commands above may result in a directory stack that looks like this:
```sh
0 ~/a
1 ~/a
2 ~/b
3 ~/c
```
To move to directory in the third index (`~/c`) we would use `cd ~3`. Using the `cd` command will modify the top element of the stack - this is why we push the current directory onto the stack after we have added each directory we want to visit.
To view the current stack of directories you may use: `dirs -v`. This will display a list of directories and their position within the stack.
To clear the directory stack you may use: `dirs -c`.
More on working with directory stacks in your shell: youtube.com/watch?v=UDD7EyGr8fU
Join the World of Zero Discord Server: discord.gg/hU5Kq2u
Your terminal can maintain a list of directories you have visited by storing them in a stack. You can manipulate this stack using commands like `pushd` to push a new entry onto this stack or `popd` to pop an existing entry off of the current stack. We can also take advantage of this directory stack to create easily navigable sets of directories when we need to work with multiple directories simultaneously. An example that sets up a three directory workspace with three directories named `a`, `b` and `c` might look like this:
```sh
pushd c
pushd ../b
pushd ../a
pushd .
dirs -v
```
Running the commands above may result in a directory stack that looks like this:
```sh
0 ~/a
1 ~/a
2 ~/b
3 ~/c
```
To move to directory in the third index (`~/c`) we would use `cd ~3`. Using the `cd` command will modify the top element of the stack - this is why we push the current directory onto the stack after we have added each directory we want to visit.
To view the current stack of directories you may use: `dirs -v`. This will display a list of directories and their position within the stack.
To clear the directory stack you may use: `dirs -c`.
More on working with directory stacks in your shell: youtube.com/watch?v=UDD7EyGr8fU
Join the World of Zero Discord Server: discord.gg/hU5Kq2u

 to your projects for common namespaces used in projects of the type youve chosen. This can help you get started more quickly in .NET by automatically importing common namespaces like `System` and `System.Linq` without you having to explicitly declare them somewhere in your projects.
You can turn on Implicit Usings in your .NET 6 projects by adding this line to your Project file.
```csproj
˂ImplicitUsings˃enable˂/ImplicitUsings˃
```
Implicit Usings introduce namespaces into the global space. You can learn more about how to add your own custom namespaces here by using `global` usings: https://youtu.be/z4THCW3b16k
Note: You can always check which implicit usings are being generated for your project by navigating to your projects `obj` directory and finding the generated file named: `[Your Projects Name].GlobalUsings.g.cs`.
You can find a more in-depth dive into this feature here: https://dotnetcoretutorials.com/2021/08/31/implicit-using-statements-in-net-6/
Join the World of Zero Discord Server: https://discord.gg/hU5Kq2u Lets Explore Implicit Usings in C# 10](https://i.ytimg.com/vi/NlvhBpLl0DY/mqdefault.jpg)



 and Docker which allows us to create new commands inside of Minecraft and then Docker provides a container layer so we can easily reproduce new Minecraft servers. In this video were going to focus on how to create new commands with Spigots APIs.
To do this well need to implement a [`CommandExecutor`](https://hub.spigotmc.org/javadocs/spigot/org/bukkit/command/CommandExecutor.html). This is an interface which has a single `onCommand` function that needs to be Overridden. `onCommand` will then be invoked when the command is used in-game and will pass a number of useful properties into the function for you to use (like who used it and what arguments were used).
There are three configurations you need to make in order to actually get your new Command to execute though.
## `plugin.yml`
The first place you need to configure is the `commands` section of the `plugin.yml` which is used to define the properties of your plugin/mod. In order to do this youll need to add the following your `yaml` file.
```yaml
commands:
commandName:
description: A custom minecraft command in spigot
usage: /commandName
aliases: [commandAlias]
```
The `commandName` is the name of the Command. Players will see this in the servers auto-complete. The `commandName` is also used later to register the `CommandExecutor`.
The description describes what the command is for, usage is displayed as helper text for how to use the command and aliases are alternative ways to call the command. In this example `/commandAlias` could be used exactly like `/commandName`.
## `App.java`
This is the main entry point for your program. When our plugin is loaded we need to register the `CommandExecutor` to connect with the command setup in our `plugin.yml`. To set this up youll want to add something like this to your Apps `onEnable` function.
```java
MyCommandExecutor command = new MyCommandExecutor ();
this.getCommand(commandName).setExecutor(command);
```
Note: `commandName` should match your `commandName` from the `plugin.yml` above.
## `MyCommandExecutor.java`
The final piece of the puzzle is a class which implements `CommandExecutor`. This is the definition of the `CommandExecutor` you pointed to in the `App.java` code.
```java
public class MyCommandExecutor implements CommandExecutor {
@Override
public boolean onCommand(CommandSender sender, Command command, String label, String[] args) {
sender.sendMessage(Ten four. Commencing operation dance off.); // 💃🕺
return true;
}
}
```
Once you have configured all three of these properties you should be able to build your plugin, install it on your server and run it. You should be able to type `/commandName` in your server and get Ten four. Commencing operation dance off. as a response.
***
MC-Clone is a project to create a Minecraft mod which will allow you to clone all or part of your current world into a brand new world with modified settings. For example copying your survival build into a creative world so you can test your next project. The mod will allow you to host these new servers in Docker and will also have some logic to shut down the custom servers once they become inactive so youre not running an ever increasing number of servers. These videos are my process of creating the plugin and what I learn along the way.
Join the World of Zero Discord Server: https://discord.gg/hU5Kq2u Starting to Build a Spigot Minecraft Mod - Building MC-Clone - Part 1](https://i.ytimg.com/vi/ODLx4yJNtJA/mqdefault.jpg)



- [TheNaturalTanuki](https://github.com/TheNaturalTanuki)
- [BaalEvan](https://github.com/BaalEvan)
For their contributions!
As time permits well also take a look at some of the other projects weve been working on and poke around with adding new features to those. Open Source Contributions and Other Projects](https://i.ytimg.com/vi/POVJ-QIyygE/mqdefault.jpg)

