diff --git a/.vitepress/config.mts b/.vitepress/config.mts
index 11997a3..34e008c 100644
--- a/.vitepress/config.mts
+++ b/.vitepress/config.mts
@@ -73,7 +73,9 @@ export default defineConfig({
{ text: 'Launching the Game', link: '/getting-started/launching-the-game' },
{ text: 'Launching Servers', link: '/getting-started/launching-servers' },
{ text: 'Access Wideners', link: '/getting-started/access-wideners' },
- { text: 'Mixins', link: '/getting-started/mixins' }
+ { text: 'Mixins', link: '/getting-started/mixins' },
+ { text: 'Basic Problem Solving', link: '/getting-started/basic-problem-solving' },
+ { text: 'Using The IDE Effectively', link: '/getting-started/using-the-ide' }
]
}
],
diff --git a/blocks/index.md b/blocks/index.md
index 120e642..5827d50 100644
--- a/blocks/index.md
+++ b/blocks/index.md
@@ -161,7 +161,7 @@ Since the example block does not have a complex blockstate, only one entry is re
}
```
-Blockstates are really complex, which is why they are addressed in an upcoming page: [Block States](./_assets/blockstates)
+Blockstates are really complex, which is why they are addressed in an upcoming page: [Block States](/blocks/blockstates)
Restarting the game, or reloading via F3 + T to apply changes - you should be able to see the block texture in the inventory and physically in the world:
diff --git a/getting-started/_assets/basic_problem_solving_01.png b/getting-started/_assets/basic_problem_solving_01.png
new file mode 100644
index 0000000..51cc026
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_01.png differ
diff --git a/getting-started/_assets/basic_problem_solving_02.png b/getting-started/_assets/basic_problem_solving_02.png
new file mode 100644
index 0000000..ce0390b
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_02.png differ
diff --git a/getting-started/_assets/basic_problem_solving_03.png b/getting-started/_assets/basic_problem_solving_03.png
new file mode 100644
index 0000000..3e5ffdd
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_03.png differ
diff --git a/getting-started/_assets/basic_problem_solving_04.png b/getting-started/_assets/basic_problem_solving_04.png
new file mode 100644
index 0000000..fa0c315
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_04.png differ
diff --git a/getting-started/_assets/basic_problem_solving_05.png b/getting-started/_assets/basic_problem_solving_05.png
new file mode 100644
index 0000000..a57f7db
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_05.png differ
diff --git a/getting-started/_assets/basic_problem_solving_06.png b/getting-started/_assets/basic_problem_solving_06.png
new file mode 100644
index 0000000..0518e6e
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_06.png differ
diff --git a/getting-started/_assets/basic_problem_solving_07.png b/getting-started/_assets/basic_problem_solving_07.png
new file mode 100644
index 0000000..cc18a4d
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_07.png differ
diff --git a/getting-started/_assets/basic_problem_solving_08.png b/getting-started/_assets/basic_problem_solving_08.png
new file mode 100644
index 0000000..261b2af
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_08.png differ
diff --git a/getting-started/_assets/basic_problem_solving_09.png b/getting-started/_assets/basic_problem_solving_09.png
new file mode 100644
index 0000000..3ba6872
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_09.png differ
diff --git a/getting-started/_assets/basic_problem_solving_10.png b/getting-started/_assets/basic_problem_solving_10.png
new file mode 100644
index 0000000..e35f639
Binary files /dev/null and b/getting-started/_assets/basic_problem_solving_10.png differ
diff --git a/getting-started/basic-problem-solving.md b/getting-started/basic-problem-solving.md
new file mode 100644
index 0000000..465d9eb
--- /dev/null
+++ b/getting-started/basic-problem-solving.md
@@ -0,0 +1,228 @@
+---
+title: Basic Problem Solving
+description: Learn how to solve simple issues and mistakes on your own.
+order: 6
+---
+
+# Basic Problem Solving
+
+Issues, mistakes and bugs can happen even to the best programmer. You can develop a basic set of steps to potentially identify and resolve those issues without the help of others. Problems solved on your own can teach you many things and also feel rewarding. However, if you are stuck without being able to fix the problems by yourself, there is no shame in asking others for help.
+
+This page focuses mostly on functionality which is provided by IntelliJ (and many other IDEs) such as Logging and how to use the Debugger.
+
+## Console and LOGGER
+
+The most basic but also fastest tool to identify problems is the console. Values can be printed there at "run-time" which can inform the developer about the current state of the code and makes it easy to analyze changes and potential mistakes.
+
+In the `ModInitializer` implementing entry point class of the mod, a `LOGGER` is used by default, to print the desired output to the console.
+
+```java
+public class MyMod implements ModInitializer {
+ public static final String MOD_ID = "mod_id";
+ public static final Logger LOGGER = LoggerFactory.getLogger(MOD_ID);
+
+ @Override
+ public void onInitialize() {
+ // ...
+ }
+}
+```
+
+Whenever you need to know a value for something at a specific point in the code, use this `LOGGER` by passing the `String` value to its `info(...)` method.
+
+```java
+public class TestItem extends Item {
+
+ public TestItem(Settings settings) {
+ super(settings);
+ }
+
+ @Override
+ public ActionResult useOnEntity(ItemStack stack, PlayerEntity user, LivingEntity entity, Hand hand) {
+ // Values are used in a String to provide more information
+ TestMod.LOGGER.info("Is Client World: " + user.getWorld().isClient()
+ + " | Health: " + entity.getHealth() + " / " + entity.getMaxHealth()
+ + " | The item was used with the " + hand.name()
+ );
+
+ return ActionResult.SUCCESS;
+ }
+}
+```
+
+When, in this case, the `TestItem` is used on an Entity it will provide the values at this current state of the mod in the console of the currently used instance. If your `Run` window for the console is missing, you can open a new one in the toolbar at the top (`View > Tool Windows > Run`), if you are working with IntelliJ.
+
+
+
+### Keeping the console clean
+
+Keep in mind that this will also be printed if the mod is used in any other environment. This is completely optional, but I like to create a custom `LOGGER` method and use that, instead of the `LOGGER` itself to prevent printing data, which is only needed in a development environment.
+
+```java
+public class MyMod implements ModInitializer {
+ public static final String MOD_ID = "mod_id";
+ public static final Logger LOGGER = LoggerFactory.getLogger(MOD_ID);
+
+ @Override
+ public void onInitialize() {
+ // ...
+ }
+
+ public static void devLogger(String loggerInput) {
+ // prevent usage if the Instance is not run in a development environment
+ if (!FabricLoader.getInstance().isDevelopmentEnvironment()) return;
+
+ // customize that message however you want...
+ TestMod.LOGGER.info("DEV - [" + loggerInput + "]");
+ }
+}
+```
+
+Otherwise clean up the `LOGGER` usage as much as you can, to prevent causing a headache for Modpack developers and curious users.
+
+### Locating the issues
+
+The Logger prints the `MOD-ID` in front of the line. The Search function CTRL / CMD + F can be used to highlight it, making it easier to spot the problem. Missing assets, such as the Purple & Black placeholder when a texture is missing, also print their errors in the console and mention their missing files. You can also use the Search function here and look for the asset name in question.
+
+
+
+
+
+## Debugging
+
+### Breakpoint
+
+A more "sophisticated" way of debugging is the usage of Breakpoints in an IDE. As their name suggests, they are used to halt the executed code at specific locations and make it possible to inspect and modify the state of the software with a variety of tools.
+
+When working with Breakpoints, the Instance needs to be executed using the `Debug` option instead of the `Run` option.
+
+
+
+Let's use a custom Item as an example again. The Item is supposed to increase its efficiency level, whenever it has been used. But whenever this happens all the remaining enchantments get removed. How can this issue be resolved?
+
+```java
+// problematic example code:
+
+public class TestItem extends Item {
+
+ public TestItem(Settings settings) {
+ super(settings);
+ }
+
+ @Override
+ public ActionResult useOnBlock(ItemUsageContext context) {
+ ItemStack itemStack = context.getStack();
+ World world = context.getWorld();
+ BlockPos pos = context.getBlockPos();
+
+ if (world.isClient()) return super.useOnBlock(context);
+
+ int levelOfEfficiency = EnchantmentHelper.getLevel(Enchantments.EFFICIENCY, itemStack);
+
+ itemStack.removeSubNbt("Enchantments");
+ itemStack.addEnchantment(Enchantments.EFFICIENCY, levelOfEfficiency + 1);
+
+ if (levelOfEfficiency > 10) {
+ world.createExplosion(context.getPlayer(), pos.getX(), pos.getY(), pos.getZ(), 2, true, World.ExplosionSourceType.MOB);
+ }
+
+ return ActionResult.SUCCESS;
+ }
+}
+```
+
+Place a Breakpoint by clicking right next to the line number. You can place more than one at once if needed.
+
+
+
+Then let the instance execute this part of the code. In this case, the custom Item needs to be used on a Block. The Instance should freeze and in IntelliJ a yellow arrow right next to the Breakpoint appears. This indicates at which point the Debugger is currently. In the `Debug` window the controls can be used to move the current execution point using the blue arrow icons. This way the code can be processed step by step.
+
+
+
+The "Step over" function is the most common one so try to get used to its Keybind (F8)
+
+If you are done with the current inspection you can press the `Resume Program` button at the left side of the `Debug` window. This will un-freeze the Minecraft instance and further testing can be done.
+
+Currently, loaded values and objects are listed on the right side of this window, while a complete Stacktrace is on the left side. You can also hover, with the Mouse Cursor, over the values in the code. If they are in scope and are still loaded a window will show their specific values too.
+
+
+
+Not loaded Integer vs. loaded Integer
+
+If we inspect the `ItemStack` object we can see that the enchantments are stored as NBT values. The `removeSubNbt()` method removes all SubNbt values with the "Enchantments" key.
+
+
+
+To avoid that, only the specific enchantment needs to be removed. This can be done using the `EnchantmentHelper` in combination with filtering a `Stream`.
+
+```java
+@Override
+public ActionResult useOnBlock(ItemUsageContext context) {
+ ItemStack itemStack = context.getStack();
+ World world = context.getWorld();
+ BlockPos pos = context.getBlockPos();
+
+ if (world.isClient()) return super.useOnBlock(context);
+
+ int levelOfEfficiency = EnchantmentHelper.getLevel(Enchantments.EFFICIENCY, itemStack);
+
+
+ // Get a list of the itemStack's enchantments
+ var enchantments = EnchantmentHelper.fromNbt(itemStack.getOrCreateNbt().getList("Enchantments", NbtElement.COMPOUND_TYPE));
+ var filteredEnchantments = enchantments.entrySet().stream()
+ // Keep only enchantments which aren't EFFICIENCY
+ .filter(entry -> !(entry.getKey().equals(Enchantments.EFFICIENCY)))
+ // collect the entries of the stream for the final itemStack's enchantments Map
+ .collect(Collectors.toMap(Map.Entry::getKey, Map.Entry::getValue));
+
+ // put the changed enchantments Map (without the efficiency) back on the itemStack
+ EnchantmentHelper.set(filteredEnchantments, itemStack);
+
+ // add the efficiency enchantment back with the new level
+ itemStack.addEnchantment(Enchantments.EFFICIENCY, levelOfEfficiency + 1);
+
+ if (levelOfEfficiency > 10) {
+ world.createExplosion(context.getPlayer(), pos.getX(), pos.getY(), pos.getZ(),
+ 2, true, World.ExplosionSourceType.MOB);
+ }
+
+ return ActionResult.SUCCESS;
+}
+```
+
+### Breakpoints with conditions
+
+Sometimes it is necessary to only halt the code when certain conditions are met. Create a basic Breakpoint and right-click it to open the Breakpoint's settings. In there, you can use boolean statements for the condition.
+
+
+
+### Reloading an active Instance
+
+It is possible to make limited changes to the code, while a Minecraft instance is running. Method bodies can be rewritten at run-time using the `Debug` option instead of the `Run` option. This way, the Minecraft instance doesn't need to be restarted again. This makes e.g. testing Screen element alignment and other feature balancing faster.
+
+
+
+When the instance is running and changes to the code have been made, use `Build Project` to reload the changes. This process is also known as "Hotswap". If the changes were applied to the current instance, a green notification will be shown.
+
+
+
+
+
+Correct Hotswap vs. failed Hotswap
+
+Other changes can be reloaded in-game.
+
+- changes to the `assets/` folder -> press `[F3 + T]`
+- changes to the `data/` folder -> use the `/reload` command
+
+## Logs and crash report files
+
+The console of a previously executed instance helps with finding the issues. They are exported into the log files, located in the Minecraft instance's `logs` directory. The newest log is usually called `latest.log`. Users can send this file, for further inspection, to the mod developer or host the file content on code-hosting websites.
+
+In the development environment you can find the logs in the project's `run > logs` folder and the crash reports in the `run > crash-reports` folder.
+
+## Still couldn't solve the problem?
+
+Join the community and ask for help!
+
+- [Official Fabric Wiki](https://fabricmc.net/wiki/start) and their [Discord server](https://discord.com/invite/v6v4pMv)
\ No newline at end of file
diff --git a/getting-started/using-the-ide.md b/getting-started/using-the-ide.md
index 70c169d..2cfadf7 100644
--- a/getting-started/using-the-ide.md
+++ b/getting-started/using-the-ide.md
@@ -1,6 +1,7 @@
---
title: Using the IDE to the fullest
description: Useful information to handle and traverse your Project using the IDE.
+order: 7
---
# Using the IDE to the fullest
@@ -17,27 +18,16 @@ Refer to the `File > Setings > Keymap` Settings or search for the functionality
### Manually
-IntelliJ has many different ways of traversing projects. If you have generated sources using the...
-
-```
-./gradleW genSources
-```
-
-...command in the terminal
-or used the `Tasks > fabric > genSources` Gradle Task in the Gradle Window, you can manually go through the source files of Minecraft in the
+IntelliJ has many different ways of traversing projects. If you have generated sources using the `./gradlew genSources` command in the terminal or used the `Tasks > fabric > genSources` Gradle Task in the Gradle Window, you can manually go through the source files of Minecraft in the
Project Window's External Libraries.
-Generate Sources using the Gradle Task
-
The Minecraft Source code can be found if you look for `net.minecraft`, but also other sources of projects, libraries and dependencies, which are imported using the `build.gradle` file
are located in there. This method is often used when browsing for assets, tags and other files.
-To search in the Project Window, just focus it and start typing
-
### Search
Pressing `Shift` twice opens up a Search window. In there you can search for your project's files and classes. When Activating the checkbox `include non-project items`
@@ -69,15 +59,11 @@ Creating `Mnemonic Bookmarks` enables you to quickly switch back to those bookma
-Right-click on a line number to set a Bookmark
-
It is possible to create multiple Bookmark lists at the same time if you need to separate or order them, in the `Bookmarks` window.
[`Breakpoints`](basic-problem-solving#breakpoint) will also be displayed in there.
-Get an overview over all Bookmarks using the `Bookmarks` window
-
## Analyzing classes
### Structure of a class
@@ -157,8 +143,6 @@ and the `Comment with Block Comment` entries, and set their Key binds to your pr
-Open IntelliJ Settings (`File > Setings > Keymap`)
-
Now you can highlight the necessary code and use the shortcuts, to comment the section out.
```java
@@ -197,10 +181,10 @@ if you are not actively working on them. To create a custom block which can be c
-Region comment block collapsing
-
-This feature may not be supported in other editors and IDEs.
-If you notice that you are using too many of them, consider refactoring your code to make it more readable!
+::: warning
+This feature may not be supported in other editors and IDEs.
+If you notice that you are using too many of them, consider refactoring your code to make it more readable!
+:::
### TODO and FIXME notes
@@ -217,7 +201,9 @@ which uses those type of comments.
-This feature may not be supported in other editors and IDEs.
+::: warning
+This feature may not be supported in other editors and IDEs.
+:::
### Javadocs
@@ -228,8 +214,6 @@ When hovering over method or class names, which have JavaDoc comments added to t
-Example JavaDocs information
-
To get started, simply write `/**` above the method or class definition and press enter. IntelliJ will automatically generate lines for the return value
and the parameters but you can change them however you want. There are many custom functionalities available and you can also use HTML if needed.
diff --git a/items/armor.md b/items/armor.md
index 6dc04e3..0b00451 100644
--- a/items/armor.md
+++ b/items/armor.md
@@ -1,12 +1,7 @@
---
title: Armor
description: Learn how to create your own armor sets.
-prev:
- text: "Tools and Weapons"
- link: "/items/tools"
-next:
- text: "Item Groups"
- link: "/items/item-groups"
+order: 3
---
# Armor
diff --git a/items/food.md b/items/food.md
index 687dd4c..5e38261 100644
--- a/items/food.md
+++ b/items/food.md
@@ -1,12 +1,7 @@
---
title: Food
description: Learn how to add a FoodComponent to an item to make it edible, and configure it.
-prev:
- text: "Creating Your First Item"
- link: "/items/index"
-next:
- text: "Tools and Weapons"
- link: "/items/tools"
+order: 1
---
# Food Items
diff --git a/items/index.md b/items/index.md
index c0a8507..875af03 100644
--- a/items/index.md
+++ b/items/index.md
@@ -1,9 +1,7 @@
---
title: Creating Your First Item
description: Learn how to register a simple item and how to texture, model and name it.
-next:
- text: "Food Items"
- link: "/items/food"
+order: 0
---
# Creating Your First Item
diff --git a/items/interactivity.md b/items/interactivity.md
index b81fd57..2f1a026 100644
--- a/items/interactivity.md
+++ b/items/interactivity.md
@@ -1,9 +1,7 @@
---
title: Item Interactivity
description: Learn how to create an item that uses built-in vanilla events.
-prev:
- text: "Custom Item Groups"
- link: "/items/item-groups"
+order: 5
---
# Interactivity
diff --git a/items/item-groups.md b/items/item-groups.md
index 264a0f9..b6f9440 100644
--- a/items/item-groups.md
+++ b/items/item-groups.md
@@ -1,12 +1,7 @@
---
title: Custom Item Groups
description: Now that you've added many items - they should probably be put together.
-prev:
- text: "Armor"
- link: "/items/armor"
-next:
- text: "Item Interactivity"
- link: "/items/interactivity"
+order: 4
---
# Custom Item Groups
diff --git a/items/tools.md b/items/tools.md
index e161e9a..6c4bce2 100644
--- a/items/tools.md
+++ b/items/tools.md
@@ -1,12 +1,7 @@
---
title: Tools and Weapons
description: Learn how to create your own tools and set their durability and mining levels.
-prev:
- text: "Food Items"
- link: "/items/food"
-next:
- text: "Armor"
- link: "/items/armor"
+order: 2
---
# Tools