Minecraft Forums

There should be some errors in the log (logs/latest.log in the game directory) explaining what went wrong, upload it to Gist and link it here.

You may want to install Forge while you're working on the model, since it greatly improves the error reporting of the model loading process. If you do, upload the FML log (logs/fml-client-latest.log in the game directory) instead of the Vanilla log.

You should also upload the model file itself and post the paths of your texture files.

You should create a resource pack rather than editing the vanilla files directly.

The JSON model format is documented here.

Each property in the textures block defines the value of a texture name. The block/cube model uses one texture per side, with the side's name as the texture name. The up texture is displayed on the top of the block, the east texture is displayed on the east side of the block, etc.

The texture paths are in the format "<domain>:<path/to/texture>", which corresponds to assets/<domain>/textures/<path/to/texture>.png. If you don't specify a domain, it defaults to minecraft.

Quote from Icedice9»

Hey, this is looking promising! I used the line below:

TextureAtlasSprite sprite = Minecraft.getMinecraft().getBlockRendererDispatcher().getModelForState(block.getDefaultState()).getParticleTexture();

Two questions with this: First, is there a better way than using getDefaultState? I get the feeling this won't support blocks with metadata like

stone, for example, that have multiple sub blocks.

Store the full IBlockState rather than just the Block.

Second, how can I get a BufferedImage from the TextureAtlasSprite? Is it possible to get a ResourceLocation or DynamicTexture from the TextureAtlasSprite? I will use the BufferedImage to create the entity texture by duplicating the block's texture multiple times over the entity texture.

JEI has code to get a TextureAtlasSprite from an IBlockState or ItemStack (this returns the particle texture) and to get a BufferedImage from a TextureAtlasSprite here.

You'll need to get the IBakedModel for the block and then get the texture locations from that. Either use the model's particle texture or the texture from one of the model's BakedQuads.

These texture locations are actually the names of sprites on the block texture atlas, they don't necessarily correspond to texture files on disk. This means you should get the textures from the atlas rather than reading them from a file.

Quote from BillyGalbreath»

Very good points both of you make. However, I guess the part that confuses me is that I am working with a custom Container object so it's loaded on both server and client side (client loads it behind a Gui), and I'm doing something on another thread and need to schedule something back on the main thread for thread safety b.s., and I the only thing I've found to be able to do so is use Minecraft.getMinecraft().addScheduledTask() or player.getWorldServer().addScheduledTask(). I can't use the Minecraft class because it will make the server side fail with the container loads with that import (because it doesnt exist server side), so I'm using the WorldServer method because even in single player the game is running a server instance. The method I posted earlier is backed by a sidedDelegate instance that can hold the data I need for either case safely. Or am I fundamentally missing some basic knowledge here?

A client-side Container shouldn't be directly interacting with the server (or scheduling a task to run on the server thread) as that would be reaching across logical sides.

You need to handle this through the sided proxy system:

• On the physical client (i.e. in the client proxy), check which logical side the thread belongs to:
• If it belongs to the logical client, schedule a task to run on the client thread using the Minecraft instance.
• If it belongs to the logical server, schedule a task to run on the server thread using the MinecraftServer instance or a WorldServer instance (which delegates to the MinecraftServer instance anyway).


