tutorial:concepts
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tutorial:concepts [2022/05/23 19:21] – mehrcraft | tutorial:concepts [2022/05/24 11:06] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Essential Minecraft Concepts ====== | ====== Essential Minecraft Concepts ====== | ||
- | This section was designed as a 10,000m overview for beginners by a beginner, covering essential concepts and definitions needed as background knowledge before you start your first mod. Some concepts relate to elements visible in game, others to used files or classes that are frequently used while modding. | + | This section was designed as a 10,000m overview for beginners by beginners, covering essential concepts and definitions needed as background knowledge before you start your first mod. Some concepts relate to elements visible in game, others to used files or classes that are frequently used while modding. |
^ Concept | ^ Concept | ||
+ | | Item | Something you can hold in your hand, drop to the ground, place in inventory or store it in a container. It may be a tool or a block held in the hand before placing it. | | ||
+ | | Block | The key component for anything you build in Minecraft and has been placed in the world. A lot of blocks are cubes, but most things you place in the world are implemented as blocks, like a furnace. Some blocks don't even look much like a cube, like buttons, fences and doors, and yet they are still treated as blocks. It is important to note that a Block should be thought in code as the definition for a type of block, not the actual single block you see in game. | | ||
+ | | Block state | Block states (often seen in code under the name " | ||
+ | | Block item | The item form of a block, so that you can hold them in your hand, stack them and store them. | | ||
+ | | Entity | Dynamic objects in the world that typically move. For example, ''< | ||
+ | | Living entity | A subcategory of entities that are alive and moving in the world, like players and mobs (cows, zombies, bats etc.). | | ||
+ | | Block entity | Stores additional data for a block like contained items or crafting progress. They can provide extra logic for a block, for example when ticking. Not all blocks have block entities - those who do implement ''< | ||
+ | | Block/item model | The model is a set of descriptive data used to represent the appearance of a block or item. For example, an iron block or furnace would contain information to describe the shape and size of each of its faces, as well as information about where to find the texture (image) that is used to give a particular surface its unique look. Models are usually described in JSON files but can also be generated via Java code. | | ||
+ | | Entity model | Entities also have their own 3D models, which are usually defined entirely in code as instances of ''< | ||
+ | | Texture | These are the graphic images used to give surfaces their unique look. They are usually implemented as 16x16 pixel .PNG files for blocks and items, or as larger images for entities and GUI elements. | | ||
+ | | Renderer | While most mods make use of '' | ||
+ | | NBT | NBT is a data storage file format used by Minecraft. NBT save/load methods are what you use in your entity or block entity class to make sure that your data gets stored and loaded from the world' | ||
+ | | Sides | Minecraft is designed in two separate pieces, a client and server piece. When you play on a server, the division is clear, but the server piece still exists when you play on your own computer. You will often see a given overridden method being called by both the client and server, and to distinguish to which side you are responding to you will need to test for it. The easiest and most common way is to check with the boolean method '' | ||
+ | | Data sync | Although you can store block data on its block entity, such data does not travel automatically between the server and client. You need to enable it yourself with a couple lines of code, again following the description in " | ||
- | | Item | Something you can hold in your hand, drop to the ground, place in inventory or store it in a container. | + | This is an early version |
- | | Block | The key component for anything you build in minecraft and has been placed in the world. | + | |
- | | Blockstate | Blockstates (often seen in code under the name ' | + | |
- | | Block Item | The item form of a block, so that you can hold them in your hand, stack them and store them. | | + | |
- | | Living Entity | Something alive and moving in the world, like players and mobs. | | + | |
- | | Entity | An internal structure to hold state data. For example, BlockEntity for blocks or ItemEntity for items, and of course LivingEntities. | + | |
- | | Model | The model is a set of descriptive data used to represent the structure of a block, item, living entity, etc. For example, an iron block or furnace would contain information to describe the shape and size of each of its faces, as well as information about where to find the texture(image) | + | |
- | | Texture | These are the graphic images used to give surfaces their unique look. They are usually implemented as 16x16 pixel .PNG files. | | + | |
- | | Renderer | While most mods make use blockstates and model JSON files plus .PNG textures to provide the full representation of blocks, items and entities and rely on the default rendering mechanism to show them in the world as you'd expect, there are situations when you will need more complex behaviors. | + | |
- | | NBT | NBT methods are what you use in your Entity class to make sure that your block' | + | |
- | | Threads | Minecraft is designed in two separate pieces, a client | + | |
- | | Data Sync | Although | + | |
- | + | ||
- | UNDER CONSTRUCTION | + | |
- | Please correct errors if you notice | + |
tutorial/concepts.1653333663.txt.gz · Last modified: 2022/05/23 19:21 by mehrcraft