• On the physical server (i.e. in the server proxy), check which logical side the thread belongs to:
• If it belongs to the logical client, throw an exception as something has gone wrong (the physical server doesn't run the logical client).
• If it belongs to the logical server, schedule a task to run on the server thread using the MinecraftServer instance or a WorldServer instance.

As explained in the documentation I linked, World#isRemote is the way to tell which logical side code is running on.

Are you sure you need a separate thread? Can you not run this code on the main client/server thread directly?

Quote from theishiopian»

1. what is the registry name of skull blocks?

Look at the Block.registerBlocks method for the registry names of vanilla Blocks (and their ItemBlocks) and look at the Item.registerItems method to see the registry names of vanilla Items (including block items that don't extend ItemBlock, like ItemSkull).

2. Is it possible to, within one json, to define a recipe that can take multiple different ingredients in the same slots, as in you can use sticks or blaze rods as a handle for a pickaxe. Is there a way to do it without using the ore dictionary?

You can use an array of ingredient objects anywhere a single ingredient is expected to create a compound ingredient that matches any of the items matched by the component ingredients.

Vanilla uses this for recipes accept multiple possible items per slot (e.g. minecraft:crafting_table accepts any plank).

Quote from Callunxz»

Hm... anyway I can send the information of the items to the other clients?

I assume through packets, which is the best method?

You'll need to scan each player's inventory for changes every tick on the server and then send any changes to all players tracking that player entity.

Use a capability to store the list of items that need to be synced/rendered for each player. Note that you can't use IItemHandler directly, since EntityPlayer already provides that capability itself.

I wrote this pseudocode example of how you could handle the syncing. In the packet's handler, you'd want to apply the changes from the packet to the client-side player entity's item list.

Quote from theminecraftgames»

I knew you should add it as a dependency (which I had) but I didn't know you should run the "idea" task afterwards. There was also a bug in my build.gradle.

You shouldn't use the idea task. When creating the project, import build.gradle directly. When updating the project (e.g. adding/removing dependencies), refresh it from IDEA's Gradle window.

The ICustomModelLoader should return the base state of the model. The broken state can be handled by the ItemOverrideList.

The textures can either default to null (like ModelDynBucket) or be manually loaded from a file (like Tinkers' Construct's ToolModelLoader).

If the model is loaded from a blockstates file, IModel#retexture will be called with the textures specified in it; allowing you to return a new model with those textures.

ICustomModelLoader#accepts should only return true for a specific location (if you're using a single instance like ModelDynBucket) or extension (if you're loading data from a file like Tinkers' Construct). Look at the implementations of this method in ModelDynBucket.Loader and ToolModelLoader for examples. models/item isn't specific enough.

You probably don't need a cache here.

I had to change xlfoodmod.general.WorldGen.tooltip to xlfoodmod.general.worldgen.tooltip in the lang file to get the category tooltip working, this is because Forge coerces your field names to lowercase before using them in lang keys and subcategory names.

It turns out that Forge doesn't actually use the lang key specified for the @Config class in the config GUI if there's only one @Config class, the title is always just your mod's name. I've reported this here.

Quote from Choonster»

You'll need to specify your own IGuiFactory class using the @Mod#guiFactory property. DefaultGuiFactory uses the GuiConfig(GuiScreen, String, String) constructor, which uses GuiConfig#collectConfigElements to create and sort the config elements, you'll need to create a similar method and use a GuiConfig constructor with a List<IConfigElement> parameter.

I found another very interesting and simple solution to this problem

Unicode has a range of codepoints called a Private Use Area. These, by definition, will never be assigned characters by the Unicode Consortium.

It also turns out that Minecraft doesn't render any characters that are in a private use area. This means that you can simply append a private use codpoint to the beginning of the name to have it sorted properly.

The first private use area ranges from E000 to F8FF, which means you can have up to 6399 config values sorted, which should be more than enough.

I created an example Gist here if anyone else wants to use it.

---

Table of Contents:

Overview
Changes in how things work
Frequently Asked Questions
[WIP] The Cubic Chunks Mod!
Gallery
Supporting this suggestion
Special thanks

[spoiler=Tl:dr]Q: Won't this increase lag?
A: Absolutely not. The title of this suggestion and big red letters at the top of this post aren't lying. If you want to know how, then I suggest you actually read this post.

Q: Will this change terrain? Will this break existing worlds?
A: No. Terrain change is not necessary. Existing worlds can be converted fairly easily with a process described later in this post.

Q: How can sunlight or rain work with infinite vertical space?
A: I suggest you read Coping with sunlight, because it's too complex for a tl;dr.

Q: I have a different question but still don't feel like reading this post. What do I do?
A: Too bad, read the FAQ. I put way too much work into this for the entirety of it to be ignored.[/spoiler]

---

Overview:

In Minecraft, the sky is the limit - literally. It doesn't matter how many thousands of blocks a player has traveled, or what dimension they're in, or even if they're playing in creative or survival, the highest they can ever build is up to a height of 256. Why is that? If Minecraft can have a world that's infinite in the north, in the south, in the east, and in the west, why can't that world be infinite up and down too?

In Minecraft's earliest days, in Classic and Indev, the world was not infinite in any direction. This was because the entire world needed to be generated at the same time, and the entire world needed to be simulated at the same time as well. This led to a conundrum - the bigger the world, the more it lagged.
Notch didn't like this. He knew his players liked to explore and build large creations, so he found a way to make the world truly infinite. When the Minecraft '' class='bbc'>Infdev came out, it brought with it truly infinite worlds. Suddenly, players could travel hundreds of thousands of blocks in any direction, and never encounter a barrier, or become too laggy.
The Infdev update brought about a very large change to Minecraft worlds to accomplish this feat. For the first time, instead every world being just a single huge piece, they were broken up into a two-dimensional grid of pieces, called chunks. Through breaking the world up into pieces, this 'chunk system' enabled infinite worlds by letting Minecraft create new pieces and simulate them only when it needs to.

Why does that not apply to the vertical axis? Because the type of 'chunk system' Minecraft uses right now is a linear one, which, by using only a two-dimensional grid to map out chunks, means that it is impossible for chunks to stack on top of one another, and by extension, meaning that a single chunk must cover the entire vertical space. This brings back the problem that the Infdev update was supposed to eradicate, now only with chunks, instead of an entire world; the bigger a chunk is, the more laggy it is. You can't just increase the height limit and make chunks taller, because it will become laggier, and laggier, and laggier to do it.
That's why, to fix this, Minecraft must change over to a cubic chunk system. Under this system, 16³ block chunks are aligned on a three-dimensional grid, completely eliminating maximum height as an aspect of lag.

The immediate benefits:
•Minecraft worlds become as virtually infinite vertically as they are horizontally: The absolute limit being Y = ±30,000,000.
•A large FPS increase: Alpha testers report an FPS increase of 100~200%.
•Increase in running capability: Computers running Minecraft on Tiny render distance will handle only 30% the blocks they do now.

The possible features:
•Spherical render/load distance: Reduce handled blocks by up to 30% by cutting corners made of unneeded chunks.
•Server chunk occlusion/exclusion: Reduce bandwidth usage and defeat hackers by only sending data for visible chunks.
•Three-dimensional biomes: Save biome data per chunk rather than per block column, create volcanoes with magma chambers, underground rivers, tropical skylands floating over icy taigas, and more.

The disadvantages:
•Unloaded gravity-pause: Falling non-player entities and fluids will be forced to pause their fall if they reach unloaded chunks, but will resume falling when those chunks are loaded.
•Slow falling-pause: Players with slower computers and smaller render distances will have falling occasionally paused as they fall into unloaded chunks, until new chunks can be loaded.

The problems:
•Current sunlight and rain calculation methods cannot work with infinite vertical space: The solution to this is described here.
•Current BiomeDecorator cannot work with multiple vertical chunks simultaneously: The BiomeDecorator code must be altered to function correctly with this, or removed.
•Current cave generation method is executed an extra time for each vertical chunk created simultaneously, leading to lag spikes on world generation: Cave generation's method must be altered to suit this system more.
•Current grass/dirt generation algorithm forces additional chunk requests when chunks are loaded, causing chunks to load slower than they should: This algorithm must be replaced with something else.

---

Changes in how things work:

Obviously, the implementation of this new chunk system will change quite a few things. These changes are mostly either necessary or in the interest of increased efficiency. Such changes are categorized and explained below.

How worlds will be stored:
[spoiler]How the current storage works, and what changes:
Interestingly enough, the current method of storage, the Anvil format, is derived from the storage method that the original Cubic Chunks mod used. The Anvil format stores individual chunk as a series of 16³ quasi-cubic chunks. These 'fake' cubic chunks allow for easier reference of specific data, but they still can't be separated from each other, meaning that it fails to reap the full benefits of this system. Even so, the change allowed Mojang to double the maximum height with no performance hit. Chunks are stored in groups of 32², inside 'MCRegion' files, for a total of 1024 chunks.
By nature, cubic chunks does away with the 'quasi-cubic' nonsense. In terms of chunk grouping, instead of using groups of 32³ chunks, new "3DRegion" files would contain groups of 16³. This means each 3DRegion file contains 4096 chunks, four times as many as MCRegion files. However, each 3DRegion contains only one fourth the amount of blocks. For per-chunk positional metadata, 3DRegion files would use the same number of bits as MCRegion files, after compression. Calculations show that the same area encompassed by a single MCRegion file would consume 64 kilobytes of extra space with 4 3DRegion files, which is nothing.

Converting existing worlds:
Most people are probably wondering something like "But won't this totally destroy all existing worlds?". Absolutely not; conversion could not be simpler. When a non-cubic world is loaded after the implementation of this system, a conversion process will begin and convert the entire world at once(To avoid making chunk loading take longer during play). First, all existing MCRegion files will be divided into quarters to create 3DRegion files. Then, all existing chunks are divided into sixteenths using the quasi-cubic properties to identify boundaries. After that, conversion is done.

The "isEmpty" flag optimization:
A 1-bit flag is added to each chunk, named "isEmpty". If the chunk consists of 100% air blocks, this bit is 1, any other case makes it 0. When the bit is 1, all data for the chunk besides the isEmpty flag is deleted and ignored, which reduces filesize. Empty chunks are never loaded, and locations where they occur are merely simulated as entities reside in them. The chunk will only load when something requires saving inside it.[/spoiler]

Changes to terrain, ores, etcetera:
[spoiler]Terrain:
By default, nothing will change. Small bits of terrain generation code need to be reconfigured to work properly with Cubic Chunks.

Biomes:
By default, nothing will change.

Ore generation:
By default, nothing will change.

Structures:
By default, nothing will change.

The Void:
After conversion to Cubic Chunks, the void and bedrock layer will still exist and generate as they always have. However, the void(Not the bedrock layer!) will not exist as a hard limit and is able to be moved, but not removed, by editing an associated NBT data tag inside a world's level.dat. This feature, that allows for increasing the maximum depth, is intentionally disabled without external programs, to prevent terrain change of any sort. It is intended to be used by experienced mapmakers and world generation mods only.

Superflat settings:
Existing superflat worlds will not change. However, new superflat worlds will gain a new decoration parameter, 'void'. Inclusion of this parameter will cause the void to form below the lowest defined layer. Exclusion of it will cause all layers below the lowest defined layer to copy the settings of that layer.[/spoiler]

Coping with sunlight:
[spoiler]There used to be a solution here, but it wasn't deemed good enough by Jeb. Suggest solutions in this thread.[/spoiler]

Changes to servers:
[spoiler]Settings:
There's a setting inside the Server.properties file called 'max-build-height'. The setting makes it impossible for any player to place or remove blocks above that height.
With the implementation of Cubic Chunks, a new setting named "maximum-generation-depth" would be added. The void, bedrock layers, and magma layers will generate normally at and above the Y level designated by the value of this setting.

Chunk occlusion/exclusion:
Using the raytracing methods already available in the code and used for explosion calculations, servers can identify which chunks are visible to a player, within safe assumptions, and only send the data for those chunks. This both reduces bandwidth usage, and cripples the usefulness of X-Ray cheats.[/spoiler]

Render/Load distance alterations:
[spoiler]After the implementation of Cubic Chunks, view distances' radii will apply to the vertical axis too. This reduces handled blocks in the cases of tiny and short render distances, and increases them in the cases of normal and far render distances. This can be optimized by utilizing a spherical render distance instead of a cubic one, which would reduce handled blocks in all distances except Far.[/spoiler]

---

Frequently Asked Questions:

[spoiler=FAQ]Q: This is impossible.
A: No it's not. See below.

Q: Is this available as a mod?
A: Not yet! But it will be!

Q: I like X-ray! What if I don't want it to be broken?
A: First of all, breaking X-ray hacks will only be possible to do in multiplayer. That said, the system that would break X-ray would be possible to disable by the server owner. If the owner doesn't disable the system, then they don't want you using X-ray, and you should not be doing what the server owner doesn't want in the first place.

Q: I play on a PvP/Anarchy/Raid/Faction server. Won't this system let people pillar up into the sky and create a base thousands of blocks in the air and never be found?
A: No.

Q: I like Minecraft's current height limits. What if I don't want to have an infinite sky or infinite underground?
A: If this system is added, all worlds will not automatically gain an infinite underground. As stated below, the Void will remain in all worlds, even after the conversion to Cubic Chunks. The ability to remove the Void will simply be there. As for infinite space in the sky, the current build limit is over one hundred blocks above any terrain that vanilla Minecraft can possibly generate. It is ENTIRELY your decision on whether or not you take advantage of this height. If you play on a server, like stated above, the server owner can set a maximum build height. If s/he doesn't, then don't play on their server - you don't play on servers where the server owners allow things you don't like. Why would you play on an anarchy server if you hate being stolen from and killed?

Q: Will this affect Redstone at all?
A: No. This system will simply make it possible to make larger redstone circuitry than before.

Q: Won't this break existing worlds?
A: No. Existing worlds can be easily converted by dividing each MCRegion file into 4 pieces, then slicing the existing 256 block-high chunks inside them into 16 individual chunks.

Q: Won't this affect mods? Won't mod authors have a hard time updating their mods?
A: The answer to this question depends solely on the answer to the following two questions: Do parts of the modification code rely on chunk data/metadata? Does the mod author want to take advantage of the features of the new chunk system? If the answers to the first and second question are both "No", then updating a mod to this system should be very easy and quick. If the answer to the first question is "Yes", then those parts of the code will need to be rewritten somewhat, but in most cases, the changes should be fairly quick and easy. The only time that it should be hard to update a mod to this system, is if the answer to the second question is "Yes".

Q: Won't this require a total rewrite of the mod API if that's released first?
A: No. Whether or not even a small part of the mod API needs to be rewritten depends on the way that it is implemented and whether or not there are API inclusions for chunk handling and other chunk-related behavior.

Q: Could a player fall into unloaded chunks if chunks aren't loaded fast enough?
A: No, they could not, and for several reasons. Minecraft has a terminal velocity, though it might not seem like it. This velocity is slower than it should take to load new chunks below the player. In cases with exceptionally slow computers, even if the player did manage to reach an unloaded chunk, their fall would be paused until that chunk can be loaded.

Q: What would happen when water, sand, or a mob falls into an unloaded chunk?
A: Nothing. The water/sand/mob would freeze in place until the chunk is loaded and it can continue moving. You can already see this same thing happening on the horizontal axis.

Q: What will happen to the Void?
A: It will still exist, along with all its effects. The only difference is that the Void is no longer a hard limit and it can be moved. After the conversion to Cubic Chunks, the Void's location will be stored in a world's ' class='bbc'>level.dat, and this location can be changed with NBT editing tools. When and where the Void exists, chunks will cease to generate.

Q: Will this affect terrain?
A: No. However, terrain generators will gain the ability to use infinite height.

Q: Will this affect ore generation?
A: No. Ore is a part of terrain generation. As stated above, terrain will not be changed.

Q: Won't all current terrain generators be incompatible with this system and need to be rewritten?
A: No. Terrain generators work independently of chunks. When a chunk is generated for the first time, it calls the terrain generator and receives a specific section of the resultant terrain to save inside itself. Because of this, some custom terrain generators can generate steep terrain all the way to Y256, where you can experience a large, flat cut-off. Since there are no chunks above Y256 to call the terrain generator for terrain, no terrain exists there.

Q: What would happen if there's a huge solid ceiling so far above you that it is unloaded? Wouldn't you just see the sky, just with everything being completely dark?
A: Yes. This already happens on the horizontal axis, and it is an issue with sky rendering, not this chunk system. As such, this has nothing to do with this suggestion. Please do not post about this.

Q: If you go deep underground, will your plants grow/ores smelt/animals grow?
A: No, because those chunks would be unloaded, just as if you had walked far away. This is a flaw with any chunk system, regardless of shape. It is a necessary evil that allows Minecraft to have infinite worlds. The only way to fix this would be to introduce a separate new system that works with chunks as they are loaded and unloaded. This suggestion deals with the chunk system itself, and not sister processes. Because of that, that is outside of the scope of this suggestion. Please do not post about this.[/spoiler]

---

[WIP] The Cubic Chunks Mod! (Tall Worlds Mod):

Cuchaz has taken it upon himself to bring us the glorious Cubic Chunks, since Mojang refuses to do so.

Cuchaz is using a API of his own creation to help assist in the making of this mod, and he's quite far along, as seen in these two tech demo videos:
[spoiler=T-Demo 1: Vertical chunk loading][/spoiler]
[spoiler=T-Demo 2: Broken height cap and no lag!][/spoiler]
With the basic functionality in place - a complete overhaul of the basic chunk system, and height limit removed - this whole concept can already be considered proven. What remains is making sure everything else functions correctly under the new chunk system. In any case, stay tuned for future updates if it interests you(If it doesn't, then you are the weakest link - goodbye!).

You can follow the mod's development in much more depth in its very own topic!

---

Gallery:

[spoiler=A mountainside with an experimental engine using Cubic Chunks designed by Nocte. 960 block view radius, and 30 FPS.][/spoiler]
[spoiler=A different view of the mountainside with the same engine by Nocte. This time, with 1600 block view radius and 15 FPS.][/spoiler]
[spoiler="A video demonstrating Nocte's engine."]

---

Support & Submission to Mojang:

If you support this, hit the rep button in the bottom-left corner of this post. It is the only good way of accurately measuring support here.

If you wish, you can put the following banner, courtesy of laz2727, into your signature. It helps to attract support from all parts of the forum!

 [url=http://www.minecraftforum.net/topic/1707097-cubic-chunks-infinite-height-elimination-of-x-ray-and-more-60-supporters/page__st__0][img]http://img833.imageshack.us/img833/443/hov.png[/img][/url]

Please help us get word out of this suggestion! Share this with your friends, with Minecraft celebrities if you're familiar with them, or even with Mojangsters like Jeb or Dinnerbone! (Do not share this with Notch. Notch doesn't work with Minecraft anymore.)

The purpose of this suggestion is to have Cubic Chunks implemented in Vanilla. Being available as a modification does not fulfill that purpose. The modification featured in this suggestion is to act as a proof-of-concept only(Note: Its being featured here is to act as a proof-of-concept. The modification itself is on its way to becoming a fully fledged modification).

---

Special thanks:
Cuchaz, for taking Barteks' proof and running with it, to give us a truly functional Cubic Chunks mod.
Barteks2x, for updating the Cubic Chunks mod to 1.6.2, proving that it is possible.
Azraile, for posting the original suggestion and allowing me to take ownership of it.
Nocte, for helping resolve flaws and designing Hexahedra.
MineCrak, for a large amount of valuable insight and enthusiasm into the topic of Cubic Chunks.
aaronfranke, for helping resolve flaws.
PanJouda, for creating the original banner.
Flexico, for creating the predecessor to the current banner.
laz2727, for creating the current banner.
Robinton, for creating the original Cubic Chunks mod.
The_Watchman13, for answering all those stupid questions so I don't have to.

---

Note: Many calculations and information can be found among the many posts of this topic. There are too many for me to cite here, but if you wish, you can search for them yourself.

Hi!

Several months ago I started to develop a very big mod for my future Minecraft-based custom server and had faced one problem: Minecraft GUI library is really painful to use, especially if you had experience in developing GUI's under other platforms. And, since my mod should use a lot of custom GUI windows, I decided to port a very well-designed Android GUI library for it.

As a result, I've made MineDroid — GUI library that manages resources of my mod and allows me to edit and store windows layouts in XML files. Main concepts of it were taken from Android so people who used to develop android applications, probably will find this library very useful and easy to understand. Anyway I've tried to make some documentation for it and even wrote a quick-start guide

Library can be used as a separate library mod, providing your mods ability to make fancy interfaces
Right now it's on beta-testing: if you'll find any bugs, feel free to report about them on the GitHub bug tracker. I'll do my best to fix bugs as soon as possible.

You can check it here: http://chedim.github.io/minedriod/

Please, comment if you find this library useful for you. It will affect how much time I will spend to support the library.

Also, there is a plugin for IntelliJ Idea that will help you to manage your resources: it adds autocompletion for XML layouts and generates R.java file with a class containing links to all your resources.

Thank you!

Some example and test GUIs:

Quote from jadenPete»

I agree, but for some people, coding just isn't there thing.

Then they shouldn't be developing mods. There's a Requests and Ideas section for a reason, if you don't like programming, feel free to post your idea in that section and a developer may pick it up and develop a mod based on it if they want to. Or, you can recruit a programmer to work with you, you as the ideas guy, and the programmer as the, well, programmer.

It's harsh, but it has to be, you cannot mod without programming. The outcome of modding without programming would either be the generic "Dirt to Diamond" or "Emerald Tools" mods, or really really bad low-quality ripoffs of much better and bigger mods like IndustrialCraft, Botania, BuildCraft, Thaumcraft, Thermal Expansion, etc. One way or another you have to know how to code. Simple decorative mods are fine, you can use MCreator for that, but any more and you should toss it out. Want to make an entirely custom entity with custom logic and AI? Not possible with MCreator. Want to make a new minecart? Not possible with MCreator. Want to make an addon for a mod or have your mod interact with another mod? Not possible with MCreator. Want to make a custom furnace that uses adjacent blocks as fuel? Not possible with MCreator. 99% of more advanced ideas that aren't hard at all to do with code are not possible with MCreator. And that's your first problem.

The second problem is with MCreator to my knowledge you don't get the source code, it generates it for you. So you'd have to decompile a class yourself, which is way too advanced for people who use MCreator to do themselves without a problem in the first place, and it has tons of small, trivial errors that may take hours to fix that people who use MCreator may not necessarily know how to fix.

The third problem is once you get the source code, it would be wise to just delete it and start over for two reasons. One, you didn't write the code, you have no clue what the code does or how it does it. You'd have to dissect it and figure out what it does which adds needless complexity. Two, the code MCreator generates is messy, bulky, inefficient, bad and last I checked, outdated (last I saw of decompiled MCreator mod classes it used Forge but referred to ModLoader compatibility classes, something you never ever ever ever ever ever do as the Forge ones are a tonne more stable, efficient and reliable). So you'd have messy and inefficient code that just confuses you, especially if you're new to Java.

The fourth problem, and it's one that doesn't really slot at the end but is overarching all of these problems, MCreator teaches you literally nothing about coding. Hell, you even need to know how to code to use MCreator in the first place if you want to do the more "advanced" stuff with events, kinda contradictory of the point of the application if you ask me. Okay, you know you can add a block to the game, whoopdy-doo, you already knew that, but do you know how to do that in code? Answer would be a no. MCreator is pointless in the grand scheme of things, it's a magnanimous waste of time. Not only do you need to ditch MCreator and forget everything you learned with that, but you have to rewrite everything you did in it from scratch yourself. Major waste of time.

Modding requires programming, there is no way around it, any way around is just an illusion that shatters the moment you need to do something it cannot do. Do not use it.

Quote from speeder55557»

ok good information but I am looking for a download-able thing if thats possible

If you mean tutorials that you can download, not sure there is any available. You could download the videos of Youtube and play them off of your drive using a media player, and I'm sure there's an application / website that'll download entire playlists, the problem with that though is TheNewBoston has about 80 something videos on Java, and other playlists aren't exactly small either.